Any best practices for 'Try It' simulations in HTML5?

Hi Community,

I have just completed a Try-It piece for systems training using SL2. I had to deploy in HTML5, as this is now the required format in our development workflow. The final product is working--all hotspots, text-entry fields, buttons, etc. work as designed--but it feels clunky and the loading animation appears every slide transition. I never had this issue when we still deployed in Flash. 

I understand that the View/Try/Test paradigm for systems training came out when Flash was the de facto format of software simulation courses. But now that everyone's moving to HTML5, are there any best practices out there that can improve the feel of highly interactive courses and minimize the impact on learner experience?



2 Replies
Daniel Brigham

Hi, Tin: I don't quite understand what you are asking. 1. You seem to be concerned about the size of the file, which you might not be able to do much about. 2. You seem to think the flow View/Try/Test when done in Storyline is clunky. Is that right? Just want to make sure I understand before I take a stab.

Tin Telesforo

Thanks for replying, Daniel. Apologies if my initial post wasn't very clear.

1) The file sizes--averaging 50MB--are not the issue; it's the HTML output of the 'Try It' pieces that feels clunky.

2) The View/Try/Test model has been working for the systems training industry for a long time, but now the limitations of HTML5 makes the 'Try' and 'Test' aspects challenging to pull of. The feel is not as smooth as in Flash. I'm assuming this is regardless of tool used, though I've only been using SL2 so far.

I'm hoping the community could share best practices in developing highly interactive 'Try' pieces that will not negatively impact learner experience.