We have provided courses to clients with a variety of LMS systems. Today we have a client whose LMS is not directing iPad users to index_lms_html5.html. Therefore their courses are opening in Safari with a less than satisfactory performance. Is there anything we can do to circumvent this - such as changing the directory in the manifest file to ioslaunch.html?
What's the launch file you're currently pointing to for the entire course? It's often index.html - and that should launch the course within the HTML5 output in Safari or the Mobile player if you've enabled both and the user is accessing on a device that supports it. Also within the mobile player you will want to look at the publishing LMS option you choose, did you publish for Tin Can API?
As for all the other questions you asked, yes this was published for AMP - because that is the desired outcome. Story.html is the default link we use outside of an LMS. The manifest file that SL produces points to index_lms.html by default. That manifest is what the LMS is using, and it is opening the modules within the browser window without prompting the AMP download in the way that it would outside the LMS without the manifest file.
Take a look at this article to understand how to best publish your mobile content.
The TinCan API that Ashley mentioned above is needed for tracking via LMS and the Articulate Mobile Player. Otherwise, we recommend to just utilize HTML5.
Thank you Ashley. We figured out that TinCan is the secret to get the AMP prompt. Unfortunately, since the last post we have discovered that the client's LMS does not support TinCan. It looks like they will be stuck viewing the module in Safari with less than satisfactory performance. (We design custom pause/play interfaces and I'm sorry to say, but the HTML5 output doesn't handle it well on the iPad.)
How are you setting up the custom play/pause? If you'd like our team to take a look at it, we're more than happy to investigate further and help determine if it's an issue with the set up, a Storyline bug or an expected behavior based on a mobile browser. You can upload files to our Support team here, and they're accessible 24/7.
We pause like this: Show layer. On that slide layer - "Pause timeline of base layer" The behavior is flawless everywhere but in Safari on the iPad. There are other performance problems we have noted that AMP takes care of. That is why we prefer our client's use it.
Thanks Lilian, for sharing - I see a few issues we've reported to our team about the pause base layer setting and HTML5, and I'd want to confirm if what you're seeing matches that behavior or if it's something new. Could you share just one of these slides so that I could take a look at how you've set everything up and do some testing around it?
7 Replies
Hi Lilian,
What's the launch file you're currently pointing to for the entire course? It's often index.html - and that should launch the course within the HTML5 output in Safari or the Mobile player if you've enabled both and the user is accessing on a device that supports it. Also within the mobile player you will want to look at the publishing LMS option you choose, did you publish for Tin Can API?
Please explain about TinCan API.
As for all the other questions you asked, yes this was published for AMP - because that is the desired outcome. Story.html is the default link we use outside of an LMS. The manifest file that SL produces points to index_lms.html by default. That manifest is what the LMS is using, and it is opening the modules within the browser window without prompting the AMP download in the way that it would outside the LMS without the manifest file.
Hi Lilian -
Take a look at this article to understand how to best publish your mobile content.
The TinCan API that Ashley mentioned above is needed for tracking via LMS and the Articulate Mobile Player. Otherwise, we recommend to just utilize HTML5.
Thank you Ashley. We figured out that TinCan is the secret to get the AMP prompt. Unfortunately, since the last post we have discovered that the client's LMS does not support TinCan. It looks like they will be stuck viewing the module in Safari with less than satisfactory performance. (We design custom pause/play interfaces and I'm sorry to say, but the HTML5 output doesn't handle it well on the iPad.)
Hi Lilian,
How are you setting up the custom play/pause? If you'd like our team to take a look at it, we're more than happy to investigate further and help determine if it's an issue with the set up, a Storyline bug or an expected behavior based on a mobile browser. You can upload files to our Support team here, and they're accessible 24/7.
We pause like this: Show layer. On that slide layer - "Pause timeline of base layer" The behavior is flawless everywhere but in Safari on the iPad. There are other performance problems we have noted that AMP takes care of. That is why we prefer our client's use it.
Thanks Lilian, for sharing - I see a few issues we've reported to our team about the pause base layer setting and HTML5, and I'd want to confirm if what you're seeing matches that behavior or if it's something new. Could you share just one of these slides so that I could take a look at how you've set everything up and do some testing around it?
This discussion is closed. You can start a new discussion or contact Articulate Support.