Continue button - move to next lesson?
May 04, 2018
By
Dan Price
Hi,
I'm using Continue dividers/buttons at the end of each lesson to ensure users have viewed all interactions before moving on to the next lesson. However, to actually move to the next lesson users have to click Continue, then click the next lesson footer.
Is there anyway to get the Continue divider to automatically advance to the next lesson, when clicked? This would reduce the clicks required by the end user, and make for a less frustrating experience.
Apologies if I'm missing an obvious setting!
Thanks
Dan
39 Replies
Not currently. You could add a button interaction and use that to branch to the next lesson.
Thanks for the reply Tom. Please can you explain how that would work? Wouldn't the button interaction be there even if the user hasn't completed all content above? We like the Continue divider as it forces the user to complete the above content.
Thanks
You're right, Dan. You would still need the "Continue" block before the "Button" block to ensure that learners completed all blocks above.
It sounds like you'd be interested in seeing another feature added to the "Continue" block, one that automatically advances the learner to the next lesson. I can pass that idea along to our Product team for you--thanks for reaching out!
Hi Alyssa,
That is the functionality I need too. I'm working on a project and the client wants next buttons as they territory that the footer dies not always display on an ipad. The continue button that advances to the next lesson would be ideal. Is it likely to happen?
Hi Ignition,
We added the option recently to remove the next/previous navigation throughout the course, and if you enabled that you could look at using a Button Block to jump to the next lesson. Would that work for your needs?
A new feature needs to be added to the "Continue" block giving the option to "Continue to the next lesson" or simply "Continue within lesson". This is a much needed feature for a better user experience.
Hello Allen and welcome to E-Learning Heroes :)
It can work both ways depending on the placement, so I'm not sure of the behavior that you are requesting here.
I put together a short Peek video to demonstrate the behavior both ways. Just let me know what I'm missing with your request :)
Thanks for that feedback, Allen! Happy to pass that along to our product team for you.
In the meantime, you can use a button block to achieve the same effect. Here's an example of what that could look like:
Thanks for the replies on this one. If you could pass the idea of Continue moving to the next lesson to the product dev team, that'd be great. I appreciate button blocks can be used to move to different lessons, but they can't be restricted (based on content completion) like the Continue blocks can.
Thanks, Dan - I'm happy to share this insight with our team!
Hi everyone! You came up with a great idea, and we put it into action! In Rise, your continue block can now be used to navigate directly to the next lesson when it's the last block in the current lesson.
Check out our latest Rise release notes here to find out what else we've been up to lately. 😊
Thanks Crystal. This is excellent news!
Is there a way to align a button block to the left side instead of the right? We have alot of clients that want buttons instead of the default navigation and a back button on the right side is a little unintuitive to them.
Actually I'm confused. The continue button isn't advancing to the next slide even though its the last block
Make sure you have the navigation turned on in settings. If it's off, then there's no next button.
Just make sure that the "Previous & Next Buttons" option is checked in "navigation" options panel. I must admit, though, that it's not very clear in the Rise documentation that this option must be turned on to make the continue blocks jump to the next lesson.
OH. I thought it could be used without the default navigation.
Is there any plan to offer a classic nav option? Like a player whose next button is active only when you reach the bottom of the block?
I really like the new nav but all my clients hate change/learning new UI. It's pretty much forced me to use SL even if rise is a better fit.
We can update the instructions, but it makes sense because if the navigation is off, there's nothing to expose after the block. Also, once a block is clicked, it is no longer visible when returning to the lesson. Thus, without the default navigation, there's no way to move past the lesson (outside of the sidebar).
I have a storyline embed (on autoplay) as a last item in a lesson and i'm trying to restrict progress to next lesson till timeline completes with a continue button but it doesn't seem to reach 100% when the timeline ends. My idea was to hide it till timeline completes then display but i'm not having much luck. Wondering what i'm doing wrong.
I have 2 other continue buttons set to hide until block above is complete and they seem to work fine except for this last one.
I have navigation set to restricted and next/previous turned on.
Hi there, Maxwell. Your Storyline block should be registering completion once you've gone all the way through your slides. Here's a short example of how it pairs with a Continue block underneath.
Can you tell me a little more about what your Storyline interaction includes? If you can share a link to your Rise content so far, I'm happy to have a look! I can also test out your .story file if you'd like to share it here as an attachment.
Now that we have this "Continue" button - thank you! - I would love to see the ability to control its navigation; to have it go to a screen other than the next one, just like the buttons work in the interactive button/stack block.
Thanks for the idea, Catherine! I'm happy to pass that along to our product team. 🌟
Yeah I totally agree with Catherine. @Rise team, hope you can make this work :)
Yes please do the additional options for the Continue button - it would be great if it could be used to exit the course as well.
Thanks Libby and Nasoula.
I've attached this conversation to our feature request so that we share any updates that we may have on this.
I wanted to share some information about how we manage these feature requests as that may be helpful.