No -> Packaged HTML5 Apps: Are we emulating failure?

Packaged HTML5 Apps: Are we emulating failure? | groovecoder.

The simple answer is “no.” But just some nitpicks.

The Problem Is Contrived/Misapprehended 

  1. If you already have a QR scanner in place, you skip half the problem.
  2. Android?
  3. The pizza place could just have their own app, easily searchable or linked (as in the captive wifi situation).
  4. If it’s an FB, they could say, “just search for ‘incredible pizza tulsa’ to get to our FB page” in the app. It worked fine on the iOS FB app search…

Just because one place offers a sub-par way to find them on mobile FB does not mean, “apps suck!”

The Web is a Bigger App Store

Claiming that discoverability is bad on the app stores may be true; however, the Web is essentially just a bigger app store, and discoverability is worse because it’s not just apps, it is all kinds of content, much of which is not pertinent nor optimized for your device.

There are many good reasons to go native or even PhoneGap. They may not be compelling for everyone, but the reasons given in that post simply show the bias of the writer.

4 thoughts on “No -> Packaged HTML5 Apps: Are we emulating failure?

  1. Yes – I’m biased against native apps; but bias doesn’t mean mean my conclusions are necessarily wrong.

    I understand reasons for native apps; I primarily question why developers package *HTML5* apps for app stores, considering stores’ terrible app and content discover-ability. So, “to get in the app store” doesn’t make sense.

    1. Sorry for the delayed reply. Wasn’t sure if I should say anything more. But just for clarity, I was not saying that *because of your bias* you conclusions are wrong. I was saying that the reasons you offered are not compelling and offered my rationale for why that’s so. In the end, it seemed to me that it was not so much your reasons that brought you to your conclusions but rather your bias. Put another way, if we removed the reasons you offered and just asked “do you think we are emulating failure,” you would say yes because you prefer browser-based solutions.

      As for why devs package, it is partly because of usage patterns on devices. The platform is very heavily app-biased, even on Android. People are taught by the platform that the way to get things done on the device is through apps, so much so that there is a saying “there’s an app for that” that has made its way into popular culture. So when, for instance, a user wonders if her device can help her do X, her first inclination often is to search the app store for it. And only if she doesn’t find something satisfactory will she extend onto a Web search.

      There is also a matter of app feel. Because the devices are app-biased, people become accustomed to that, so they learn to want, or at least to expect, to use apps for things rather than Web sites for things. And the “Add to Home Screen” experience rarely, if ever, stacks up/feels as right as something that is packaged as an app.


      1. I recounted a “there’s an app for that” experience, and it sucked compared to a plain old web experience. That consumers expect these crappy experiences is precisely the problem – because developers package HTML5 apps and don’t put any effort into a plain mobile web experience.

        Sure it’s “just one place” but I’d bet if you put the majority of app experiences up against plain web experience, the web would win – if developers would actually use 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