Our QA team is aware of this and is working hard to get it improved for a future version. While it seems to work fine in Chrome, Mobile Safari does exhibit excessive delays. Thanks for bringing it to our attention.
Any rough idea on timeline for this? Our teams will need to make decisions on whether to continue using Storyline or seek out another tool or approach. Thanks, Scott.
I won't speak for Aticulate directly, but my experience with them is that they address issues fairly quickly when they're aware of them. Unlike other companies (*cough* *cough* Adobe), they don't usually provide lip service without following through.
Mobile courses were a big deal to our company and we've had no issues using the Mobile Player. Obviously if you're wanting to track courses within an LMS, that puts a wrench into the Mobile Player unless your LMS supports Tin Can.
From my research, there aren't many options out there that has figured out HTML5 output flawlessly and if they have, they likely don't have the robust options of Storyline or the 1 file to launch all 3 publish types.
Our QA team is aware of this and is working hard to get it improved for a future version. While it seems to work fine in Chrome, Mobile Safari does exhibit excessive delays. Thanks for bringing it to our attention.
Has this issue been addressed yet? or any ETA? We've purchased a number of Articulate licenses and have now come across this. We might have to look for an alternative if this is not resolved quickly as we were planning on to start producing lots of content fairly soon. We're experiencing the same issues on the iPad 1, 2, and 3 (with iPad 1 experiencing the greatest lag time ~6 seconds between page transitions on assessment questions).
The issues with slow response time are more a symptom of an immature HTML5 and Mobile Safari than a Storyline limitation. The iPad's mobile Safari browser currently has inherent limitations that impact how multimedia operates, as well as the overall performance of HTML5 content.
Please review the following article to learn more about mobile Safari's limitations and recommendations for improving performance of your content:
My company is having these same problems. We were in the process of changing from Flash based courses to using Storyline to create our e-learning. Currently though this issue is proventing us from doing so, has there been any developmets with this issue? We need our LMS based e-learning courses to run smoothly on an ipad.
Storyline's performance in HTML5 on an iPad will continue to evolve as HTML5 itself does. And as it does, we'll continue to update the chart here. As always, we recommend testing your content in its intended environment before deploying to users.
Hey Christie, I have, and the info that I supplied came from (my own) iPhone 6s and iPad mini 2, both running on Chrome. I can't say the performance on the Articulate Mobile Player is good, but compared to html5 it's great.
Hi, Erez -- Thanks for your response! We're always working on improving HTML5 from our end, but in the meantime, AMP is recommended. If you would like to share your thoughts or ideas with our Product Development team, you are welcome to do so using this form. :)
11 Replies
Hi Josh,
Our QA team is aware of this and is working hard to get it improved for a future version. While it seems to work fine in Chrome, Mobile Safari does exhibit excessive delays. Thanks for bringing it to our attention.
Any rough idea on timeline for this? Our teams will need to make decisions on whether to continue using Storyline or seek out another tool or approach. Thanks, Scott.
Hi Scott,
I won't speak for Aticulate directly, but my experience with them is that they address issues fairly quickly when they're aware of them. Unlike other companies (*cough* *cough* Adobe), they don't usually provide lip service without following through.
Mobile courses were a big deal to our company and we've had no issues using the Mobile Player. Obviously if you're wanting to track courses within an LMS, that puts a wrench into the Mobile Player unless your LMS supports Tin Can.
From my research, there aren't many options out there that has figured out HTML5 output flawlessly and if they have, they likely don't have the robust options of Storyline or the 1 file to launch all 3 publish types.
Just my 2 cents.
Has this issue been addressed yet? or any ETA? We've purchased a number of Articulate licenses and have now come across this. We might have to look for an alternative if this is not resolved quickly as we were planning on to start producing lots of content fairly soon. We're experiencing the same issues on the iPad 1, 2, and 3 (with iPad 1 experiencing the greatest lag time ~6 seconds between page transitions on assessment questions).
Hi Aditya, welcome
The issues with slow response time are more a symptom of an immature HTML5 and Mobile Safari than a Storyline limitation. The iPad's mobile Safari browser currently has inherent limitations that impact how multimedia operates, as well as the overall performance of HTML5 content.
Hello,
My company is having these same problems. We were in the process of changing from Flash based courses to using Storyline to create our e-learning. Currently though this issue is proventing us from doing so, has there been any developmets with this issue? We need our LMS based e-learning courses to run smoothly on an ipad.
Thanks,
Rob,
Hey Rob, welcome to Heroes!
Storyline's performance in HTML5 on an iPad will continue to evolve as HTML5 itself does. And as it does, we'll continue to update the chart here. As always, we recommend testing your content in its intended environment before deploying to users.
Welcome again!
Hello,
I see that this is a 3+ year old thread, but the issue is still alive and well. Can anyone confirm an improvement, or possible solutions?
Hi, Erez -- Thanks for reaching out, and have you had an opportunity to review this information, HTML5 Content Is Slow or Doesn't Work in Mobile Safari?
This post was removed by the author
Hey Christie, I have, and the info that I supplied came from (my own) iPhone 6s and iPad mini 2, both running on Chrome. I can't say the performance on the Articulate Mobile Player is good, but compared to html5 it's great.
Hi, Erez -- Thanks for your response! We're always working on improving HTML5 from our end, but in the meantime, AMP is recommended. If you would like to share your thoughts or ideas with our Product Development team, you are welcome to do so using this form. :)
This discussion is closed. You can start a new discussion or contact Articulate Support.