Even if HTML5 doesn’t actually give you much, its buzzword status could still help you deliver a better UX
November 22, 2010
Sheesh, there’s a lot of HTML5 talk these days. I was initially confused and disappointed by HTML5’s buzzword status, until I realized that its very buzzword existence could ultimately help me deliver a better user experience.
The Canvas tag makes a game like Agent 008 Ball awesome — but a productivity app, maybe not so much
Each time I hear someone tell me that HTML5 the answer to, say, the challenge of developing mobile clients for multiple platforms, I have to wonder if they have actually reviewed the set of technologies actually comprising HTML5. On its face, HTML5 would seem to mean very little for a productivity app like Cozi.
- The most immediately useful aspect to Cozi is probably the <audio> tag for the few situations in which the Cozi web application plays a sound. We currently do that with Flash, and it’d be nice to jettison that baggage. Audio is not a big deal for us, however.
- Offline storage? Maybe. The cynic in me is betting that, once we begin investigating this, we’ll discover that HTML5 offline storage solves 70% of what we want. Still, this is somewhat interesting.
And, from what I can see, that’s about it for Cozi. I’m missing the magic of the rest.
- The <canvas> tag is a huge step forward for slick graphically-intensive apps like Agent 008 Ball, but I’m not seeing the big breakthrough for an app that can already render everything it wants with native HTML elements.
- We don’t do much with video.
- Drag and drop. This is only interesting if you believe that drag and drop is an intuitive and convenient UI for moving files. My own belief is that users would benefit much more from optimized modal UIs designed for common tasks like picking photos. (The File Open dialog could start out showing the user’s actual photo storage location, show thumbnails by default, the dialog could allow multiple selection across multiple folders, etc.)
- The pile of new tags of purportedly general utility like <section> or <figcaption> solve no problem anywhere on our list of the 50 Biggest Problems We Have. What would really help instead would be a framework by which different communities could define new domain-specific tags that solve domain-specific problems. Hence my investment of time and labor in the QuickUI web control framekwork.
“But wait!” cry the poorly-informed or deliberately overexcited HTML5 buzzword-pushing media. “What about animations? And things with rounded corners and drop-shadows? And embedded fonts? And single-page applications? And increased standardization? Those things are all revolutionary!” Yes, they are—and all those things were possible before HTML5.
There are however, some very important second-order benefits of HTML5:
- The relentless repeating of the HTML5 buzzword may have the beneficial side-effect of finally giving consumers a way to evaluate whether, for example, the latest mobile phone they’re considering buying is going to provide them a good browsing experience. “I’ve heard that I need HTML5. Does this phone has HTML5?” It doesn’t matter that the literal interpretation of the question is probably not what the consumer cares about; the question’s answer may still give the user what they want. We might finally see consumers and IT departments wake up and jettison their ancient copies of IE in favor of a modern browser on a reasonable upgrade cycle.
Of course, I’m sure there are many web applications that will directly benefit from HTML5 in ways that completely change their business. They must be very happy. For now, my company probably isn’t one of those beneficiaries. Still, the above second-order effects of HTML5 might eventually allow me to deliver a better user experience to more users. If that means reducing HTML5 to a buzzword, I’m all for it.