Absorb LMS, Storyline HTML5 iPad Player

Hi Keith!

As you may have already found, it's probably the inability of the Mobile App to authenticate a site with login credentials. If your LMS requires a login, learners probably won't be able to use the Articulate Mobile Player, because browsers cannot pass security credentials to iPad apps unless the LMS supports Tin Can API.

Does it load in SCORM Cloud, out of curiosity? 

Hi Peter,

I read that Absorb LMS supports the Tin Can API which is why I thought it would work. I will connect up with Absorb and discuss.

THANKS for your ongoing, intelligent, informed, prompt responses in the forums. Somebody give this guy a raise!

Keith,

You sir, are welcome. I insist you go out and have the best weekend of your life

Thanks for the kind words, and thank YOU for all of your contributions around here!

I'll be curious to hear what Absorb has to say; I'm honestly not familiar with them. 

Take care!

Keith -

We (Omniplex) partner with both Blatant (Absorb LMS) and Articulate products within the Europe. Our initial tests with the IPad has been fruitfull.

It wasn't clear by your comments whether you were trialing Absorb or an existing Absorb LMS client? As utilising Absorb with the iPad, would require an existing client to be migrated to the latest UI (code named Ninja) which would need to be scheduled if it hasn't already done so?

I did a quick test this AM and I was able to publish and launch a course within the Articulate Mobile Player through Absorb, I took a quick quiz and tracked completion - but  please do understand this is still a beta.

We have however discovered that publishing a course as Scorm TinCan using is causing some problems that is being investigated by Articulate.  So until this issue resolved, we would suggest avoiding this feature if you plan on utilising iPad content.

If you have specific issue relating to Absorb you would like us to investigate further I would suggest raising a more direct enquiry direct with either ourselves or  Blatant directly for further analysis:

UK Time:

http://www.omniplex.co.uk/index.php?option=com_content&view=article&id=7&Itemid=

7 for UK Time.

USA Time:
If however you are in the USA, then raising your query direct http://support.absorblms.com/home  maybe more favourable to yourself.

I hope this is helpful.

addendum: "One paragragh had an omission please read this as:

"We have however discovered that publishing a course as Scorm TinCan using "Question Banks" is causing some problems that is being investigated by Articulate.  So until this issue resolved, we would suggest avoiding this feature if you plan on utilising iPad content"

I'm confused by point 3:  It sounds like the Articulate Mobile Player (AMP) is not loaded at all, but that iPad/Safari loads and runs the course as HTML5.  

Is that correct?

Hi Peter,

Thank you for your detailed response!! I just needed to clarify one thing. Is it true that you were able to...

1) Publish a course within Storyline to HTML5 with the Articulate Mobile Player option checked

2) Import that course to Absorb (Ninja)

3) Play that course from within Absorb and have the Articulate Mobile Player show up properly

When we do this, the Articulate Player just doesn't show up at all for some reason.

(Are there certain settings within Absorb involved here? Perhaps it must be set so it doesn't load in the Absorb "Player" or something like that?)

Hi Sam!

Yes, you are correct. The AMP is not loaded at all, but the iPad/Safari loads and runs the course as HTML5.

Peter/Sam!

I am SO sorry! Once I published to "Tin Can" format, it all seems to work. My apologies. I owe you guys for taking time on this! Let me know how I can repay some time.

We accept checks, money orders, PayPal...

Hi Peter,

I realize this is about 3 years old, but I'm curious to find out what the "secret formula is?" So now that our LMS supports the TinCan API, I was wondering in your experience, since all existing courses in our LMS are SCORM compliant, is the best practice to have an instance of the same course in SCORM as well as in TinCan?

• If so, how do you roll-out these two format of courses to your users
• How does this impact the tracking of your courses and reporting (is it too confusing)

I'm looking for answers to see what the best approach is since in our LMS, we cannot overwrite our existing SCORM courses (with each of its own SKU) with a TinCan pub.

Hi Gem!

This thread is a bit dated and Peter does not make it back to the forums very often.

I do think your question would be better answered by members of the community that have gone through a similar transition. Although, I cannot think of a similar conversation off-hand.

Are you having difficulty with the HTML5 content? Is that why you wish to have the Articulate Mobile Player available to your users now?

Our LMS requires a login in order for courses to get tracked, and the post by Peter reads:

"... If your LMS requires a login, learners probably won't be able to use the AMP because browsers cannot pass security credentials to iPad apps."

The issue with our iPad users is SL2 U7 keeps prompting them to download the AMP when published to SCORM on Safari, yet they cannot get past this prompt to even take the course. The only other recourse now is to publish it as a TinCan so it gets tracked.

If we do this, the issue then becomes there will be two instances of the course, one in SCORM and one in TinCan API, since the SKUs on our LMS cannot be overwritten since it will destroy the data integrity of reporting.

I welcome best known practices of TinCan API from our LMS gurus out there please!

And yes, at times the HTML5 content sometimes doesn't synch well with video once published. But that is another issue as well.

Hi Gem!

When you are publishing to SCORM and utilizing on Safari on iPad, you should be de-selecting the publish to Articulate Mobile Player option so that the content will display in Safari as expected. This will prevent the prompt to download happening to your users.

Yes, hopefully some users will be able to chime in with some best practices/advice.

We only select HTML5 when publishing. However, SL2 U7 prompts this whether or not the AMP is or is not already installed. I know for a fact someone from SL told me this is the normal behavior on the iPad and there is no around it. This is the issue: Articulate SL should disable this behavior somehow.

Therefore, this is why the only workaround is publishing in TinCan format. Why isn't TinCan encouraged? That's the future... this the solution I need ONLY please. The settings in the publish to SCORM is irrelevant. Again, we are migrating fully to TinCan API ONLY!

Thanks for clarifying Gem. I thought you were concerned with the current behavior as well. Hopefully someone with similar migration experience will be able to pop in and assist you here.