Both our content and the test Solar System content reports back to the LMS, but we don't see any communication from the Articulate Mobile application on the iPad. The ipad does not send a REST request for any communication. We are running the latest version of the mobile software.
Articulate Mobile App player is essentially a Flash Player. As you know, Apple does not allow the Flash Player (a plug-in) on their devices or on the mobile version of Safari. Secondly, SCORM is Javascript and needs a browser to communicate back to an LMS.
There are alternative ways to track from the Articulate Mobile App player via the xAPI (TinCan) or another custom mechanism, but it's not something 'out-of-the-box' with Storyline.
One way would be to publish your content as HTML5 and have users access the LMS from the Safari or Chrome browser. Still, this would require additional programming. It's an Apple thing, not a Storyline thing.
Others may have experience or options that may work for you though.
Hi Jordan! Looks like Kevin has jumped in to assist you here, but I wanted to take a moment to welcome you to E-Learning Heroes
A note regarding LMSs
Articulate Mobile Player content will be tracked and reported in your LMS if you published for Tin Can APIand your LMS provider has implemented Tin Can API support. In fact, if you published for Tin Can API, learners will be able to switch between all output formats (Flash, HTML5, and Articulate Mobile Player) without losing their progress or results.
If you published for SCORM or AICC, your LMS won't be able to track or report Articulate Mobile Player content. If you need to track the results of your LMS courses, we recommend that you don't include the Articulate Mobile Player option when publishing. Or, encourage your LMS provider to support Tin Can API. (Our white paper on Tin Can API implementation provides helpful information for your LMS provider.)
If you publish for SCORM or AICC and you don't need to track learners' progress or results, you may still be able to view content in the Articulate Mobile Player. Some learning management systems will allow it, while others won't. You'll need to test your content in your LMS environment to determine if it'll allow viewing SCORM or AICC content in the iPad app.
I think your answers are conflicting, or maybe I don't understand. We are developing an LMS to support the TinCan API. During testing we don't see any communication coming from the iPad app. The app does load the content, but there is no progress communication.
Does the Articulate Mobile Player support the TinCan API?
Hi Jordan! Did you publish your content for Tin Can? As for developing your LMS and how that works, I would not be able to help you with, but perhaps someone in the community will.
Yes, the content is published for the TinCan API. We don't need help developing the LMS, but just need to understand if the Articulate Mobile Player app supports tracking with TinCan.
I seem to be having the same issue as Jordan. We have extensive experience with Articulate and Storyline. In launching and looking at the story_html5.html and the ioslaunch.html files, they do not have any calls to the Story.js file which contain the means for a statement to be sent to our endpoint.
In monitoring the traffic from the iPad app which was launched with a fully formulated tincan API structure, played on the Articulate iPad app, we saw there was none. No calls what so ever from the app to the endpoint.
Story line Update 4 1311.1422 is the version we are using. Is something getting stopped when the app is opened?
8 Replies
Hi Jordan and welcome to E-Learning Heroes!
Articulate Mobile App player is essentially a Flash Player. As you know, Apple does not allow the Flash Player (a plug-in) on their devices or on the mobile version of Safari. Secondly, SCORM is Javascript and needs a browser to communicate back to an LMS.
There are alternative ways to track from the Articulate Mobile App player via the xAPI (TinCan) or another custom mechanism, but it's not something 'out-of-the-box' with Storyline.
One way would be to publish your content as HTML5 and have users access the LMS from the Safari or Chrome browser. Still, this would require additional programming. It's an Apple thing, not a Storyline thing.
Others may have experience or options that may work for you though.
Hi Jordan! Looks like Kevin has jumped in to assist you here, but I wanted to take a moment to welcome you to E-Learning Heroes
A note regarding LMSs
Articulate Mobile Player content will be tracked and reported in your LMS if you published for Tin Can APIand your LMS provider has implemented Tin Can API support. In fact, if you published for Tin Can API, learners will be able to switch between all output formats (Flash, HTML5, and Articulate Mobile Player) without losing their progress or results.
If you published for SCORM or AICC, your LMS won't be able to track or report Articulate Mobile Player content. If you need to track the results of your LMS courses, we recommend that you don't include the Articulate Mobile Player option when publishing. Or, encourage your LMS provider to support Tin Can API. (Our white paper on Tin Can API implementation provides helpful information for your LMS provider.)
If you publish for SCORM or AICC and you don't need to track learners' progress or results, you may still be able to view content in the Articulate Mobile Player. Some learning management systems will allow it, while others won't. You'll need to test your content in your LMS environment to determine if it'll allow viewing SCORM or AICC content in the iPad app.
You can read more about that here.
Hi Leslie and Kevin,
Thank you for welcoming me.
I think your answers are conflicting, or maybe I don't understand. We are developing an LMS to support the TinCan API. During testing we don't see any communication coming from the iPad app. The app does load the content, but there is no progress communication.
Does the Articulate Mobile Player support the TinCan API?
Hi Jordan! Did you publish your content for Tin Can? As for developing your LMS and how that works, I would not be able to help you with, but perhaps someone in the community will.
Hi Leslie,
Yes, the content is published for the TinCan API. We don't need help developing the LMS, but just need to understand if the Articulate Mobile Player app supports tracking with TinCan.
Yes, Jordan. That is what I was sharing with you
Hi Leslie,
I seem to be having the same issue as Jordan. We have extensive experience with Articulate and Storyline. In launching and looking at the story_html5.html and the ioslaunch.html files, they do not have any calls to the Story.js file which contain the means for a statement to be sent to our endpoint.
In monitoring the traffic from the iPad app which was launched with a fully formulated tincan API structure, played on the Articulate iPad app, we saw there was none. No calls what so ever from the app to the endpoint.
Story line Update 4 1311.1422 is the version we are using. Is something getting stopped when the app is opened?
Hi Steve,
I am at least happy that someone else has this problem too. Were you able to solve the issue?
This discussion is closed. You can start a new discussion or contact Articulate Support.