With Articulate able to publish to Flash Lite 3 and Android devices with Flash, and with Storyline coming soon with iOS/HTML5 support (as well as a new Suite later in the year), I'm wondering if we need a thread on best practices for designing m-learning.
How is designing for m-learning different than designing for a "regular" monitor screen? What things are the same?
I admit, I'm a neophyte in this area. Anyone got any best practices, web links, resources, thoughts, things you've tried that work, etc., that you'd like to share?
I have built a few in HTML and the best advice is to remember the device. Silly, I know, but certainly hotspots are something you may want to avoid. Big buttons are a must for navigation. The problem arises with assessment. Even with multiple choice answers you may be limited to 3 answers depending on question, screen design etc.
Also compatibility is a problem with Apple as well. It is frustrating for very well versed learners not to be able to use their iPhone or pad to get content -- that's why we've always done mobile in HTML. You can use Google App inventor to build some cool Android apps, but you still have not solved the Apple problem. Soon, though, I think software cos will gt on board with the one development platform, many outputs solution... we shall see.
I am also looking for the mobile solution for both platforms. How do you develop a product for both without the duplication of efforts. We want lean production here! With such a diverse usage of tablets now, how can you limit to what the student will have. Do you make the Apple user's buy the other tablets? I don't thing this will happen.
Come on Apple, forget about the Flash thing and make it helpful for us developers to do our jobs. My $.02.
Any and all information from these blogs are helpful for me. Thanks all!
I just read a book that I'd like to suggest. It is geared toward creating Help (our technical writer shared it with me), as opposed to creating mLearning, but it definitely has some valuable information in it.
"Developing User Assistance for Mobile Applications" by Joe Welinske
I think audio and video are great on most devices. Anything tuned for a large screen probably won't deliver a good experience (Powerpoint, long documents). Brief interactions that display very little on the screen at a time, offer limited choices, and leverage presentation elements that are easily distinguished on a small screen probably work out better. The typical PPT conversion will likely produce a frustrating experience unless it's designed with small screen in mind.
Reading on devices isn't always the most comfortable activity. I'd say stick with media that minimizes the necessity to pinch zoom or scroll on smaller devices. I think there's some data out there that indicates how many folks with portable devices actually read with them (I know there are quite a few that do, but I think the data shows most do not). This is particularly important for those still toting around the old Blackberry. I read somewhere that this is the most prevalent mobile device. That screen is excruciatingly small. People read email on it, sure. But they are nuts Ever seen a crackberry-head in a meeting? Pretty funny:)
1) For each screen, design so the user only has to scroll one screen down. I read somewhere to abide by a 600 character limit per screen, which amounts to about the same.
2) Keep course duration to 5 minutes or shorter. On one topic or just a change from an existing training.
Such an important topic and an area of development that is set to grow.
I have found this useful page on Quora which explores the vital elements needed to make m-learning work and there's a lot of discussion that appreciating and factoring-in 'context' is crucial.
Hi, Just read a GREAT book on this called Mobile first by Luke Wroblewski. Like it says, you design for mobile first. And it has pictures to show you the difference good clear design can make.
12 Replies
This is a great topic Gerry. I too am interested in hearing what people come up with.
I'm interested also! I'm doing some research on this currently and will let you know what I find out. Please let me know if you find anything also.
Thanks, Lisa! Surprised there hasn't been more activity here on this topic.
Or is this a cause of the "hype horse" coming before the cart? From some organizations here in our location that seems to be the case.
I have built a few in HTML and the best advice is to remember the device. Silly, I know, but certainly hotspots are something you may want to avoid. Big buttons are a must for navigation. The problem arises with assessment. Even with multiple choice answers you may be limited to 3 answers depending on question, screen design etc.
Also compatibility is a problem with Apple as well. It is frustrating for very well versed learners not to be able to use their iPhone or pad to get content -- that's why we've always done mobile in HTML. You can use Google App inventor to build some cool Android apps, but you still have not solved the Apple problem. Soon, though, I think software cos will gt on board with the one development platform, many outputs solution... we shall see.
That's really good advice Benjamin.
Also, I wanted to share some information I heard regarding best practices:
I'll add more when I know more.
I am also looking for the mobile solution for both platforms. How do you develop a product for both without the duplication of efforts. We want lean production here! With such a diverse usage of tablets now, how can you limit to what the student will have. Do you make the Apple user's buy the other tablets? I don't thing this will happen.
Come on Apple, forget about the Flash thing and make it helpful for us developers to do our jobs. My $.02.
Any and all information from these blogs are helpful for me. Thanks all!
I just read a book that I'd like to suggest. It is geared toward creating Help (our technical writer shared it with me), as opposed to creating mLearning, but it definitely has some valuable information in it.
"Developing User Assistance for Mobile Applications" by Joe Welinske
You can find it here: http://www.writersua.com/mobile/book.htm
I think audio and video are great on most devices. Anything tuned for a large screen probably won't deliver a good experience (Powerpoint, long documents). Brief interactions that display very little on the screen at a time, offer limited choices, and leverage presentation elements that are easily distinguished on a small screen probably work out better. The typical PPT conversion will likely produce a frustrating experience unless it's designed with small screen in mind.
Reading on devices isn't always the most comfortable activity. I'd say stick with media that minimizes the necessity to pinch zoom or scroll on smaller devices. I think there's some data out there that indicates how many folks with portable devices actually read with them (I know there are quite a few that do, but I think the data shows most do not). This is particularly important for those still toting around the old Blackberry. I read somewhere that this is the most prevalent mobile device. That screen is excruciatingly small. People read email on it, sure. But they are nuts
Ever seen a crackberry-head in a meeting? Pretty funny:)
Forgot to mention this book. Clark Quinn published this earlier in the year (or maybe late last year). It's supposed to be pretty good:
http://www.amazon.com/Designing-mLearning-Organizational-Performance-ebook/dp/B004LP2I28/ref=sr_1_2?ie=UTF8&qid=1310079975&sr=8-2
Here are my thoughts:
1) For each screen, design so the user only has to scroll one screen down. I read somewhere to abide by a 600 character limit per screen, which amounts to about the same.
2) Keep course duration to 5 minutes or shorter. On one topic or just a change from an existing training.
Such an important topic and an area of development that is set to grow.
I have found this useful page on Quora which explores the vital elements needed to make m-learning work and there's a lot of discussion that appreciating and factoring-in 'context' is crucial.
http://www.quora.com/How-do-you-best-design-for-mobile-learning?srid=JwI
Hi, Just read a GREAT book on this called Mobile first by Luke Wroblewski. Like it says, you design for mobile first. And it has pictures to show you the difference good clear design can make.
I am not a tech person and found this very helpful. http://www.abookapart.com/products/mobile-first. You can even download it to a phone to read!
Thanks for your great tips here, too. I'm learning lots.
This discussion is closed. You can start a new discussion or contact Articulate Support.