The Death of Flash
In 2010 Steve Jobs posted his manifesto “Thoughts on Flash” as a response to the criticism of Flash not being available on Apple portable devices. In this document, he calls out Adobe to switch from focusing on Flash in order to make money to “creating great HTML5 tools for the future”. Seven years later Adobe finally grants him this wish by announcing that they will stop updating and distributing the Flash Player in 2020.
Macromedia Flash 1.0 was launched as a rebrand of its precursor, FutureSplash Animator. What started out as a graphic and media tool became the standard for interactive web applications. In 2005 more computers had Flash installed on it than Java or Windows Media Player. In the same year, Macromedia was bought by Adobe. This included their product line of Flash, Dreamweaver, and Shockwave. Adobe continued to develop these products and tried to maintain its position by bringing out two major releases of Flash based on the ActionScript 3.0 language.
Flash Security Concerns
However, it wasn’t the open standards that killed Flash. Security, performance, and battery life issues were the main challenges that caused it to be dropped by users. In 2015 Flash was identified as providing 8 of the top 10 security vulnerabilities. This includes severe breaches such as arbitrary code execution and even hacking webcams. These vulnerabilities led to Facebook and Google gradually replacing Flash on their sites with HTML5 in 2016.
So is Flash completely dead? No. There are still people that (have to) use browsers that don’t score high on the HTML5 compatibility scale. With the tech giants making the switch it will, however, trigger more people to upgrade operating systems and browsers, further lowering the dependency on Flash going forward.
If you’re still running parts of your web ecosystem in Flash it might be smart to not wait until 2020 to migrate to HTML5 standards. The time to move is now, and if you haven’t you risk a degradation in customer experience or put yourself at a significant security risk. At Sogeti, we can help you make this transition, or look at the options for moving your web applications to full web CMS solutions.
Michael Feith is a digital solution architect at Sogetilabs. Read more Sogetilabs blogs here.