Android output - need some human advice

Dec 03, 2014

Michael Burns
By Michael Burns

Ok, I know - Articulate doesn't officially support use on Android. But I have a few questions, and haven't been able to find answers.

Is there a way to force the user to use the Android AMP app? I've seen this on one example (can't find it again unfortunately), but haven't found a way to do this with my own work.

Is there a way to force HTML5 on Androids, like it is on iPhones? My thought here is, if the device supports HTML5, then it will most likely be better. I've tried Chrome vs. the Android default on my Samsung S5, and both are terrible performance (slow, choppy, sometimes objects won't load at all).

Is there anything specific to avoid to optimize Android output in Storyline? For instance, have you found to avoid having too many triggers, or maybe use text boxes instead of text within objects? Any insight would be greatly appreciated.

Thanks! - Michael

1 Reply
Ashley Terwilliger-Pollard
over 9 years ago12/03/14 at 5:58 pm (UTC)

Hi Michael,

You didn't mentioned which version of Storyline you're using, but I did want to point out here that we do support Android in Storyline 2 as detailed here in the system requirements.  As far as forcing a user to view it within a particular environment, Storyline will determine what type to show them based on how they're accessing the course as described here. 

If you're using Storyline 1, we don't support Android, so I'll defer to the community on creative workarounds that they've implemented. 

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