Posted by mLearnCon StaffCategories: Browser , Cloud , Development for Mobile
Mobile-optimized websites aren’t a new concept by any means. As long as there have been WAP browsers on dumbphones (like that first flip phone you thought was so high-tech back in the early 2000?s), many content providers have offered a customized experience for those devices.
With the arrival of more powerful (and sexier) devices like the iPhone and iPad, however, a new option started gaining popularity: mobile apps. Apps allowed publications like the Wall Street Journal, Time, Newsweek, and even Canadian fixtures like The Globe and Mail to deliver richer, more interactive experiences to users on-the-go. Apple’s App Store helped make apps easy to find and purchase and later adding in-app subscription payments, creating a win-win-win situation for publishers.
But native apps do pose a slight problem. iPhone apps don’t run on Android or Blackberry phones, obviously. That means publishers have to launch several different versions of their mobile apps in order to reach all mobile users. There’s also the loss of profit to consider, with both Apple and Google skimming 30% off app sales [Apple has recently revisited their restrictive subscription rules - Ed].
So what’s a publisher to do? The Financial Times figured out the answer: build an HTML5-powered mobile web app instead.
Why? Because while differences in mobile operating systems make building one app for every phone financially unfeasible, just about every current smartphone or tablet offers an HTML5-compatible web browser. By building a web app that can adjust itself to a particular device’s display, a publisher can greatly simplify its mobile development process. Web developers have, after all, been able to build self-adjusting sites which respond to a user’s screen resolution for quite some time — so achieving this on a mobilized web app is a fairly simple task.
To read more go here to the Sync-Blog.com