Best practices to convert/publish existing Flash-based projects to HTML5
In the last couple of years, many organizations have shifted to moving eLearning solutions to mobile devices, which meant rebuilding the complete solution so that it would work seamlessly on HTML5. As mobile learning solutions are based on HTML5, therefore it is even more essential to convert from legacy Flash-based solution to a more, modern HTML5-based solution. Adobe has already deprecated Flash from its suite of products. For more information, see this blog.
The removal of Flash has in turn affected projects in Captivate that were produced as Flash output. We’ve listed a few best practices that you may refer to, while you contemplate transitioning from Flash to HTML5.
- Identify the courses that must be migrated to HTML5. You may not move all courses to HTML5. Shortlist the pilot courses that you want to move. In addition, ensure that you have all the assets and resources in place so that there are no unpleasant surprises during the migration.
- Assess the scope of migration. While some projects may only require minimal changes, for example, changes in visual design, other projects may require extensive changes, for example, redesigning of animations.
- Move bulky, legacy courses to shorter, easily consumable mobile learning solutions, so that your courses cater to a range of mobile devices. You must evaluate a different learning design approach that can cater to multi-device support.
- After a trial conversion, send your project to a peer group or a focus group for comprehensive feedback, so that you can incorporate the feedback into your future conversions.
For more information, see the following resources:
- Paul Wilson’s blog on converting Flash to HTML5 without source files
- Allen Partridge's blog - Learn how to convert Flash into HTML5 content
- Allen Partridge's blog- Migrating Legacy Flash eLearning Content to HTML5