Ok, so I know that I am behind the ball and many of you have been doing this for years. But we’ve only had access to trainings onsite and computers. There has been discussion about adding iPads for access. I’m wondering about the time to expect in building responsive eLearnings. 1) updating the 200+ courses to bring them to responsive. 2) additional time to build as opposed to traditional. Thoughts? Thanks
Thank you for these thoughtful responses!
Thank you MIchael.
If you’re intended output is for IPad and your content was already built as HTML5 then using the scaleable HTML feature is a fast and effective way to get you going. Especially if you have over 200 files. If you’re going from SWF you’re going to have to check each file using the HTML5 tracker to make sure that the objects used in the files are HTML5 compatible. Sadly, many components of older versions of Captivate were not. Hope my two-cents helps.
Scaleable HTML5 projects will work great on an iPad, but on a cell phone, the interactive elements might be too small to interact with. Give it a shot and let us know if that worked.
This video by Paul Wilson is a great resource to review when adjusting old captivate projects to HTML 5. https://www.youtube.com/watch?v=CsVpK-tMEJw
There is a lot of lacking information in your question. Which version was used to develop those older courses? Were they published to SWF or were they ready for HTML5 publishing?
The work to convert may take a lot more time than you expect. If those courses are older, you first have to take out all items incompatible with HTML5 publishing (see HTML Tracker). That may involve replacing by other items. Typical are all rollover items, since mobile devices do not have rollover events at all.
Next question: is it really necessary to create responsive projects? There is no easy way to convert an existing non-responsive project to a responsive project. Except for some very simple projects the proposed workflow for such a conversion may prove totally useless. That means you have to recreate each project, using the assets found in the Library.
Be realistic: you can display a non-responsive project on a tablet (like iPad) if you choose the Scalable HTML feature. That would reduce your work hours to make everything compatible with HTML5 publishing. Even if you are already familiar with using Fluid Boxes or Breakpoint views (as alternative) know that the developing time for a non-responsive project may be doubling (or more) compared with a non-responsive project.
Maybe have a look at this older post:
Tough Choice: Breakpoints or Fluid Boxes? – eLearning (adobe.com)
You must be logged in to post a comment.
