Flash Defeats HTML5 in Round One by a Knockout

Developer Chris Black made this video showing how Adobe Flash and HTML5 perform head-to-head on a simple Web animation (in this case, a bouncing ball). He uses both an iPod Touch and a Google Nexus One—the latter of which is tested both on Flash and HTML5—to test frame rate and smoothness while zooming and panning.

The results are pretty interesting. Many key figures in the tech industry, most notably Steve Jobs, have forsaken Adobe Flash, mostly used for Web video and animations, in favor of the possibility of HTML5 performing those same duties more efficiently, sometime down the road. Google's Android supports Adobe Flash, though reports on its usefulness have been mixed (most say to only use it when needed for video, otherwise load times will be painfully slow during normal use). But most people haven't seen HTML5 in action compared head-to-head with Flash.

This video shows Flash absolutely crushing HTML5 in frames per second, as well as in its ability to continue to play the animation while zooming and panning. HTML5 is consistently several times slower in framerate, and often stops completely during a zoom, not to mention requiring far more battery life than Flash.

The caveats, well laid out by Wired, are many: HTML5 is a very early project, and probably wasn't optimized properly for this test. Black even admits that some things, like "Gradient fonts, drop shadows, basic video and simple transitions are probably better suited for HTML5." But his conclusion is that HTML5 won't necessarily destroy Flash and that some applications are better suited for Flash than HTML5 (and vice versa, of course). Maybe that's why Apple allowed Adobe back into the App Store.

Dan Nosowitz, the author of this post, can be followed on Twitter, corresponded with via email, and stalked in Brooklyn (no link for that one—you'll have to do the legwork yourself).

Add New Comment

7 Comments

  • Mauricio Perez

    I wonder whether the Nexus battery died the instant the video camera finished? I would like to see some battery levels testing on both in future as this was a known issue for Flash usage on iPhones. I am hearing that Flash may be supported on iPhones soon also?

  • David Nine

    Well next time I go to a web page containing a bouncing ball, I'll be sure to use Flash.

    /

  • matt sime

    Oh come on. Don't be such a tool.

    The HTML 5 example has been cited as being "very, very, poorly coded" and there's already several examples out there showing that HTML 5 handily outperforms flash, when written by a skilled practitioner. Now, where's that "remove Dan from my RSS feed" button.

  • w

    lol.. its a bouncing ball, not a first person shooter. How poorly could anybody possibly code that ? it is too simple for code inefficiency to be a factor.

  • albie

    Spoken like a true Apple worshiper. So, you need a skilled practitioner to do anything good in HTML5? Kind of a vague statement buddy.

  • Michael Glenn

    No, spoken like a programmer. Lies, damn lies and statistics. The web is littered with "my language X beats your language Y because I code poorly in language Y". The bottom line is this is a lousy test case. If the argument is going to only be Flash is faster or HTML5/JS/SVG/Canvas is faster it misses the point that an experience tailored for mobile will win every time.