STL 360 - serious performance issues on iPhone 6

Feb 24, 2022

Hello,

I'm working for a digital learning agency and we produce lots of modules with Storyline 360, recently we've come accross a very serious issue that almost made us loose a client. The module was systematically crashing at some point for lots of users, after slowing down more and more with each new slide. Turns out those users were using an iPhone 6 or 7.

After a lot of tests we managed to make the module run on those phones, but we had to get rid of a LOT of design attributes (we were not using anything "fancy" such as in-soft shadows or anything, just plain jpeg & transparent PNGs when required), and drastically reduce the number of layers (it's a multi-language module, we were using one text layer per lang, activated according to the current chosen language. Over 3 language layers on one slide (only ONE activated at once, all the time) the module kept crashing at the same approximate point (there was really nothing special about that specific slide, it was just like the others). Even then, after resolving the "crash" issue, we could still see some increasing slow-down when going further into the module. 

We are now seeing this kind of behavior for almost every module we produce : testing them on iPhone 6 rarely passes the test without some severe & increasing lags or crashes.

Tests on Android phones show the same "progressive increasing slowdown a lags" phenomenon, just a bit less visible (and we're probably testing on more recent Android phones, that's why)

Which leads us to think that there might be a memory-cleaning issue from the javascript code handling the animations (and also... the handling of "hidden layers", which shouldn't take so much resources). That's the increasing slowing down that tells us this.

Do you think you could check this with your team and run a few tests, and VERY hopefully we might expect some fixes soon? Because it's really giving us a hard time with our clients...

Thank you very much!

3 Replies
Lauren Connelly

Hello Anissa!

We can definitely look into this with you! I'm sorry for the trouble.

I understand this is specific to viewing the course on an iPhone 6. Which iOS version is being used? Also, does this only happen when viewing the course in a specific browser or all browsers?

It would be helpful if you could share the .story file so we can test it on our end. Can you upload the .story file privately using a support case? We'll take a look and reply with our findings.