Forum Discussion
Storyline 3 Crashes on iPad Safari and Chrome
Hello,
I'm researching an iPhone crash issue and... I just found this one, which was reported 8 years ago, and I'm sad to declare that... it's still happening, and it makes developing learning modules on iPhone a literal HELL.
Has anything been made about this issue? it's only happening on Safari / iPhone (on iPad it works ok), and we notice that the memory is just getting filled more and more with each slide, and never getting emptied.
Our clients ask us to develop a LOT of "mobile-first" courses, and we are losing a lot of time and money trying to overoptimize every single pixel or animation, while they work smoothly on ALL other devices. iPhone are running super-heavy 3D games filled with FX & sounds & animations, how can we explain to our clients that their 80Mo html5 module cannot be watched on a modern iPhone?
- PhilippeDelv3992 days agoCommunity Member
I have to add that the modules I'm talking about right now are modules that were produced a few years ago (3-ish) and that we updated recently (using the last storyline update).
the previous modules, released 3 years ago, were NOT crashing on iPhone, but once they've been updated (few changes, not that much content added) they started crashing quite early in the module. optimizing carefully every little thing (images / sounds / flatting-out a maximum of layers into the base layer...) made it crash further but no way has been found so far to make the module playable in its whole length.