Web developers: support a mobile OS that supports the web


You know who you are:

  • You're building a mobile web app, but you're only supporting iOS and Android. Neither of which are exactly "web friendly" (I'm especially looking at you, iOS).

  • You're making a hybrid app with PhoneGap, but you're only using the iOS or Android build options. Because, well... because.

  • You see things with amazing mobile HTML5 support like BlackBerry 10, Tizen and FireFox OS and say "well, if they ever get more marketshare, we'll spend some time supporting them".

You're the "chicken" in the "chicken and egg" problem

Stick with me, this analogy holds. You know how developers like to wait for a platform to gain marketshare before they spend time supporting it? Well, that means less apps and compatible websites will launch on that platform. Less apps and websites means less curb appeal for consumers. Less consumers means... less marketshare.

Mobile OS Market Engine

By chickening out, you're


Leaving webOS, but not the Web

While at Palm and HP, I made it my mission to evangelize HTML5 app development both inside and outside our company. The very core of the webOS value proposition was the web. In webOS, mobile websites, native and web-based apps lived together in a “zen-like” harmony.

At least, that was the theory. In my two years there, I watched webOS slip from a leader in mobile web to a distant follower. I won’t elaborate much on the internal hows and whys (frankly, I doubt I even have the full story anyway), but the simple fact was I had a dramatic drop in confidence in our ability to stay relevant. All the drama in the news didn’t help, and neither did the mighty layoff hammer which eventually swung down on myself and more than half of the remaining staff.

I’ve had a couple months to relax, decompress, and