Forum Discussion
Good Afternoon, all. A quick update:
- In Storyline 360 Updates 10, 11, 12, and 13, we incrementally introduced pieces of the solution we outlined last September. The following improvements are now complete:
- Based on the age of the iOS device and the weight of the slide, Storyline preloads some content if the browser can handle it and keeps some content in memory.
- If the slide is too heavy or the device is too limited, Storyline preloads nothing and keeps nothing in memory after exiting the slide. Slides will load more slowly for learners in this scenario, but it should reduce the frequency of crashing.
- The same solution was added to the release of Storyline 3 Update 3 earlier this week.
We've tested many media-rich courses, and although it is still possible to build a slide that will crash Mobile Safari (think many layers of large, lengthy videos, or high-resolution images with zoom regions) we believe our solution solves the problem for all but the toughest courses.
We have an inkling that there is still more work that can be done on this, which is why you haven't seen FIXED ALL MOBILE SAFARI CRASHING in neon lights within our release notes, but we've made significant progress. If you have a .story project file that is still capable of crashing Mobile Safari, we'd love to have a copy of it so that we can continue to optimize our published output for iOS.
Hi Justin,
Thank you for the update. In order to see the changes, do we need to create a new story file in the updated version, or can we just publish our existing course in the update to produce the desired results.
Thank you!
- Justin7 years agoStaff
Jamie, you should see those improvements simply by republishing your existing projects.