What is the most important mLearning problem solved by Captivate's approach to responsive?

It should be the design that is made easier: you can create different layouts for up to 5 breakpoint views, which are browser resolutions used on different devices. Example: design for small phone resolutions will have a less complicated background, different graphics, less objects, bigger buttons, etc.  In between the breakpoint views devices will always show the layout of the 'higher' breakpoint, but that layout will be rescaled if the parameters in the Position Properties panel are set up correctly. To find the right combination development takes much longer than for a simple rescalable HTML5 project, which would always have the same layout on any device. That approach can be used as well, but will not provide the same UX especially on small browser resolutions like for smartphones.

I agree that this is not solving the 'learning' side of the course. As a former professor I do not believe that the attitude for learning on a desktop/laptop is the same as on a phone. Responsive design will not solve that conflict.

My own guess would be that it produces a single set of output files that are supposed to work across the variety of devices.

But personally, I question how effective that actually is, given all the different reports of this not working or that not working or why does this feature not work in HTML5. So in my own view, it's a bit of a pipe dream.

Cheers... Rick