You have your published project, ready for mobile delivery, and you now want to know what all these output files do. What are their roles and what happens behind the scenes?

The first thing to note is that there’s no longer a player.html file for your projects. Instead, Storyline gives you three options for publishing for mobile delivery: Flash, HTML5, and the Articulate Mobile Player App. All three options are created at once and live in the same output folder, so there is no need to publish your project multiple times.

Storyline automatically decides which version to play in order for your user to view the project:

Let’s dig deeper and explore what this actually means. In your output, you will see these essential files:

• story.html – This file launches your project. It does all the work: it is the default player and identifies the user’s browser in order to determine which version of the project will play – the Flash version, the HTML5 version or, if you elected to include it, the Articulate Mobile Player App for iOS.
• story_html5.html – The user will be directed to this file if the user does not have Flash, but does have a browser that supports HTML5. HTML5 is a backup option for devices that don’t use Flash.
• story_unsupported.html – This file will launch if the user does not have a browser that supports HTML5, but has made it to the HTML5 version of the course – specifically, this file is geared for IE browsers below v9. This file provides an error message with a link to click on that then launches the user back to story.html (to successfully play the Flash version).