Google Chrome moving to HTML5 by default. Flash to be hidden on browser by end of the year.
Google recently announced that they will be killing/eliminating Adobe Flash within the year. I am wondering what Articulate is doing to prepare for this change that may have a major effect on so many e-learning courses designed and developed in Storyline. Will Storyline courses accessed using HTML5 soon look and behave the same way the Flash version does? When this change does happen within Google Chrome, will users be prompted to to use the Flash version OR will Chrome see that there is an HTML5 version and just auto load that version instead?
I have seen the "Comparing Flash, HTML5, and Articulate Mobile Player Output for Articulate Storyline 2" page, but I have found many of my Storyline projects do not look or behave the same in HTML5 as it does in Flash. For instance, the images (both created images and images from a screen capture) look fuzzy in the HTML5 output. Font titles and buttons in the Player look distorted. Videos inserted from a screen capture get distorted in HTML5. Features such as rollover hyperlinks, text interactions, previous/next buttons within a lightbox, ect. all do not work or do not work as they are designed when using the HTML5 output.
The company I work for currently has 9 Storyline 1 and 9 Storyline 2 licenses. We have produced literally hundreds of e-learning content in Storyline for customer consumption. Please let me know what we can expect as a response from Articulate due to this change within Google Chrome.
I can offer screen shots of the differences and can go into further detail on the issues I experience from the HTML5 output versus the Flash output if someone would like to talk to me about it.
Per the System Requirements, HTML5 currently does not work in Internet Explorer, Microsoft Edge, or Firefox. Soon HTML5 is likely all that will be supported by Chrome. Please let the Articulate Storyline community know what the company is doing to ensure compatibility among both browsers (IE, Firefox, Chrome, etc) and publishing outputs (Flash, HTML5).