iPhone ‘Application Development’

John Gruber made some excellent points regarding today’s 2007 WWDC Keynote presentation. I would like to add a few more points regarding the business impact of Apple’s announcement.

Apple recently announced that iphone application development will be done as web 2.0/ajax applications instead of embedded, native applications.

For some classes of applications this makes sense, but the problem that I see comes with applications that use persistent storage. Although there are ways to provide persistent storage using javascript, these methods all use the web browser’s cache, which means that your users can inadvertently wipe their application data by clearing their browser cache.

Any developers wishing to work around this basically end up having to provide a server back end to persist user data.

The business impact of this is a shift from a software sales model to a service provider: instead of just writing, testing, and selling your applications you are now forced to provide a 24/7 network infrastructure for hosting your web service back end and user database, along with 99.999% availability.

Also, commercial applications based on service oriented architectures lend themselves best to a subscription model instead of regular license sales, which just means added headaches.

Obviously this is a non-issue for standalone widgets that pull down data from existing websites, such as imdb, but if you are an indie developer with an eye towards developing sophisticated handheld applications for the iphone this is a much bigger pill to swallow.

One Response to “iPhone ‘Application Development’”

  1. Soft Arts » Blog Archive » Web Apps Versus Native Apps Says:

    [...] iPod Touch in February 2008, and I think that it’s great, great news. Although I have my own opinions on the matter I have by and large tried hard to stay out of the bitchcraft most people have been practicing about [...]

Leave a Reply