Publishing for mobile devices

Dec 13, 2012


Does publshing for mobile devices in Storyline mean only for iPads?  I have tried viewing content in on other mobile devices but it does not work.  Is there anything that i need to take into concideration when publishing for mobile devices besides iPads?




8 Replies
cynthia Kuni

HI Ian, thanks for your response, i was testing on different devices and all of them had an issue of some sort. for expample on a samsung touch screen, since my tutorial had the data entry option, the user once clicking on the data entry field could not type as the phone keypad did not appear as it does in touch screen phones.  player template nevigation just didnt function.

when viewing on a nokia in its standard browser, the tutorail just fails to load. Am not sure if i was missing anything.

I need to know if there are things to consider when developing or publishing for different mobile devices.

this tutorial worked perfectly on an ipad by the way.




Christine Hendrickson

Hi Cynthia,

You might want to take a look at the comparison chart for Comparing Storyline's Flash, HTML5 and Articulate Mobile player output. You'll be able to take a look and see what features are supported by the different output types. This chart may help you figure out what you need to consider when publishing for these devices. 

Click here to review the system requirements for authoring and viewing Storyline content:

I hope this information helps
Ian Monk


Just to echo what Christine has posted...

You will find that you need to be very careful when you are developing across mobile platforms. Obviously, you want to be consistent in the way you display information across platforms, but that's easier said than done. What works for a PC will not work the same for iPads and other tablets due to the different delivery capabilities (flash, html5, iPad mobile app). It's unfortunate, but that the reality of the industry right now. 

I would agree that this is a massive challenge and can often seem limiting. I am hopeful that Articulate is working on streamlining our capabilities as mobile development was the main reason for our team to switch authoring tools. 

On a side note, LMS: Tracking & Reporting for the mobile app is only available for Tin Can API. From my experiences, many LMS are not quite there yet. That said, if your main goal is to track user progress than you'll need to ensure that your LMS can support Tin Can API, otherwise this may not be the best option for you.

Celito Macachor

Hi Christine and Ian,

That comparison chart seems very extensive. If development is confined only to those features that will work in all three outputs, will it mean that the file will have better chances of working on all devices with lesser problems? Would that be careful enough?

Thank guys for your learned inputs. Makes life easier for us who are still groping with mobile development, and also find this as the main reason for switching authoring tools.

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