I Like The Mobile Internet, When Done Right
January 28th, 2008Last year I signed-up for an unlimited mobile plan with Bell Mobility and I started to play around with the “Mobile Internet” when I was out and about with my friends. One of the first things I noticed was that for a lot of the sites I was playing with the Information Architects were just taking the architecture of their current website and just shrinking the site down to fit into a smaller screened mobile phone. They didn’t take into consideration the context in which the majority of users were using their mobile browsers.
I was most frustrated with sport sites. If I am mobile, the most likely reason I am logging onto an ESPN.com is to check out the score of a game that is either presently being played or just recently finished. So why does it take 3 to 4 clicks to get to a sport score for a specific sport? And why, on top of that, do I have to return to the home page to follow then do the same path, but for another sport, o get up to date scores for another sport?
If an interface for the Mobile Internet is created with context in mind I find that the mobile interface can be more compelling to their desktop equivalent. This is simply because the mobile interface has to be more opinionated because it is smaller and can not have more then a single column layout.
TheScore’s Mobile iPhone Edition is the perfect example of a web interface done right. The Information Architect for the mobile interface I am assuming either is a sports fan or studied the needs of sports fans when they were away from their TV and computer.
The good thing is that I am not the only crazy one that believes that the mobile interface is not bad. AdaptivePath’s Peter Merholz recently blogged about designing interfaces and more elegantly solidified my thoughts on designing for mobile interfaces:
What we’re realizing is that the key item of concern when designing for mobile is the context in which the device is used. What this means is that discussions of “PC” versus “mobile” are misguided, because we shouldn’t be focusing on the device. We are not designing for mobile — we’re designing for mobility.
The quote is from Don’t design for “mobile” - design for mobility.


