Next Button Alerts and Notifications in E-Learning #293: Challenge | Recap
Generally, when someone asks about the ubiquitous next button, they’re looking for creative ideas to move beyond t...
Published 5 years ago
Version 1.0
Blog Post
I've also continued with the animal theme. This one is repurposed from a challenge I did a long time ago.
I'll be interested in what people have to say about this one because there are multiple ways to move through the slides and I don't make it obvious on slides with static text. I do provide visual ques and a prompt on the animated slide.
https://360.articulate.com/review/content/5579d79f-4de4-47e6-a72d-2750b2821c0f/review
I'll be interested in what people have to say about this one because there are multiple ways to move through the slides and I don't make it obvious on slides with static text. I do provide visual ques and a prompt on the animated slide.
https://360.articulate.com/review/content/5579d79f-4de4-47e6-a72d-2750b2821c0f/review
Yes, that's much smoother on desktop! Very slick. Do you think there's a way to make this work on mobile devices? When I've tucked menu bars off screen like this in past, I've left a small actionable tab visible that can be clicked on, rather than hovered over.
Only 15% of users on my LMS access my courses on a mobile device, but that's up from 9% two years ago, so it's a growing area. What you've done here is absolutely perfect for utilising space on smaller screens.
Only 15% of users on my LMS access my courses on a mobile device, but that's up from 9% two years ago, so it's a growing area. What you've done here is absolutely perfect for utilising space on smaller screens.
- Hi Jonathan, I just tried it on my iPhone and the hover does work so that is good news. The issue with this one is that the bottom of the course is cut off when viewing on the phone so you don't actually see the hover area.
My understanding is that the modern player is supposed to scale to fit whatever browser you are using but it does not seem to work very well on the phone and does not account for the browser bar at the top.
I originally designed this example in Storyline 2 so it was using the traditional player and the story size was something like 1024 by 576. I switched to the modern player for this iteration but did not do anything else.
If you start a project using the modern player and design using a story size that will scale better when viewed on a phone, this solution should work.- Thanks for the update Nancy. Will have to try this out as I always understood the hover state was not supported on mobile devices. The closest I have gotten is pressing and holding the object to activate its hover state (essentially defaulting to a down state).
I'm on Android and have never been able to get hover states/triggers to work in the way you describe on my phone, so that's a little challenge for myself. Thanks for the inspiration.- I tested on apple. I have an android phone as well for testing purposes. I will check it out to see if I get the same results. Designing for multiple device types is still not ideal.