Forum Discussion
Remove play button on html5 opening screen in Storyline 360
And I'm just going to keep saying this until someone at Articulate listens/understands:
A "play" button at the beginning of Storyline content is only necessary when there is content that might autoplay (e.g., audio or video) at the beginning. If Articulate can't figure out how to intelligently detect that, the author should be allowed to set whether or not a play button appears.
For example, if I have a drag-and-drop exercise that I create in Storyline, there is no reason at all for mobile users to first click a confusing "Play" button to begin dragging the objects. The dragging itself (or the selection of a multiple choice option or the clicking on a hotspot or...) IS the user interaction. You do not need to create a perfunctory or substitute user interaction (the play button) to indicate the user's willingness to begin the real user interaction.
H5P content is a great example of this. Most H5P content types work brilliantly across mobile devices and browsers without the need for a play button to launch or activate them.
And it's not just about styling that play button -- it's about displaying it only when it is absolutely necessary. For a great deal of content, it is not necessary (and is, in fact, confusing and cumbersome for the end user).
Well said Eric. On Desktop computers a module that doesn't have audio or video on the first slide doesn't display the awful screen with the play button. On mobile devices it appears regardless. I think we need Articulate to first address the inconsistency and then provide us with a way to customize this screen.
Oscar