I am trying to publish a course for desktop and mobile with IE and Chrome browsers. I think the best solution is to publish for Flash with HTML5 fallback to keep animation functioning correctly in IE. The desktop versions now work well with Flash first, but the course will not play on iPhone or iPad. A window opens on the browsers and then nothing happens. This should fallback to HTML5 on iPads and iPhones and continue to play the HTML5 version, correct?
Thanks for the response. I started with that approach - HTML5 first Flash Fallback, but this client primarily uses Internet Explorer, and I was running into issues with animations not showing properly and slowness. Is there any reason I am not getting the HTML5 version on iPads and iPhones? Is there a setting I am missing?
Flash/HTML5 fallback should be fine, since mobile browsers will bypass Flash and default to HTML5.
Are you viewing the course in a LMS? If so, try testing it in another LMS like SCORM Cloud to compare. SCORM Cloud is industry standard for LMS testing, and it's free!
If you'd like some help with that testing, attach your file here. I'm happy to assist!
I published for the Web rather than LMS since there is no need to track results. Then, I put the files on a local server. My client is working with IE in desktop mode, but iPhones and iPads aren't playing with the Flash first publish. A new tab opens but no content shows up.
I have a new wrinkle, I just tried the flash first version on my Samsung S8 Android phone, and I get the message "This plugin is not supported", yet it plays fine with HTML5 first.
I have attached the published files. Please let me know if you need more information to solve this puzzle.
I think the issue may be with the Flash first HTML back up publish. If you run the story.html file will it play correctly?
I really need both version to work for this client and the Flash version works better for them right now, but they still want the HTML5 version when required.
8 Replies
I'd suggest flipping things so HTML5 is first as described in this thread.
Thanks for the response. I started with that approach - HTML5 first Flash Fallback, but this client primarily uses Internet Explorer, and I was running into issues with animations not showing properly and slowness. Is there any reason I am not getting the HTML5 version on iPads and iPhones? Is there a setting I am missing?
Hi Bonnie,
Flash/HTML5 fallback should be fine, since mobile browsers will bypass Flash and default to HTML5.
Are you viewing the course in a LMS? If so, try testing it in another LMS like SCORM Cloud to compare. SCORM Cloud is industry standard for LMS testing, and it's free!
If you'd like some help with that testing, attach your file here. I'm happy to assist!
Hi Alyssa,
I published for the Web rather than LMS since there is no need to track results. Then, I put the files on a local server. My client is working with IE in desktop mode, but iPhones and iPads aren't playing with the Flash first publish. A new tab opens but no content shows up.
I have a new wrinkle, I just tried the flash first version on my Samsung S8 Android phone, and I get the message "This plugin is not supported", yet it plays fine with HTML5 first.
I have attached the published files. Please let me know if you need more information to solve this puzzle.
Thanks in advance for your help,
Bonnie
Hi Bonnie
I just uploaded your published file to my webserver and ran the html5 link on my iphone - and it plays as expected.
I'm running IOS 10.3.3
I think the issue may be with the Flash first HTML back up publish. If you run the story.html file will it play correctly?
I really need both version to work for this client and the Flash version works better for them right now, but they still want the HTML5 version when required.
Thanks
Hi Bonnie
these are the files in the published output . If I play 1 or 3 on the iphone they both work. so yes the story.html file does work.
Hi Wendy,
I'm going to do more research here. Thanks for the point in the right direction.
This discussion is closed. You can start a new discussion or contact Articulate Support.