I have an old Nokia 3650 cell phone with a pre-columbian Java and an even older Symbian OS rev. Although it might just as well be called the Simian OS for all the good that my opposable thumbs do me. While it basically sucks I have learned how to take advantage of its many Web 0.5 features like WAP browsing.
I have experimented with most aspects of mobile internet, mobile local and mobile search on my phone. Most web implementations and search options for this generation of technology are either useless or so difficult to use that they might as well be. They do however tend to highlight interface issues with using mobile devices for browsing, emailing, reading etc. and when it does work it is awe inspiring. There is still something very Buck Rogerish about reading Bill Slawski’s recent post on Google Health & Privacy while heading down the highway (my wife IS driving of course).
Any task that requires significant input like internet searching, extensive email responses and Google SMS local search get used only when the “pain is worth the gain”. Other activities like Goog-411 that are not only painless but “fun” get used more regularly.
The one surprising thing that my antiquated cell phone does well is allow me to read. Virtually all of the uses that I have found for it include active reading with little or no input….I read emails (then call the client), read my kids text messages (then fume :)) and most significantly keep abreast of my Google Reader list of “must read” local search news for the day.
Reading “Mobile web design is so different from the desktop web” (Martin Kleppmann of www.yes-no-cancel.co.uk) clarified my understanding of why some things work and some don’t on my ancient mobile browsing environment.
Google in their WAP mobile Google Reader implementation demonstrates Martin’s point:
For mobile users it is even more important than for normal web users that the designer has figured out exactly what the most frequently needed aspects of his site are, and made those aspects immediately and very easily accessible. This means that a mobile page can contain far fewer navigational elements (links) than a page intended for desktop viewing.