Apps v. Websites: Ultimate showdown in the mobile browsing era
by Liz on Sep.27, 2009, under Web Development
I was looking at my iPhone the other day when I was in a particularly bad dead zone, and thought to myself “Wow, I don’t have much to do that’s not Internet-required”. Other than a few games and stanza, it appears most of my apps are simply an interface for a single website.
As I thought about the implications of this, I realized that the line separating webapps and desktop applications has blurred. I use mint.com to manage my finances, and facebook to manage my social circle. I use google docs to deal with my documents and gmail.com to manage my e-mail. All of it, since gmail can check other POP-enabled accounts.
Now, to look at it another way- there are many thousands of apps in the App Store in iTunes, but the Pre and Blackberry have disappointingly low figures. Of course, the iPhone has been around longer than the Pre, and it has a larger, more technically-capable cult of followers than the business-centric Blackberry, but the real reason is that developers simply haven’t had enough time to learn an entirely new SDK, and why would they want to?
The simple solution is to develop an application that is cross-device compatible- a webapp. Something they have only to fire up their browsers to get to, it increases the user base of your application to anyone with a portable connection. The roadblock? Session Management.
The biggest problem with the iPhone, Pre and Blackberry (less so with android phones, but a problem nonetheless) is that it can’t carry data past more than a few webpages. The choice to use a webapp is simple when you don’t have to login- you can store everything in the URL variable scope. When users have to access personal information, or verify their identity (for purchasing things perhaps?) the choice to use cookies, or session variables is one that is difficult to make. When you want your users to spend time using your site- increasing their exposure to your brand and maximizing revenue potential- you need to bite the bullet and write a device-specific application. When you only need to provide data in short bursts (like twitter, or meetways) you can afford to make a smaller, data-optimized version of your website.
