I’m creating a series of courses in Rise that use checkbox lists as a vehicle for collating insight about a user’s current situation that can be referred back to later and even post-course completion.
Because the checkbox lists in Rise appear to me to serve no purpose, I’m having to use Storyline blocks with Javascript to store variables, then recall them later in the course so that the user can print all checklists with their selections, so they have a record of what they have done, and what is outstanding. All work perfectly until viewed on anything smaller than a desktop/laptop.
Rise seems to be quite flawed when it comes to using Storyline blocks. As in, there is no fallback option for content that won’t work as it should on certain devices. Having a fallback option is pretty basic for a responsive product; if the viewport is desktop/laptop, then show section A. If the viewport is smaller than a desktop, then show section B.
I can’t be the only person that can’t see any value in a checkbox interaction if the data can’t be stored and recalled later.
This would give the checkbox some meaningful purpose, as the user could add to it later in the course or print various checklists within a course at the end of a course, with all their selections displayed, allowing the user to see which tasks still need to be completed.
For the price of Articulate 360, I’d really like to see one of two things happen, but ideally both:
1. Develop the ability to store and recall variables in Rise without the need for Storyline
2. Develop a fallback experience so users on a desktop can see the rich Storyline content, but users on smaller devices are presented with an alternative (lesser) experience using a Rise block.
The black screen and play button is one of the worst user experiences I’ve seen in a long time and completely breaks any flow state achieved.
It’s really not difficult from a development perspective.
Are any of these in the pipeline?
