If you need to access your courses in the mobile player, you'll need to publish with Tin Can API and ensure that your LMS supports it. If your LMS does not support it, you can still access the content in the HTML5 output using Mobile Safari by publishing with your SCORM option. Please check out this tutorial on Publishing a Course for Mobile Devices for more information.
If you're needing to deploy the course on mobile devices are you able to use the HTML5 output? If so, you could choose that as a publishing option, and publish with any of the SCORM options and just don't select the checkbox for the Mobile player. When users access your course on a supported devices/browser detailed here they'll be shown the HTML5 output and able to navigate through the course normally.
If your LMS supports Tin Can API, you can choose to publish for the Mobile player and HTML5. When this happens, the user will be able to access the course in the Mobile player again on supported devices, and if they are on another device that does not support the mobile player or have Flash, they'll be directed to the HTML5 output.
Here’s how Storyline determines which version of your content to display when learners view it:
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.)
SCORM and Tin Can can both track the course in terms of users answers and the elements reported to an LMS, so I'm not sure I'm clear on the set up that would require both? If we're misunderstanding something or you have a more unique situation in terms of needing dual tracking, you are welcome to share additional details and specs here so that the community could help you find a solution outside the built in functionality of Storyline.
5 Replies
Hi, Vicente -
I wanted to let you know that there is not an option to publish for SCORM and Tin Can simultaneously.
Then, ¿I only have the option to offer two courses, one for desktop and one for tablet?
What is the best e-learning platform that recommended for Storyline?
Hi, Vicente -
If you need to access your courses in the mobile player, you'll need to publish with Tin Can API and ensure that your LMS supports it. If your LMS does not support it, you can still access the content in the HTML5 output using Mobile Safari by publishing with your SCORM option. Please check out this tutorial on Publishing a Course for Mobile Devices for more information.
Thanks, but it's a big problem for me if I can't offer to my clients multiplatform courses. :-(
Hi Vincente,
If you're needing to deploy the course on mobile devices are you able to use the HTML5 output? If so, you could choose that as a publishing option, and publish with any of the SCORM options and just don't select the checkbox for the Mobile player. When users access your course on a supported devices/browser detailed here they'll be shown the HTML5 output and able to navigate through the course normally.
If your LMS supports Tin Can API, you can choose to publish for the Mobile player and HTML5. When this happens, the user will be able to access the course in the Mobile player again on supported devices, and if they are on another device that does not support the mobile player or have Flash, they'll be directed to the HTML5 output.
Here’s how Storyline determines which version of your content to display when learners view it:
SCORM and Tin Can can both track the course in terms of users answers and the elements reported to an LMS, so I'm not sure I'm clear on the set up that would require both? If we're misunderstanding something or you have a more unique situation in terms of needing dual tracking, you are welcome to share additional details and specs here so that the community could help you find a solution outside the built in functionality of Storyline.
This discussion is closed. You can start a new discussion or contact Articulate Support.