The Annoying iPhone App Process Was All Part of Apple’s Master Plan To Make Developers Build Web Apps

Steve Jobs with iPhone
Robert Scoble just Sc-c-c-cobleized us with this post speculating that iPhone app developers, fed up with the App Store approval process, are abandoning apps in favor of websites that do the same thing.

Lately I’ve noticed that some developers are avoiding building apps and, instead, are building custom web pages that are designed specifically for the iPhone. [...] Yesterday another one came along from Nextstop, which is a cool new app for sharing cool things to do near you (great for travelers to check out) and they, too, decided on HTML5 instead of doing an iPhone app.

Some reasons Nextstop likes HTML5:

1. Rapid iteration. If they code a new feature tonight, you get it tonight. No waiting three weeks for you to get their latest.
2. It prepares their systems for building a native app. Why? Because apps can include a Safari browser instance inside, so all of this work is reusable, even if they do a native app.
3. It’s easier to build and debug because you don’t need to do a lot of specialized coding to make the native app work properly.
4. It fits into the greater web easier for users. In an iPhone app it can be jarring to take users out to a web browser, but if they already are in the browser they are used to going to other pages and back again using Safari’s navigation.

That sounds like a really great idea, doesn’t it. You know who else thought so? Steve Jobs:

WWDC 2007, SAN FRANCISCO—June 11, 2007—Apple® today announced that its revolutionary iPhone™ will run applications created with Web 2.0 Internet standards when it begins shipping on June 29. Developers can create Web 2.0 applications which look and behave just like the applications built into iPhone, and which can seamlessly access iPhone’s services, including making a phone call, sending an email and displaying a location in Google Maps.

But then the developers were all like, “Nooooooooo!” and Apple was all like, “Fiiiiine!” in October 2007 and announced a way to build native apps. But submitting an app to the App Store and going through the approval process is annoying as hell for developers, so they’re getting around that by doing what Apple wanted them to do anyway in the first place.

That Steve Jobs sure is a crafty one.

    • http://www.iphoneappdeveloper.com/ iphone app developer

      Yeah steve is crafty but there are still plenty of loyal app developers making plenty of $$ taht will not abandon the app store or their iphones.

    • http://www.iphoneappdeveloper.com/ iphone app developer

      Yeah steve is crafty but there are still plenty of loyal app developers making plenty of $$ taht will not abandon the app store or their iphones.

    • airmanchairman

      Solid, valid point!!!

      I for one am sure glad that at least one developer/blogger/technophile has enough memory in his buffer to recall the “Web apps only” directive Steve Jobs made on introducing the iPhone, to a terrifying chorus of vehement disapproval from the developer community.

      In the long run, once the obstacles of rich input, 3D graphics, sound and video etc have been technically overcome, the Web will be the way to go. Till then, its the App Store way or the digital highway…

    • airmanchairman

      Solid, valid point!!!

      I for one am sure glad that at least one developer/blogger/technophile has enough memory in his buffer to recall the “Web apps only” directive Steve Jobs made on introducing the iPhone, to a terrifying chorus of vehement disapproval from the developer community.

      In the long run, once the obstacles of rich input, 3D graphics, sound and video etc have been technically overcome, the Web will be the way to go. Till then, its the App Store way or the digital highway…