Do you have recommendations for training I need to build for mobile vs. desktop? People interact differently with training on their phones and I've heard you want to avoid some interaction types.
Here are a few tips. First, think of the size of a phone v.s a desktop monitor. To ensure readability on a phone, be sure you keep the text large enough, and don't put too much on any screen. (Sorry, I don't have specific standards for that.) To ensure usability, make buttons and links far enough apart so users won't accidentally click the wrong one.
As for interactions, the basic click-tell interactions should work. But drag-and-drop may not.
Also, keep in mind that "hover" doesn't mean anything on a phone, i.e., the Hover state is useless. It also means that the user can't determine in advance if something is clickable by hovering over it to see if the cursor changes. So the design needs to be clear about what's clickable.
Finally, if you're using Storyline, I suggest you use the Preview feature to see how the course, as well as the menu and navigation, display on a phone in both landscape and portrait mode. You may want to limit the user to only one mode, e.g, if the course is designed with a landscape aspect ratio, set the course so the user has to hold their phone in landscape mode. (If you aren't familiar with these settings, go to the Articulate tutorials and user guides.)
2 Replies
Here are a few tips. First, think of the size of a phone v.s a desktop monitor. To ensure readability on a phone, be sure you keep the text large enough, and don't put too much on any screen. (Sorry, I don't have specific standards for that.) To ensure usability, make buttons and links far enough apart so users won't accidentally click the wrong one.
As for interactions, the basic click-tell interactions should work. But drag-and-drop may not.
Also, keep in mind that "hover" doesn't mean anything on a phone, i.e., the Hover state is useless. It also means that the user can't determine in advance if something is clickable by hovering over it to see if the cursor changes. So the design needs to be clear about what's clickable.
Finally, if you're using Storyline, I suggest you use the Preview feature to see how the course, as well as the menu and navigation, display on a phone in both landscape and portrait mode. You may want to limit the user to only one mode, e.g, if the course is designed with a landscape aspect ratio, set the course so the user has to hold their phone in landscape mode. (If you aren't familiar with these settings, go to the Articulate tutorials and user guides.)
This is really helpful, Judy, thanks!
This discussion is closed. You can start a new discussion or contact Articulate Support.