Restricting course navigation
Feb 04, 2013
Hello,
Just getting my feet wet in Articulate and have an issue I'm hoping to get some help with.
My course needs to have the following criteria:
- scenesdo not change until audio voiceover ends, next button not available to skip pre-maturely
- questions are intermittently placed throughout about 150 scenes
- once a question slide comes up, the user should then be able to use the 'back' and 'next' buttons to move through the course to review the material, but not be able to click 'next' to move past that question screen
I've found that through the 'Player' you can remove the Menu and can pick scenes and set them as 'locked,' to not allow the user to move through the course until the trigger allows it.
Any way to allow going back and forth once a question is reached, but not move past it?
Thanks for the help!
Luke
54 Replies
Excellent, excellent...
It is important for me to have my player restrictions enforced as my users are required to view every slide completely and in order to accurately complete the course in my company's eyes.
As a result, would you say that Flash is the only method of publishing that I can have full confidence will enforce my player restrictions, and as a result, would iPad be out as an option?
I'm looking at the Publish screen in my Storyline.
Is Flash assumed as the method of publishing?
And if I un-check the "Include HTML5 output" option that will remove the ability for my viewers to access the course on mobile devices?
But leaving the "Use Articulate Mobile Player on iPad" selected will mean the user that accesses their welcome email from their iPad will be prompted to download the app and if they use that app, the version of my course they will encounter will have the player restrictions active?
I think I'm a bit confused by the chart you show in the above link (here), why does it have a listing for both HTML5 and Mobile, I thought that "You can choose Include HTML5 output to let learners view content on mobile devices that don't support Flash."
Stated in this tutorial:
http://community.articulate.com/tutorials/products/publishing-a-project-for-ipad-or-html5.aspx
Hi Luke!
Okay to understand how Storyline determines which version of your content to display when users view it, check out this article.
When you see HTML5 vs Mobile, here is a better explanation of that:
I think you are understanding how all of this works, but let me know if you have further questions now.
Thanks so much and have a great day!
Hi Luke,
In the chart that Leslie references, the "Mobile" refers to the Articulate Mobile Player - Mobile just fit better in that column. The HTML5 output will allow users to view it on their iPad in their browser window (with the browsers referenced here for HTML5). Hope that helps clarify!
This discussion is closed. You can start a new discussion or contact Articulate Support.