Best Practices Question: Interactions per page

It really depends on the content you're providing training on.

If this page in which a user clicks a check box, enters some text, and clicks a button relates to, say, some software in which they do these three things on the same form or "screen" of the program... you should probably keep those interactions together in your training. Chances are, your users who perform this action outside of training aren't going to be clicking on a check box, then clicking "next", then typing some text, then clicking "next" again, then clicking submit. So I would recommend avoiding this with your training.

While I understand the concern of load times in relation to number of objects on a page, I'd say that having a user wait an extra 2-3 seconds so you can provide more effective training would be worth it. If having those three interactions on one page is dramatically increasing load time (I'd say 10 seconds or longer to load depending on file size and your connection speed) then you should probably be looking at solutions outside of limiting interactions in Lectora.

At my work we have pretty average upstream/downstream speeds and I've never run into issues with Lectora courses running slow once published to my LMS (outside of the LMS itself having delivery issues which have had nothing to do with my courses). Even some courses with 20+ buttons on a single page and multiple actions for each button.

Hope this helps and didn't ramble too much. Let me know if I'm not making sense! :)

@bgruebmeyer 50333 wrote:

- Multiple interactions on a page using the same graphic images reduce load times for users

- Breaking the interactions up on separate pages make it easier for developers to maintain

I think you pretty much just answered your question.

What is the page flicker amount that is comfortable for your users?

What is the maximum slide complexity that is still comfortable for your developers?

E.g. my developers can handle anything, so we'd stick with maximizing user comfort and combining several interactions on a page, but when we produce titles that will be edited by the client later, we have to keep things reasonably simple.

If loading a screenshot really takes noticeable time and ruins the experience for your users, you may think about pre-loading these images. The simplest way is to put them all on the first page and cover them with a white rectangle (hiding them may prevent them from pre-loading in some browsers) so that the browser would request all those images at this page and serve them from cache when you need them. Add a 10-sec delay before 'Next' button is shown and put a nice animation (like this one) on top.