Here's a doozy: Building a "responsive" course to work on an LMS
Mar 27, 2015
Been scratching my head over this one for the past few days so thought I'd see if anyone else has some ideas/been down this road before. I am attempting to create a course that will work on both desktop/tablets and on mobile phones. I've seen some very helpful posts about sending learners to different course (story) versions based on device...but, because my course also needs to go on an LMS, I am limited to developing 1 course (SCO) and creating different scenes within it for the different device experiences (this is an assumption I am working under so feel free to shoot down if incorrect).
BTW - I have found a goldilocks size that works well across desktop/tablet/mobile: 1108X554, no skin elements.
So, basically I am wondering if there is a way to direct the learner to one scene within a story based on device (preferably automatically). I'll worry about the bookmarking implications/challenges (yeah, the project requires that too) later, ha.
THANKS!
7 Replies
You might be able to do a media query using javascript, then pull those variables into storyline. Once in storyline you can do a conditional trigger that will send the user to certain scenes based on those variables.
BTW, thanks for not calling it "Responsive eLearning".
what about the publish settings for HTML5 and/or storyline player won't they make sure its viewable on multi platforms?
Hi, Steven -- In case the participants in the thread are no longer subscribed, you are welcome to reach out to them directly using the "Contact Me" link on their profile pages. :)
Good reminder Christie, I've now done that. Thanks.
Fantastic, Steven -- hope you get the information you need. :)
Hi all - Just following up as I was asked if I found a solution. Unfortunately, I did not with Storyline and bit the bullet and moved to a HTML5, homegrown solution. Not exactly rapid, but it is getting the job done. Crossing my fingers for responsive capabilities in future releases!
Thank you for popping in with an update, Damian. :)
This discussion is closed. You can start a new discussion or contact Articulate Support.