My Layar development experience

When SPRX Mobile announced that they were opening up the Layar API back in July, I applied immediately. I wanted to learn more about publishing geo-coded data, keep abreast of what Layar was up to, and try to deliver some useful data all at the same time. Fortunately my application was accepted and I received one of the first batch of API keys to go out.

My specific project has been to take the real-time bus arrival information provided by One Bus Away and publish it on the Layar platform. I use the mobile-formatted One Bus Away website at least twice per workday as part of my commute. This data is currently only available in Seattle, but will soon be expanding to everywhere that offers a GTFS feed. My feelings about this experience have been almost entirely positive, but I still come away from it discouraged.

On one hand, the people building Layar (Dirk in particular) have been very helpful. The platform is easy to develop for and they provide good documentation and tools to make it even easier. All of the time spent on this project (which took less than 24 working hours, total) was spent figuring out Google AppEngine, the python web framework I used, the One Bus Away API, and how to filter nearby stops to a reasonable set to show to a user. With minor exceptions Layar performed very well. I have provided all 436 lines of code here so you can see for yourself how easy it was.

Marjolein and Claire from SPRX were helpful in less technical ways too.  All developers were invited to the launch event to show off their layers. They ran several conference calls for people all over the world to answer any questions on the API or about the launch. SPRX has done a great job with the launch of Layar 2.0, and I think all the positive press they have received is a direct result of that.

My discouragement has less to do with Layar specifically than it does with the entire category of tricorder augmented reality. The view through the mobile phone and its camera is less useful than a top-down map would be for every piece of data I have seen so far. For my layer in particular, the rider is very likely to know where the stop is. In situations like that where location is unimportant, both the Reality View and Map View actually get in the way.

This experience has led me to two conclusions.  First, augmented vision is pointless until head-mounted displays are available.  I already felt that way, so now I am just more firm in my belief.  Second, filtering data to a useful subset for display is actually the hard problem.  Job listing sites, travel sites, Ecommerce sites, and review sites already knew this, which is why they spend so much effort on search. Turns out the problem is the same for mobile location-aware services.

If you live in Seattle and would like to try out the One Bus Away layer for Layar, just search for One Bus Away inside of Layar.  I welcome your feedback on how I could make this layer more useful. And, of course, I would also love to hear your thoughts on the utility of augmented vision on a mobile phone.


5 Responses to “My Layar development experience”

  1. MrRoyce replied on :

    Hi there, I am a developer that is dying to try out the Layar/AR API. Your comment on the usefullness of AR for applications such as ‘bus arrival info’ is similar to my own thinking. I would think that fixed location AR is most useful for people that are new to an area or for targets that change freq. (E.g. homes for sale). There may be times when someone need to find a gas station that is open at 2am or where their towns recycling station is, but to me, those are more ‘gimics’ than things that are going to gain traction in the AR space. I can also see restaurants or other businesses providing specials to folks that visit their AR related web page etc.

  2. sidereal thought on :

    And, of course, I would also love to hear your thoughts on the utility of augmented vision on a mobile phone.

    Would you love to hear my thoughts on augmented vision itself? Probably not, because I know you’re a fan :) . Restricting information delivery to line-of-sight is fundamentally a step backwards. I can’t think of any data application that would be enhanced by constraining the data to what I can see. Even just putting peoples’ names above their heads is improved by an overhead map that shows me the names of people in the next room over as well.

  3. Rob replied on :

    Hi, Joe,

    Thanks for posting your experiences with Layar. I submitted a proposal for a Layar app and it was accepted. I think it will work well with AR, because it will show locations that even those who live in the area may not know exist. Anyway, I am not a programmer, I’m a tech writer. When I took some programming classes in college they were still using punched cards, so that should tell you I’m a dinosaur. What would be the minimum programming skills I need to acquire, or are there templates available that I could use and just populate with my own data? I have a hosted website although I haven’t done much with it, but I know it supports MySQL, Python, and the usual server-side apps. Any suggestions you could offer would be greatly appreciated.


  4. Joe commented on :

    I haven’t looked at the Layar docs in a while, but I imagine they have tips to get you started. Unfortunately I don’t have much advice on where to start as a non-programmer. Python worked pretty well for my stuff, so maybe just start with the general Python tutorials? I’m sure there’s one for non-programmers somewhere.

1 Pingback

  1. Pingback from Layar Rapid Development Tools – Layar Blog on :

    [...] Joe Ludwig has published the python code for one of his Layar projects in his blog post here. For the impatient, Here's the [...]

Leave a Reply