Yes, you'll likely still need to look at publishing with Tin Can API if you'd like to use the mobile player as described here. If you can't use the Tin Can API have you looked at just publishing with the HTML5 option enabled? Then your users could access the course in Safari on an iPad and still would allow the LMS to track elements and reporting. Here is a bit more information on distributing for Flash, HTML5 and the mobile player.
I find the HTML5 output unreliable on the iPad, with slowness, drop outs and not resuming to the right spot. The course appears to work perfectly via the app, but there's no point for us if we can't track it.
I appreciate your straight answer nonetheless. In the meantime, I'll continue to discourage our audience from using their iPads for this training until we upgrade to xAPI capability.
Are you using Storyline 2 to publish to HTML5? I've had relatively good luck with the HTML5 output on iPad. I keep modules small, avoid audio and video. I have built a few complicated assemblies that seem to run fine. Haven't noticed restore problems for quite some time.
Unfortunately, because of the way SCORM launches, initializes, and operates, the mobile player will likely never work with the SCORM API.
While the regular content pages don't appear to drop out so much with SL2, I can't say the same for the assessment. Perhaps all the variable work is maxing out Safari's memory.
Yes, I've noticed long courses (many slides) max out the suspended data, which causes havoc with resumption on any device.
The problem I have is that I've inherited these courses that were developed by an external vendor, and they are very large. I'll try to influence their paring back as much as possible, but usually the pressure goes the other way... vested interests trying to squeeze more in.
It sounds like you've isolated where some of the issues are in terms of the course, version of Storyline you're using, etc. but if you want our team to take a look to see if there is other advice we could offer in regards to the course set up or issues you're running into, we're always happy to take a look. You can send it along to our Support engineers here.
Nonetheless, I tested the course again on a later model iPad, and it worked much better. The content was still slow to load, but I didn't experience any freezing or dropouts.
Thanks Ryan for sharing here, and I do see that Renato suggested also testing your content from SCORM Cloud (and he shared a link for a version he posted there) as it's an industry standard for LMS testing. Since he didn't see the issue there, he suggested reaching out to your LMS team. Also, he did share some additional information with regards to resizing to fit the web browser window, HTML5 output does not support gestures, such as pinch-to-zoom or swipe, on mobile devices. However, the Articulate Mobile Player app for iPad is optimized to support gestures.
13 Replies
Honestly, I've never used the player for any project. I'm not sure but I don't think it does tracking at all.
If you have to deliver mobile content you need to go html5 with all its additional challenges.
Hi Ryan,
Yes, you'll likely still need to look at publishing with Tin Can API if you'd like to use the mobile player as described here. If you can't use the Tin Can API have you looked at just publishing with the HTML5 option enabled? Then your users could access the course in Safari on an iPad and still would allow the LMS to track elements and reporting. Here is a bit more information on distributing for Flash, HTML5 and the mobile player.
Thanks Jeff and Ashley.
I find the HTML5 output unreliable on the iPad, with slowness, drop outs and not resuming to the right spot. The course appears to work perfectly via the app, but there's no point for us if we can't track it.
I appreciate your straight answer nonetheless. In the meantime, I'll continue to discourage our audience from using their iPads for this training until we upgrade to xAPI capability.
Hey Ryan -
Are you using Storyline 2 to publish to HTML5? I've had relatively good luck with the HTML5 output on iPad. I keep modules small, avoid audio and video. I have built a few complicated assemblies that seem to run fine. Haven't noticed restore problems for quite some time.
Unfortunately, because of the way SCORM launches, initializes, and operates, the mobile player will likely never work with the SCORM API.
Funny you should ask Steve, because I'm testing SL2 output as we speak. (Indeed I'm on SL1, waiting on SL3 before upgrading.)
It's still awfully slow, but the drop out and resumption issues seem much better. The screen resizing doesn't seem to work though.
Perhaps with SL3 it will be another step better again!
Oops, I spoke too soon...
While the regular content pages don't appear to drop out so much with SL2, I can't say the same for the assessment. Perhaps all the variable work is maxing out Safari's memory.
Possible. Really large things seem to drag down the party.
Yes, I've noticed long courses (many slides) max out the suspended data, which causes havoc with resumption on any device.
The problem I have is that I've inherited these courses that were developed by an external vendor, and they are very large. I'll try to influence their paring back as much as possible, but usually the pressure goes the other way... vested interests trying to squeeze more in.
Hi Ryan,
It sounds like you've isolated where some of the issues are in terms of the course, version of Storyline you're using, etc. but if you want our team to take a look to see if there is other advice we could offer in regards to the course set up or issues you're running into, we're always happy to take a look. You can send it along to our Support engineers here.
Will do, thanks Ashley.
Support could not replicate the issues.
Nonetheless, I tested the course again on a later model iPad, and it worked much better. The content was still slow to load, but I didn't experience any freezing or dropouts.
This will do until we eventually upgrade our LMS.
Thanks all for your help.
Thanks Ryan for sharing here, and I do see that Renato suggested also testing your content from SCORM Cloud (and he shared a link for a version he posted there) as it's an industry standard for LMS testing. Since he didn't see the issue there, he suggested reaching out to your LMS team. Also, he did share some additional information with regards to resizing to fit the web browser window, HTML5 output does not support gestures, such as pinch-to-zoom or swipe, on mobile devices. However, the Articulate Mobile Player app for iPad is optimized to support gestures.
Yes Ashley, Renato has sent me a second email which I see is in my inbox this morning.
Glad to hear the Articulate Mobile Player app for iPad is optimized to support gestures. I look forward to using it one day.
This discussion is closed. You can start a new discussion or contact Articulate Support.