Slide layers not working on iPad

Nov 27, 2013

Hi,

Some odd behaviour here testing the LMS course on iPad.

When an automatically triggered layer occurs (that is the learner has not clicked or otherwise done anything to trigger the layer) it lags - the voice starts and finishes, any base objects appear, and any timed content along with the progress bar only start when the voice has finished.

On slides where the leaner directly triggers the layer, there is a definite pause maybe a screen flicker and the layer then behaves normally.

I am thinking perhaps the small memory of the iPad is happy when it is given time to show a layer, but when one occurs automatically it isn't able to cope with the sudden demand for memory?

I am using an iPad 3 with iOS 7.0.4

Has anyone else come up with this problem and found a solution?

Many thanks in advance

(I tried to attach the whole published story - in a zipped format but it timed out on me - if anyone wants a copy to look at please tell me the best way to get it to you! :o) )

6 Replies
Tim Naylor

Thanks Russ, but this is something that has flagged up from testing on various iPads in several settings. It wasn't until it was passed back to me as the creator (I don't do the LMS side of things) that I realised that lag was happening on specific occasions - well in all fairness they wouldn't know because they don't know how the course is put together.

Ashley Terwilliger-Pollard

Hi Tim,

The flickering of slide layers within the HTML5 output is something we're aware of, and our team is working on updates to improve performance in future Storyline updates. In regards to the first issue you've described with the remainder of the content not displaying until the audio is over, that is something we'd be happy to test. Please share your .story file with us here or privately with our team here. 

Ashley Terwilliger-Pollard

Hi Tim,

I just checked in on your case and see that you were able to successfully run it on the PC, but that John shared:

The iPad's mobile Safari browser currently has inherent limitations that impact how multimedia operates and the overall performance of HTML5 content. See this article to learn more about mobile Safari's limitations and recommendations for improving content performance:
http://www.articulate.com/support/kb_article.php?product=st1&id=4z71jip9kvp8

Since the file works fine on a PC, the issue can be attributed to the iPad's limited hardware specifications.

Since using the Articulate Mobile player is not an option, then I would then recommend that you try to simplify your file's design. Try to make a test file that uses only one slide layer and then see if it will work on an iPad. From experience, the more content put into a single slide, the more it would lag when run on an iPad.

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