Storyline HTML5 Output Crashes Mobile Safari on iPad Frequently
I'm working on a Storyline course that works flawlessly on a computer, but crashes frequently when published to html5 and viewed on an iPad. Most of the world is not using TinCan or xApi, so publishing to the Articulate Mobile Player for LMS tracking of content for much of the professional eLearning world, isn't possible yet.
I've spent countless hours manually tweaking the programming of interactions, animations (even removing them) and while I may get slightly smoother playback on the iPad (iPad 2 in this instance) it still crashes at random points, not one or a couple of repeat crash points that could be tested and ironed out. I will say, I got the course to play through on an iPad Air (with a few glitchy behaviors), but it's not realistic to expect clients to have the latest and greatest hardware.
What's worse, Storyline is marketed so well, and has such a great community, that thought leaders in educational institutions are asking for Storyline for HTML5/iPad delivery to their LMS, not knowing how badly and frequently HTML5 output crashes the iPad. Yes, all iPads are not created equally, but currently, the iPad 2 is the most widely used version (still although it is old) and it's just not powerful enough to handle anything aside from very simple Storyline courses with very simple animations and not too many slides. It's scary.
I've tried the most recent update (update 6) and the crashes still happen, although performance did seem better, but then I found new bugs (video controls always show on iPad in html5, even if you mark "no controls" in Storyline) that meant I couldn't deliver my course using that update. I will say Articulate was great in helping me roll back to Update 5, but, alas, it seems this product is not capable of outputting HTML5 courses that won't crash mobile Safari on the iPad, courses of much depth at least, and it's hard to see how deep this problem runs until you're course is almost fully programmed. We're several years into the update cycle, and it's starting to feel like this problem is out of reach?
We NEED a list of best practices from Storyline for nearly EVERY feature what works well and what doesn't on HTML5 and in iPad, and this NEEDS to update with each Storyline "Update" (Update 6 for example). I'm coming to a position where I can almost no longer recommend Storyline for courses clients want on the iPad, because of all of the crashing that happens, and that's sad, because Storyline is really a great tool.
We need a better way to manually trigger garbage collection, because I'm assuming this is the problem in the HTML5 version on the iPad, and that eventually overwhelms the browser and crashes it.
Like I said, we need a list of best practices for course layout, tool use, etc. for publishing to HTML5...
- How many slides are too many?
- How many layers are too many?
- Are layer dense slides better than more slides with less layers?
- What can and can't you animate effectively in HTML5 on limited capability devices?
- What styles (shadows, strokes, highlights, reflections, etc.) affect both playback and rendering performance in HTML5?
- What specific things should people AVOID AT ALL COSTS when producing iPad content for mobile safari?
- What are limitations of each tool for HTML5 publish?
Sorry for the long winded post, I honestly really love Storyline and think it's probably the best tool on the market, and if though discussion we could help improve this issue, it could help a lot of others I'm guessing have had similar issue.