Why Apple’s Failure with iPhone Web Applications Doesn’t Matter
Here is the story many people would like you to believe:
Apple told developers that the only way to build applications for the iPhone was to use web technology. Developers didn’t go for it so Apple eventually caved and created the native iPhone SDK.
Ergo, attempts like those by Google to make mobile web applications the centerpiece of a mobile strategy are doomed to fail.
Wrong! Apple’s failure with iPhone web applications does not matter when it comes to the future of mobile web applications.
Here’s why Apple’s experiment wasn’t a good test:
- Apple’s web-only development wasn’t mobile — Not in any way. There was no access to geolocation, accelerometer, offline mode, or the camera. The only thing mobile was the fact you were constrained to a small screen.
- Apple’s own apps weren’t built using web technology — “Do as we say not as we do” didn’t go over well with developers. If you’re going to make the argument, you need to lead by example like Palm has.
- HTML 5 Capabilities were not available — In the time since Apple’s experiment, browsers have started to expose things like offline support and geolocation that are essential for mobile.
There are good arguments to be made for why mobile web applications may not succeed. I may not agree with them, but I can acknowledge their logic. And for a whole host of immersive applications like games, I can readily acknowledge that mobile web applications will likely never make sense.
But to use Apple’s flirtation with mobile web applications as the foundation for an argument that mobile web applications will never take off is akin to looking at the success of web browsers on WAP phones and arguing that iPhone users will never use their browser.