Mobile apps — We’re doing it all wrong!
Posted in Apple, Palm, iPhone on August 2nd, 2009 by Bencredible – 3 CommentsI think Apple had it right back in the iPhone 1.0 days: Apps are web sites. Conventional wisdom would say that I’m wrong, I mean look at the popularity of the App store. However, iPhone apps are just that: applications for the iPhone (and sometimes the iPod Touch.) What about all the other devices out there?
In an ideal world I could develop an application for the web and have it deploy to any mobile device from an iPhone to a Blackberry to a Windows Mobile device. The web browsers in these devices are actually quite powerful. Take a look at Google Latitude to see what I mean.
The problem is that since we have native apps there is little to no reason to develop a standard to pull the device hardware forward to the web browser. If I want to develop an application that can utilize the tilt sensors in an iPhone and a Blackberry I would have to write different code for each. That’s not the ideal solution. Each device should be able to present its hardware to the browser in a standard way that anyone can take advantage of. And nearly all hardware should be available from the on-board sensors, GPS, phone, ambient light sensor, etc., etc.
Looking at 99% of the iPhone apps out there I see little to no work that could not be done in the browser should they be able to take advantage of all the hardware. The final piece of the puzzle is an offline mode for apps that require heavy animations for weather and whatnot that allow the app to run even when there is no bandwidth. A giant cache folder as it were.
This is a bit of an idealistic view of how things should run. Apple already tried it once and failed. I don’t think they were wrong, I just think they were early without enough tools. Hopefully someone will try again but this time make it a standard that will work on any device with a webkit browser at its core.
There is one aspect that I have not figured out how to run in a browser: 3d games. I have yet to figure out a workaround for those.
What do you think? Am I crazy or could this someday be the future of mobile computing?
