Of course, SWFs have a problem. Learners using a mobile device that does not support Flash such as the iPad, iPod, and iPhone (that's millions upon millions of potential learners), cannot use SWF content. When trying to access SWF content, those learners will be met with a warning that SWFs are not supported. The only way around the warning is to use a supported device (meaning, those learners will have to access the eLearning content via a desktop or laptop computer... which might not be convenient or even possible).
Publish the project (when the Publish process is complete, there's no need to view the Output). Minimize (Hide) Captivate and then open the folder containing the published assets.
The assets folder will contain a combination of the SWF and HTML5 output files. If you've published SWF or HTML5, you're likely familiar with the output files. However, now that you've published both outputs at the same time, there's a new start file in the folder: multiscreen.html.
If you make multiscreen.html the link for learners to click when accessing the lesson, desktop users who have Flash will automatically be served the SWF version of the lesson. Learners who are using devices that do not support Flash will automatically be served the HTML5 version of the lesson. How awesome is that?