HTML vs. Native Apps: The Jury is Still Out

Allow me to disagree with my esteemed colleague.  A few thoughts–just my opinion. He echoes another article I read recently (can’t find it now) that basically argues against native and for HTML5-based apps. I’ll offer a few points to the contrary here.

First, you don’t need a plugin for native phone apps, and often native apps run more smoothly. They also still tend give you a better chance of being discovered than, e.g., a pure Web search. AND, with a native app, you can get both Web coverage (host a Web page talking about and linking to it in the app store) and whatever app store coverage you get.

Another point in native app’s favor is that they tend to be optimized for particular platforms from a Design perspective, i.e., they feel native, they feel like the experience that the platform promises–the one that the person decided to buy over the others. They are also (usually) consistent, following platform patterns.  These points are not typically true for Web apps–especially since a major benefit (from the app creator’s perspective) is the whole “write once run anywhere” thing, so you end up with a vanilla app experience that is either native for one platform or for none.

About IE10 and HTML5–it’s not going to be immediately adopted. It’s not clear when, for instance, touch/gesture support will be pushed out to WinPhone yet. Even then, it will take some time for folks to update their phones, and you can’t effectively “be sure” it is there for some time yet.

This adoption problem is much more an issue on desktop. Saying HTML5 doesn’t require a plugin doesn’t tell the whole story because it requires a current browser, which for all intents and purposes serves the same function as a Silverlight or Flash plugin–the user has to have special software installed to use it.  And both of those plugins have much more of an install base right now than HTML5, and will for some time yet (a long time, in software years).  It would be very surprising to see major enterprises all moving to IE10 right away.  It would be nice, but I’m not holding my breath.

Three years from now, maybe it will be true that HTML5 is the obvious winner on the desktop, but I’m still not convinced it will ever be on mobile devices.  Most likely, the best strategy will be to come out of the gate with a mobile Web app OR choose a platform you think gives you the best bang for your buck initially, and then you can fill in the gaps (either building native for other platforms or Web app for your non-primary target).

Just my 2c.

2 thoughts on “HTML vs. Native Apps: The Jury is Still Out

  1. hi,

    this debate of native vs web, maybe is a false question and the question is about what tools to use for developing mobile apps. i would like to see a large investment in tools that could help developers to develop apps that run in any device.


    1. I agree it would be nice, but honestly, I think that’s a pipe dream.

      1) It’s pretty hard to keep tooling up to date with platform changes.
      2) It could easily make developing an app 10x harder, trying to deal with all the different form factors, styles, interaction patterns, and contexts of use in one app.
      3) The platform vendors don’t have much motivation to support it.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s