We are currently creating courses in the Articulate Storyline 2 version. Having done this , within the LMS then all options within the publishing for HTML 5 and all mobile devices is selected with the TIN CAN API version.
The courses run first by default is the Flash player and if one is not installed within the browser, then it would run with HTML5.
Is there is way that we could have it the other way round instead?
Learners will see the Flash version of your course if their browser supports it.
If learners are using iPads or Android tablets and you selected the Articulate Mobile Player (AMP) option when you published, the course will launch in AMP. (If they don't have the app installed, they'll be prompted to install it.)
If learners are using iPads or Android tablets and you didn't select the AMP option when you published, but you did select HTML5, the HTML5 output will launch in their mobile browser.
If learners are using a browser without Flash and you marked the HTML5 option, they'll see the HTML5 output. (For a list of supported browsers, click here.)
Is this something that has to be done within the code where it says "point directly to the story_html5.html file within your published output" and then the user would have HTML5 by default? This means it would work even if the user has a flash supported browser?
4 Replies
Hello Anjali,
Unfortunately there is not a way to reverse the way this works.
Here’s how Storyline determines which version of your content to display when learners view it:
Thanks so much Emily!!
Hi Emily,
Just a small question again regarding my above question:
I cam across a discussion where Ashely answered: https://community.articulate.com/discussions/articulate-storyline/html5-output-with-flash-why
Is this something that has to be done within the code where it says "point directly to the story_html5.html file within your published output" and then the user would have HTML5 by default? This means it would work even if the user has a flash supported browser?
Thanks again!!
Anjali,
You could direct users to the .story_html5.html file from the output, however this would need to be accessed on one of the supported browsers.
This discussion is closed. You can start a new discussion or contact Articulate Support.