The (im)Mobility of Web 2.0 Apps
narramissic writes "So many Web 2.0 apps seem like a natural fit for use on mobile phones -- more so, in fact, than the PCs they were written for. Take for example, Google maps or Flickr or any of the myriad social networking sites. Frankly, I wonder why anyone would even want to use them while sitting at a desk. And yet the reality of using those apps on cell phones is solidly disappointing because of the inherent constraints of mobile phones and networks. This article gets deeper into the ups and downs of reworking Web 2.0 apps for use on mobile phones."
Phones, Blackberries, PDAs, and even (my personal favorite) the Nintendo DS are all restricted by a small number of buttons and tiny screen real estate. Ergo, they often need overhauls of their entire front end to accomodate touch-screens, keypads, and voice commands, AND on top of all that they need their networking kicked around a little as well to account for the possiblity of sucky/no service.
The more that laptops and wi-fi become ubiquitous, the less that people will care about using other devices for more than what they WANT to use them for. Yes, having Google Earth and an audio version of Wikipedia would rock. But I don't see it happening.
From TFA:
Browsers on the desktop have evolved along the lines of "do everything" applications, which is why the AJAX/Web 2.0 stuff kind of works in them. Lets face it, if you writing an application from scratch to do match the functionality of Google maps, say, you wouldn't start with a browser. Google maps is impressive because it actually works in a browser!
For Web 2.0 sites, 'lite' custom apps may be just the answer.
Dark Reflection
Never mind Web 2.0 apps on my mobile, I'm still waiting for Web 1.0 pages to work half decent.
For better or worse, the Web seems to have settled on a header plus the two or three column layout. On a mobile, unless the site has been optimized (which very few are) you have to scroll down through the header (where every link usually ends up being a seperate line) then through everything on the left and right before you get to the content.
Actually, in the spirit of "picture worth 1000 words," let me SHOW you what the slashdot home page looks like on my BlackBerry 8700;
the first new article is in bold below -- See how far you have to scroll to see it?