Articulate Storyline Resilience
I am in the process of updating a large number of older Articulate Storyline objects (Created in SL1 and SL2) that have suddenly stopped working. After some research, I found out that they had stopped working because of recent browser updates causing the published files to no longer execute in many browsers. I have also found the 'Articulate Updater' tool that was released some time ago to fix these issues (https://articulate.com/support/article/articulate-updater-release-notes-and-instructions).
Is this what it is going to be like moving forward? While this tool makes it easier to update the files, it is nonetheless more work to be done (Finding the courses, which files are broken, finding and re-uploading individual files, possibly running into issues when the course goes live...). I understand that Articulate Storyline 360 has obviously had several updates since SL1 and SL2, but does that mean that this trend will repeat itself later on down the road? I need to know that I won't end up having to do this again in the future for every other Articulate Storyline project I create using 360.
If Articulate publishes to HTML5 (even SL1 does that) then why are we all running into issues with browser updates and incompatibilities? I know that the the security settings on browsers sometimes get changed, and Flash might not work all the time, but should that really cause the whole object to break? HTML5 is resilient in web design, but somehow even though Articulate Storyline exports to HTML5, it doesn’t seem to be nearly as resilient judging from it’s older products.
Please let me know if there is a way to confirm that this will not be an issue going forward.