

A few years ago, Radiohead released a video shot entirely with a 3D array of lasers rather than with lights and cameras. Now the Montreal-based band Arcade Fire has partnered with Google to promote a song using another new technology: HTML5. For bands like Arcade Fire and Radiohead, it’s about supporting their songs in new ways and reaching new audiences (we’re writing about it, aren’t we?). For Google, it’s about advancing the cause of both HTML5 and their HTML5-enabled Chrome browser.
It’s not quite accurate to call the Arcade Fire/Google collaboration “The Wilderness Downtown” a ‘video’. Directed by Chris Milk, the website is essentially a showcase of several HTML5 features. Leveraging Google Street View, the site first asks the visitor to enter their childhood address. If Street View images exist for that address (they didn’t for my childhood address in the New York City suburbs), those images are incorporated into the video – complete with panning, effects, and overlayed animation. In other words, the presentation is “geo-personalized” for each viewer (if you grew up in an area that’s been covered by Google Street View, that is). That’s cool factor #1.
Multiple browser windows opening on cue, all playing video in sync (allowing, for example, a flock of animated birds to fly from one window to the other)? Cool factor #2.
Then a window opens allowing user input and manipulation of sophisticated graphic objects via both mouse and keyboard. Since all this is implemented locally via HTML5 at the browser (rather than by some JavaScript calling back to a server), latency is about zero – it feels as if it’s running locally on an installed application (which, in fact, it is – the browser). Cool factor #3.
However, if a user tries to access the site with a browser other than Google’s Chrome, they’re presented with a warning prompt that the ‘film’ will not render properly in their browser. In my experience, while the presentation took longer to load on Firefox, I got relatively similar results, though. It leads me to question the warning, especially since according to the WC3 (the HTML5 standards organization), the browser with the most complete implementation of the HTML5 standard right now is built by – wait for it – previously standards-unfriendly Microsoft, with their just-released beta of IE9 (that this is not widely known is yet another in a series of missed PR opportunities for Microsoft).
So, OK, maybe the “Chrome only” warning is a little reminiscent of those “For best results use only <foobar>-branded accessories with your new <foobar> product” warnings – still, the loading time and overall performance with Chrome was pretty impressive. Whether it’s a fair fight – whether the site is built on browser-agnostic strict HTML5 or Google’s cheating a bit by optimizing for Chrome is another question (and not an unreasonable one – we’ve written before about Google’s big plans for Chrome to evolve beyond the role of a browser into the cloud-based Chrome operation system).
All of which speaks to a fundamental obstacle facing the adoption of HTML5 video – standardization. While the new <video> tag threatens to someday make third party video middleware such as Flash and Silverlight irrelevant, the significant hurdle of insuring compatibility across all the various browser HTML5 implementations out there remains. Further complicating things, each browser company often has its own competing business agenda. For the WC3, getting HTML5 off the ground can sometimes look like an exercise in cat-herding (in fact, there still hasn’t yet been agreement on the underlying video codec).
This is one of the primary reasons widespread adoption of HTML5′s native video tag is still a few years away.
Who’s dreading the advent of HTML5 almost as much as Adobe? Probably the web developer, who will have to test on five different browser HTML5 implementations rather than on a single Flash container.
For more on HTML5 video click here.