Give us an "HTML5-only" Publish Option

Sep 24, 2015

I've seen the staff arguments that "HTML5 is still an emerging standard."

No. It's not. It was emerging in 2008. Now it's a standard and Flash is all but dead as it is rife with security issues and unsupported on the devices that real people use most. In December 2011 (the year Adobe abandoned mobile Flash), research firm Strategy Analytics forecast sales of HTML5 compatible phones would top 1 billion in 2013. We are among a growing tsunami of companies that are looking to eliminate Flash-based content and containers as soon as possible.

I've also seen the staff arguments that "HTML5 displays differently in different browsers."

News flash; so does everything else on the web. Let us deal with that. It's what we do. It's time to give us the option to publish as HTML5 only.

31 Replies
Steve Flowers

Much of the stuff I've built over the past half-year has targeted HTML5 specifically (referencing the story_html5.html file to launch.) In almost all cases, testing cross-browser has revealed that everything works as expected in each browser tested (Chrome on Mac / PC, Firefox, Safari, Safari iOS.) I'm not using a lot of video or audio in these bits. I would guess that some older Firefox versions are going to choke on video publish.

Is there something you're seeing that works differently when published from Storyline 2?

Ashley Terwilliger-Pollard

Hi Keith,

Currently the HTML5 output is only supported in the following desktop environments:

  • Windows: Google Chrome (latest version)
  • Mac: Safari 7 and later, Google Chrome (latest version) 

As for our future plans, our team is always looking at ways to increase support for other environments and browsers. I personally like to keep an eye on this site: HTML5test.com as it helps rank the different browsers and how they'll perform.

As Steve mentioned, lots of users report success with HTML5 across browsers if they've been able to directly point to the HTML5 output. 

Daniel Sposato (Philly)

I have to agree with Steve. I have tested SL2 HTML5 output in IE, Firefox, Chrome and Safari with only minor problems that I rarely find to be issues hindering my development.

I don't understand why this HTML5 output is such a big issue with some people. It's terribly easy to separate the flash files from the HTML5 files if needed after publish. I can imagine that Captivate users would complain, as that has an HTML5 only option. But that tool sucks in so many ways! For re-usability of interactions especially! And I love a lot of Adobe applications! Just not that one.

This discussion is closed. You can start a new discussion or contact Articulate Support.