Clarification on mobile publishing...

May 09, 2013

Hi there,

I need some clarfication on this paragraph below...

"If you choose Web, Articulate Online, or LMS when publishing your Storyline content, you'll see several options on the Publish window. You can choose Include HTML5 output to let learners view content on mobile devices that don't support Flash. You can also choose Use Articulate Mobile Player on iPad to let learners view content on iPad using Articulate Mobile Player, a free app that gives learners the richest viewing experience on an iPad."

If  I publish in HTML5- this will let viewers on mobile devices that don't support flash view content, except for an iPad. 

The only way to view on an iPad is with the Mobile Player App. 

Am I understanding this correctly?

The other question I have is that some end users are expereincing slides that do not load correctly.  PC computer with a typical web broswer (not mobile technology).  Why might this be? It is just a slide here and there.  The inconsistency is what I am trying to figure out. 

Thank you much- kara

5 Replies
Peter Anderson

Hey Kara!

Whether you choose HTML5, the Mobile Player, or both, your users will be able to view their content on iPad. Here’s how Storyline determines which version of your content to display when users view it. 

As for the slide content that's missing randomly, can you provide any more detail about the specific kind of content that goes missing? Are you hosting the course on an LMS or website?


Peter Anderson

We'll look forward to reviewing your file then, Kara

Just a note, that in general, HTML5's performance will not be as smooth as Flash or Mobile Player output. It's still relatively new, though, so that will improve with time. 

Please feel free to share your case number here when you receive one. 

You'll also want to be sure you're following some basic rules to prevent strange behavior:


  • Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior. 
  • You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
  • Avoid using special characters, accents or symbols in your file names.

Finally, if your Storyline software is not working properly, a simple repair may fix the problem.


Thanks, Kara!

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