I'd appreciate any PM on comments from anyone that has experience deploying Storyline HTML5/SCORM to IOS/iPad students. Success stories, issues, things to look out for or avoid, ...
We attempted to deploy a fairly complex simulation developed in Storyline using HTML5 with SCORM 2004 4th Edition to iPads via the SCORM Cloud.
Performance using Apple's Mobile Safari browser was extremely slow. We experienced better performance using Google's Chrome browser for the iPad. Even so, when the course hit slides with many layers, we experience a crash in the browser. However, if the same course, was running from a web server, but not an LMS, it did not experience the crashes. That appeared to be related to a timing issue between the LMS and the course. We were able to tweak the LMS settings, and modify the course architecture, to get fewer crashes, but not eliminate them.
A very annoying/distracting issue for end users was screen flashing - that is, the browser repaints the screen when layers appear or hide. Given these issues, we went with the Articulate Mobile Player App using Tin Can. That solved the issues identified above.
A very annoying/distracting issue for end users was screen flashing - that is, the browser repaints the screen when layers appear or hide. Given these issues, we went with the Articulate Mobile Player App using Tin Can. That solved the issues identified above.
If it isn't confidential information, would you PM me with the vendor of the LMS you were using for Tin Can support?
I have a client who need a few courses developed for Ipad use. Before I promise him anything can you let me know of a LMS that allows for either Tincan or SCORM reporting when courses are viewed form an Ipad. I know articulate online can but would like to offer them another option.
I have tired several with and all had one issue or another.
I have a course that runs HTML5 output in iPad with SCORM. It works, but it is slow.
I have seen intermittent problems with fill-in-the-blank where sometimes the last character the user types gets deleted from the response when the user presses the "Enter" key on the onscreen keyboard. I can't duplicate the problem reliably.
It runs acceptably, but you just have to understand that basic things like page-to-page navigation runs slower than on a PC. Probably 3 seconds to load a page after clicking Next. Have tested on all iPad versions.
I had a course with a custom menu and resource page ( so three layers per slide) and transition from one slide to another was very slow as well. Around 4 seconds or more. It makes you feel like noting is happening when you press the next button so you press it again and sometimes it take you forward 2 slides.
I had a course with a custom menu and resource page ( so three layers per slide) and transition from one slide to another was very slow as well. Around 4 seconds or more. It makes you feel like noting is happening when you press the next button so you press it again and sometimes it take you forward 2 slides.
I had the same problem of clicking next several times while waiting. A simple fix would be for Storyline to disable the Next button when it is clicked.
13 Replies
We attempted to deploy a fairly complex simulation developed in Storyline using HTML5 with SCORM 2004 4th Edition to iPads via the SCORM Cloud.
Performance using Apple's Mobile Safari browser was extremely slow. We experienced better performance using Google's Chrome browser for the iPad. Even so, when the course hit slides with many layers, we experience a crash in the browser. However, if the same course, was running from a web server, but not an LMS, it did not experience the crashes. That appeared to be related to a timing issue between the LMS and the course. We were able to tweak the LMS settings, and modify the course architecture, to get fewer crashes, but not eliminate them.
A very annoying/distracting issue for end users was screen flashing - that is, the browser repaints the screen when layers appear or hide. Given these issues, we went with the Articulate Mobile Player App using Tin Can. That solved the issues identified above.
If it isn't confidential information, would you PM me with the vendor of the LMS you were using for Tin Can support?
Hi Garry/Sam
I have a client who need a few courses developed for Ipad use. Before I promise him anything can you let me know of a LMS that allows for either Tincan or SCORM reporting when courses are viewed form an Ipad. I know articulate online can but would like to offer them another option.
I have tired several with and all had one issue or another.
thanks
Nigel
Hi Nigel,
I've been using SCORM Cloud with my client to deploy to iPads.
--Garry
But you are having issues. I am hopeful that scorm.cloud will work out those issues in the near future.
Thanks for the quick reply Sam and Garry.
Regards
Nigel
I have a course that runs HTML5 output in iPad with SCORM. It works, but it is slow.
I have seen intermittent problems with fill-in-the-blank where sometimes the last character the user types gets deleted from the response when the user presses the "Enter" key on the onscreen keyboard. I can't duplicate the problem reliably.
Dane,
How many minutes of audio are in your course?
Sam
I have done a little testing with audio, but have not deployed any for use by students yet.
But your course runs slow. Any video / multimedia? Which iPad version are you testing with?
It runs acceptably, but you just have to understand that basic things like page-to-page navigation runs slower than on a PC. Probably 3 seconds to load a page after clicking Next. Have tested on all iPad versions.
I had a course with a custom menu and resource page ( so three layers per slide) and transition from one slide to another was very slow as well. Around 4 seconds or more. It makes you feel like noting is happening when you press the next button so you press it again and sometimes it take you forward 2 slides.
I had the same problem of clicking next several times while waiting. A simple fix would be for Storyline to disable the Next button when it is clicked.
This discussion is closed. You can start a new discussion or contact Articulate Support.