Converting FLASH to HTML5 in Adobe Captivate 9

[berry072]

Hello,

I have some apps in FLASH which I want to convert with all funcionalities to HTML5 (or create from scratch in Captivate 9, if I were sure that the result has the same funcionalities). I wanted to do it with some older versions of Adobe Captivate, but it was not possible then - I had more advanced actions in my FLASH than I could achieve in HTML5. I would like to know if someone of you tried to do this with Adobe Captivate 9 and succeed? Is it possible to achieve my goal with this version, or should I wait for the next one? Or maybe can you recommend me any other solution? I would be grateful for any help.

Alice

[RodWard]

If you're intending to use Captivate, I recommend you look into updating your Flash version to Adobe Animate and then rebuild/republish your apps as OAM files.  These can be inserted into Captivate for HTML5 output.  However, exactly how much about your original app functionality you would need to throw away is impossible to tell at this point.  HTML5 isn't quite as powerful as SWF/AS3.

[teamperform]

Hi Rod - Just saw this post from 2016 on converting from
Flash to Captivate.  Is this still your recommendation for converting courses designed in Flash to Captivate?

[RodWard]

The original poster was asking about how to convert his Flash-based apps to HTML5.  If he had created applications in Flash, he would at least have had some programming experience in ActionScript 3.  I was offering him a solution for HTML5 that involved publishing his apps as OAM files and then pulling them into Captivate slides.  However, how much of his original functionality would be possible in HTML5 was impossible to tell from the scant information provided.  HTML5 still doesn't quite equal the overall performance of SWF.

When it comes to elearning courses that were originally designed in Flash, I would (if at all possible) recommend you try to rebuild entirely in Captivate.  Most Flash-based courses that I have seen were only really using Flash functionality that can now easily be also done in vanilla Captivate files (interactivity, fades, object states, etc).  Building from the ground up in Captivate makes more sense to me because it will then be much easier to maintain going forward.