Storyline 2 Player Now Pubs Only in TinCan API

May 04, 2015

The new Storyline 2 feature of the iOS player for mobile devices utilizes the TinCan API for tracking – no longer tracks SCORM pubbed content as it did in the Storyline 1 player. Realizing the only other format is HTML5, of course, it is not efficient enough since it is not compatible with all browsers.

I was wondering if anyone has a workable solution or best practice to this if their LMS is not configured to track the TinCan API yet.


24 Replies
Gem Austria

Thanks for the info, Phil. Please clarify though since in SL1, it always tracked on iOS devices (iPad) yet it doesn't in SL2 despite the Articulate Mobile Player feature selected.

Could it be another issue by chance if it's not tracking. It used to track when that same feature was selected in SL1 in our same LMS??

Gem Austria

Thanks Phil!

I'm deducing it tracked on the iPads in the past since we had always checked HTML5 (therefore AMP is irrelevant) and Safari was utilized. IE utilized Flash which is the default.

Seems (according to Leslie's helpful documentation) Google Chrome is the only one that is best compatible with HTML5 on PC, and IE tracks via Flash in the browser. Let me know if this sound about right to you.

Andrew Downes

If you do want to use the mobile app and Tin Can and your LMS can't launch Tin Can content, you can also use SCORM Cloud dispatch. You add your content to SCORM Cloud and then use a simple SCO package in your LMS to launch the content. You then get basic SCORM data tracked to your LMS and all your Tin Can data in SCORM Cloud. 

Alternatively, ask your LMS vendor to add Tin Can support. The number of adopters is growing each week. Which LMS are you using? 

Andrew Downes

I'm not sure I completely understand the question, but will try to reply anyway!

It really depends on what Tin Can functionality your LMS vendor is adding. Let's assume they are doing the equivalent of installing SCORM Engine which is a content player and LRS. In that case, you could just re-publish your Storyline content with the Tin Can setting chosen and the tracking would work in the same way it does for SCORM. 

Gem Austria

As far as re-publishing Storyline content... your input led me to publishing a test course which generated a "tincan.xml" file like a SCORM pub would generate an "imanifest.xml" for tracking. I attached a screenshot of the SL2 pub panel. Since the Tin Can is a separate publishing feature, does this mean that it would necessitate 2 publishes of that one course (one is SCORM and one in TinCan) to make sure the course gets properly tracked on all platforms - which means there would be actually 2 instances of the same course in our LMS.

Andrew Downes

Absolutely. Tin Can has the capability to be anywhere from a lot more secure to a little bit less secure than SCORM depending on how its implemented by your vendor.

Even if Tin Can is implemented in an insecure way though, I'm not sure that having the desktop version use SCORM would be any more secure; presumably an attacker would always choose the least secure option. 

See this stack overflow question for more on Tin Can and security:

Ashley Terwilliger-Pollard

Hi Gem, 

Apple made some changes to the way apps launch in iOS 9. As a result, your Articulate Storyline 2 content may not launch in the Articulate Mobile Player (AMP) as you'd expect.

The launch page for your course will open in Safari, but then you'll be prompted to install AMP as shown below—even if it's already installed.

To support the changes in iOS 9, we released Update 7 for Storyline 2. See the following sections for details:

This discussion is closed. You can start a new discussion or contact Articulate Support.