I would like to find out what I'm losing in Storyline should I start developing using Rise instead? (ie any differences in features, capabilities I'm losing?)
I would greatly appreciate if someone could help me figure this out. I have a had a quick look at Rise and it looks like it is pretty much something that accurately depicts responsive authoring. However, I have been using Storyline ever since and I want to know what I'm losing if I go with Rise instead.
Starting from a storyboarding perspective if possible I'd like to know the specific boundaries about what I can create, do in terms of customising the theme, branding, and creation of complex interactive elements with Rise. How about animations? button states, layers, pop up captions etc? Hope it makes sense :)
I would expect you would continue creating courses as well as creating courses using Rise as well.
They are really to different authoring environments for different use cases. Storyline has a blank canvas approach that will allow you to create what you want within the slide, but it produces non responsive slide based learning, which on mobile devices may restrict the usability (may!).
However Rise is a template responsive course that will give a great experience on Mobile devices as a well as desktop, but to deliver this you are restricted in how the interactions work and the customisation of the theme. At the moment the theme can have a single colour change and a font change. This doesn't mean you cannot build great learning because you can, I would see Rise as another tool in your armoury rather than as a replacement for Storyline.
I had been wrapping up the finishing touches on a course I built in Captivate (please, no throwing eggs at me folks) earlier this week and decided to try Rise out by converting this course to a Rise project.
The usability, from an authoring standpoint, of Rise is phenomenal. Super fast and slick. I didn't encounter any bugs with the authoring. Export doesn't work as of now, so it's not usable for me, so I abandoned the project.
To answer your question - I think the biggest thing to consider is the paradigm shift required of your design for Rise. The vast majority of elearning courses use a voice narration to "drive" the content. In other words, voice narration plays while visual elements are timed to animate/appear on the page to the user.
While you could accomplish this through video, and while there is an audio component in Rise, it's not really designed for that type of approach, nor should it be IMO.
It really should only take an hour or less to build a quick sample course and, through that, get to know how it works, what the available blocks/lessons are and how they work in a course, so I recommend you just jump in and build a project.
Hey Mark - thanks so much for your warm words about Rise!
Regarding the Export issue you mentioned - we've identified an issue with exporting large projects with lots of video. We should have a fix out for it in a matter of days. (In the meantime, you can test export with a smaller project or the built in sample course.)
Mark, Rise is a basic eLearning tool. If you have something like a manual that needs to be turned into an ebook, I would use Rise. Or a simple page, turner course, I would use Rise. For anything else, I would use Storyline. There isn't a timeline in Rise, so you can't synch text with audio like you can in Storyline.
4 Replies
I would expect you would continue creating courses as well as creating courses using Rise as well.
They are really to different authoring environments for different use cases. Storyline has a blank canvas approach that will allow you to create what you want within the slide, but it produces non responsive slide based learning, which on mobile devices may restrict the usability (may!).
However Rise is a template responsive course that will give a great experience on Mobile devices as a well as desktop, but to deliver this you are restricted in how the interactions work and the customisation of the theme. At the moment the theme can have a single colour change and a font change. This doesn't mean you cannot build great learning because you can, I would see Rise as another tool in your armoury rather than as a replacement for Storyline.
I had been wrapping up the finishing touches on a course I built in Captivate (please, no throwing eggs at me folks) earlier this week and decided to try Rise out by converting this course to a Rise project.
The usability, from an authoring standpoint, of Rise is phenomenal. Super fast and slick. I didn't encounter any bugs with the authoring. Export doesn't work as of now, so it's not usable for me, so I abandoned the project.
To answer your question - I think the biggest thing to consider is the paradigm shift required of your design for Rise. The vast majority of elearning courses use a voice narration to "drive" the content. In other words, voice narration plays while visual elements are timed to animate/appear on the page to the user.
While you could accomplish this through video, and while there is an audio component in Rise, it's not really designed for that type of approach, nor should it be IMO.
It really should only take an hour or less to build a quick sample course and, through that, get to know how it works, what the available blocks/lessons are and how they work in a course, so I recommend you just jump in and build a project.
mark
www.elearninglive.com
Hey Mark - thanks so much for your warm words about Rise!
Regarding the Export issue you mentioned - we've identified an issue with exporting large projects with lots of video. We should have a fix out for it in a matter of days. (In the meantime, you can test export with a smaller project or the built in sample course.)
Thanks again!
Mark, Rise is a basic eLearning tool. If you have something like a manual that needs to be turned into an ebook, I would use Rise. Or a simple page, turner course, I would use Rise. For anything else, I would use Storyline. There isn't a timeline in Rise, so you can't synch text with audio like you can in Storyline.
This discussion is closed. You can start a new discussion or contact Articulate Support.