Preloading / prerendering content in Captivate, HTML5

Report · Jan 15, 2017

Hi,

I`m using Captivate 9 and publish in HTML5.

I wonder whether it`s possible to preload or prerender content in a Captivate course.

Let me be more specific:

Let`s assume we have a course (built with Captive, published in HTML5) with a couple of slides. Some of the slides involve large external files (e.g. graphics, audio or whatever). Entering a new slide it always takes a while until all content is ready - which can really affect usability and user experience.

There is a kind of solution as follows: If there is big image on say Slide 5, I can put this image on Slide 4 "For Rest of Project" and hide the image. On Slide 5 I show the image - it will appear instantly. However this solution is a bit unhandy, especially also because of the restricted z-order of objects that are timed "For Rest of Project".

On the other side there exist very powerful options of preloading, prefetching and prerendering content in HTML5. The different options can be seen on the following page: https://css-tricks.com/prefetching-preloading-prebrowsing/

However I wasn`t able to get them to work in a Captivate course. So my question is: How can I use the preceding methods in a Captivate course? Has anybody succeeded in preloading, prerendering or prefetching content in a Captivate course (for a specific slide or the whole course, with HTML or any other method)? How did you do this in detail?

I`m very sure this is possible - it would be a great improvement of UX!

Thank you very much in advance for any advice!

Report · Jun 11, 2017

Hi there,

We are having similar frustrations due to load times between slides undermining UX (Captivate preloader is set to 100%, however our largest files are audio which Captivate preloader does not load).

I am curious if you had any success / insights regarding your above question?

Thanks

Report · Jun 11, 2017

Captivate has the ability to "embed" general web content as an iframe in a slide, which is a strategy to completely remove the media from captivate rendering. However, I believe that this always gets loaded "on top" of other captivate resources on the slide. If this is ok, then you may have a path.