Why HTML5 is killing Flash: it’s the devices, people!

Old phone and iphoneIt’s 7 years now since Steve Jobs famously declared war on Flash in an open letter entitled “Thoughts on Flash“. With his knack for prescience, only now is it really looking like it’s lights out for Flash. In response, during the Android Keynote at Google IO 2010, Vic Gundotra cheekily declared that “it turns out on the Internet people use Flash”, that Android would still support Flash, and that it was “much nicer than just saying no”, referring to Apple’s decision not to support it. But, after five years, Flash was officially dropped from the Android platform, and since late 2011, Adobe no longer develops its mobile Flash player:

We will no longer continue to develop Flash Player in the browser to work with new mobile device configurations (chipset, browser, OS version, etc.) following the upcoming release of Flash Player 11.1 for Android and BlackBerry PlayBook.

Fast-forward to July 2017 and Adobe is putting the final nails in the coffin for Flash, albeit fairly slowly:

We will stop updating and distributing the Flash Player at the end of 2020 and encourage content creators to migrate any existing Flash content to these new open formats

Yes, Flash is dying a slow, slow death, and will no longer be distributed after 2020.

Pressure had been mounting on Flash from all sides: advertisers, publishers, and browser manufacturers. In 2015 Amazon sounded a death knell for Flash, saying that Flash based ads will no longer be permitted on its platforms from September. Use HTML5 instead, was the company’s advice.

Further woes for Flash came with the news that the Chrome browser would begin to automatically pause Flash based ads from 1st September that year. Google recommended switching to HTML5 (and indeed started to convert Flash ads to HTML5 automatically where possible). So, with Amazon’s ad network also ceasing Flash ads on that day, September 1st 2015 became something of a day of reckoning for Flash, and perhaps a day to be celebrated as a turning point in the history of the web (#FlashBegoneDay). From that day, we all started to see fewer Flash ads in our browsers.

In addition a large group of major news publishers banded together, manifesto-style, urging advertisers to deliver the final death blow to Flash, by moving away from the technology altogether. The letter listed the many benefits of moving to HTML5:

[T]he one open, industry-standard, universal format for building mobile-ready creative is HTML5.

Your opportunity has never been greater. Nearly half of the US population has a mobile phone with internet access, and one out of five pageviews on the web happen on a mobile device – a number that is growing every month.

HTML5 will enable you […] to make your creative ideas captivating on every screen, elevate your brand image, and lower your creative costs.

The letter closed off like this, with the prominence and influence of the participating publishers hard to miss:

The impact for mobile web can only be positive.

  • Performance:
    Performance was one of the reasons given by Jobs back in 2010:

    Flash has not performed well on mobile devices. We have routinely asked Adobe to show us Flash performing well on a mobile device, any mobile device, for a few years now. We have never seen it.

    Performance is still an issue. An article on the Verge lamented the crapness of the mobile web, whilst said article carried a payload of some 3.5MB, mostly pushed up by the inclusion of ads. No Flash ads means better performance all round. Amazon’s guidelines show that it takes performance seriously:

    • Console statements must be omitted to avoid verbose logging and errors in older browsers
    • Clicks are limited to three redirects
    • Ads must limit https requests to six
    • Assets must be hosted on a Content Delivery Network (CDN)
    • External CSS/JS libraries must be pulled from a server that supports gzipping
    • All code must be minified and concatenated
  • Privacy & Security:

    Security was another issues Jobs raised in 2010, saying Symantec highlighted Flash for having one of the worst security records in 2009. HTML5, being open and standardised, is suffers far fewer security issues than the closed and proprietary Flash, although let’s be fair, with access to the device hardware such as camera, microphone, and geolocation, as well as local storage, there is a lot of sensitive data accessible via the browser; complacency would be remiss. Amazon is taking this seriously with respect to ads, specifying clearly that all ads and ad-tracking must be over HTTPS, and that HTML5 APIs for accessing device hardware are off-limits:

    Accessing device API’s such as Local Storage, Geolocation, Microphone, or Camera is prohibited.

    (Although, I wonder how easy it would be to sneak something past Amazon’s auditing process…)

Why now is the right time for HTML5 to take over from Flash

Flash is history! This graph is a wonderful reminder of how HTML5 has grown over the past decade, and why Flash is no longer needed. HTML5-capable devices are everywhere; the devices are ready, people!

Number of HTML5 features supported by number of new devices released by year

Number of HTML5 features

Chart reproduced from our HTML5 support in mobile devices article, using data from DeviceAtlas.

Main image: Nick Sieger

Updated 2017/08/03 to include Adobe’s Flash end-of-life announcement

Leave a Reply

Exclusive tips, how-tos, news and comment

Receive monthly updates on the world of mobile dev.

Other Products

Market leading device intelligence for the web, app and MNO ecosystems
DeviceAtlas - Device Intelligence

Real-time identification of fraudulent and misrepresented traffic
DeviceAssure - Device Verification

A free tool for developers, designers and marketers to test website performance
mobiReady - Evaluate your websites’ mobile readiness

© 2024 DeviceAtlas Limited. All rights reserved.

This is a website of DeviceAtlas Limited, a private company limited by shares, incorporated and registered in the Republic of Ireland with registered number 398040 and registered office at 6th Floor, 2 Grand Canal Square, Dublin 2, Ireland