I've found the HTML5 running in Mobile Safari to be extremely slow. Also, it's not very stable. Mobile Safari doesn't fully support HTML5. I have better performance using Google's Chrome browser on the iPad.
The Articulate Mobile Player runs circles around the HTML5 output.
The player is an Air app and it plays SWFs that are created through the publish process. These SWFs are different than the SWF created for the Flash output. It is definitely not HTML5.
Have you looked into using the Tin Can API and the SCORM cloud to dispatch the courses from behind the firewall? We are doing something along those lines for a client. Shoot me an email if you want to talk through some options.
3 Replies
Hi Eric,
I've found the HTML5 running in Mobile Safari to be extremely slow. Also, it's not very stable. Mobile Safari doesn't fully support HTML5. I have better performance using Google's Chrome browser on the iPad.
The Articulate Mobile Player runs circles around the HTML5 output.
--Garry
Hi Garry!
Thanks, for this project, the story files will be stored behind the corporate firewall. The Articulate player won't/can't access it.
Do you surmise that the Articulate player is basically acting like an HTML5-ready and optimized browser?
The player is an Air app and it plays SWFs that are created through the publish process. These SWFs are different than the SWF created for the Flash output. It is definitely not HTML5.
Have you looked into using the Tin Can API and the SCORM cloud to dispatch the courses from behind the firewall? We are doing something along those lines for a client. Shoot me an email if you want to talk through some options.
This discussion is closed. You can start a new discussion or contact Articulate Support.