I'm just wondering if there have been any successes/challenges with launching mobile courses to the smaller mobile screens on HTML 5 compatible smartphones? I'm tasked with designing for a BYOD (bring your own device) culture with BlackBerrys, iPhones, Androids (oh my!) and Windows Phones.
I'm new to storyline so before I design something crazy I just wanted to see how it has gone for others.
The prevailing opinion on mobile content is to avoid "shrink-ray conversions" You'll have some trouble hitting all of those platforms with HTML5. The older Blackberry will present you with a double-whammy. A smaller screen with different proportions than the smartphone form factor.
If I were targeting phones, I'd start with a tiered approach. I'd want to drive this through some healthy questions:
What's the simplest thing I can bring to the phone that will have utility? Audio, video, and text are all relatively universal (Blackberry is an outlier but there are some options there as well). So how can I provide some simple (emphasis on simple) tools to support work in the workflow? How can I provide spaced practice or spaced exposure? How can I provide pull tools? How can I build small moments that fit comfortably within a mobile context?
Can I setup something on the phone version that gives the best of two worlds (where and when the participant is + the full power of the desktop)? Maybe an adjunct set of tools, documents, and media that support independent study or support on the go while providing a fully enhanced experience on the desktop?
I think building facilitated experiences for mobile is distinctly different in both design and implementation. That doesn't mean the mobile and desktop experiences can't work together for a more effective punch. But I think that leaves you using Storyline for desktop and something else for the phones
1 Reply
Hey, D!
The prevailing opinion on mobile content is to avoid "shrink-ray conversions" You'll have some trouble hitting all of those platforms with HTML5. The older Blackberry will present you with a double-whammy. A smaller screen with different proportions than the smartphone form factor.
If I were targeting phones, I'd start with a tiered approach. I'd want to drive this through some healthy questions:
I think building facilitated experiences for mobile is distinctly different in both design and implementation. That doesn't mean the mobile and desktop experiences can't work together for a more effective punch. But I think that leaves you using Storyline for desktop and something else for the phones
This discussion is closed. You can start a new discussion or contact Articulate Support.