They just need to play at some size that falls within the borders of the screen resolution and is comfortable for the viewers.ĭesktop users are the easier ones to accommodate for HTML5 conversions because their browsers can easily stretch or shrink to fit the course content. E-learning courses don’t need to fill the user’s entire screen.
If so, that pretty much solves your target audience issue, and will usually mean there is no need to consider reformatting the course dimensions. So part of your job as the ‘e-learning expert’ on the team is to make sure all stakeholders are well educated about these issues before management can make a mistake and blame it on you. By the time they find out it’s not really what they want, it’s usually too late. However, an important issue for Captivate developers is that when managers make the decision to go responsive, most are totally unaware of the fact that their training budget will build far fewer responsive courses than normal ones, or of the fact that changing their mind later to return to non-responsive projects is simply not an option because it means ditching the responsive course/s already built. (This probably explains why previous surveys I’ve conducted from this website show only a minority of participating Captivate developers chose responsive HTML5 as their main project output.) That translates out into a lot more development time and budget. Another issue with responsive projects is that they can take a lot longer to build and place many more limitations on what you can include as far as functionality. The extra time gets eaten up due to the fact that responsive projects need to be designed for anywhere from three to five different screen sizes (if you go break-point responsive). Instead of just arranging objects for a single slide (as in normal projects), responsive projects require the designer to configure the output so that those same objects can look good on devices using vastly different view-port sizes and orientations.
0 kommentar(er)
