Mobile Web Apps vs. Native Apps

February 1st, 2011 7 Comments

And so begins the next development war.

37 Signals officially announced Basecamp Mobile today, and gasp, it’s a mobile web app, not a native one or ones.

Launch: Basecamp Mobile

Sure, 37 Signals isn’t the first company to make this decision, but they are well-known and well-respected for both their development chops and their relentless pursuit of simplicity.

So, this is a kind of a big deal among web developers.

The reasoning is sound, but of course, developers immediately began taking sides over Twitter and in blog form.

Unsurprisingly, DHH (@dhh) had the following to say in short form:

Taking your web app mobile just for iOS in 2011 is like taking your business to the web just for IE4 in 2001.

I happen to agree with mobile web development over native development, and I’m not alone.

This marks the beginning of what will be the development equivalent of a land war in Asia.


Possibly Related Posts

7 Responses to “Mobile Web Apps vs. Native Apps”

  1. Jason Grigsby Says:

    The only quibble I have is that this isn’t a new debate. It’s been going on for quite some time. 🙂

  2. Tweets that mention Mobile Web Apps vs. Native Apps | The AppsLab -- Says:

    […] This post was mentioned on Twitter by Jake Kuramoto and theappslab, Abdul Jaleel K.K. Abdul Jaleel K.K said: Mobile Web Apps vs. Native Apps […]

  3. Jake Says:

    True, but until semi-recently, the sides weren’t nearly as even. HTML5/CSS 3 and JS match up nicely with native toolkits.

  4. uvox Says:

    Definite advantages to web apps in the enterprise space as the mobile version needs to integrate with a suite, app server, database, etc. The question would be how easy it would be to leverage device features such as cameras for OCR, geo-location, audio controls and so on. Maybe it’s becoming easier.

  5. Jake Says:

    Well, if REST APIs exist, native toolkits are just as easy as mobile web apps. Data access is on the backend system.

    Mobile web apps can access some hardware controls with HTML5, and this is improving. However, native is still better, but the problem there is developing on different platforms. Tools like PhoneGap and Appcelerator are a must if you want to build for multiple platforms.

  6. Gary Myers Says:

    “The end goal is that we’ll be able to develop one version of Facebook for mobile devices, that runs on all different kinds of mobile phones. That’s really where our focus is now.”

  7. Jake Says:

    Yup, Facebook will be testing the HTML5/CSS 3 waters. I expect them to hedge their bets with iOS and Android native apps, but the lack of a good mobile Facebook for BlackBerry, Symbian, etc. is a gap they need to fill w so many users.

    I tend to agree with a mixed strategy.

Leave a Reply