Starting Slowly with mLearning

Over the past few weeks I’ve built a few small mobile learning (mLearning) applications and I’ve learned several lessons along the way. Here’s a brief recap:

• First, as I’ve mentioned before, the point of mLearning is not to create a 45-minute course that can be accessed on a cell phone. mLearning is best used for performance support: quick, easy look-up tools for your learners are a good place to start.
• Second, it’s easier than I originally thought. I’ve found that a small web page – when formatted properly – can be the simplest way to start with mLearning. Give it a shot: Create a basic HTML page, put it on a web server, and then go to it using your phone (if the phone is web-enabled). That’s it. Of course, if you add images and Flash, things get more interesting. Take it one step at a time and you’ll see that it’s not too bad. (Now, don’t get me wrong, there are some parts of implementing mLearning that get complicated, but I’ve found the hardest parts are related to politics and logistics.)
• Third, people get really excited when you demo what you’ve created. After doing a demo of your work, ask people to start thinking of additional mLearning tools that would be helpful. I got some great ideas from colleagues just by giving them a quick demo and then following up with questions. I kept hearing, "It would be really cool if you could (do XYZ)."
• Finally, Adobe’s Device Central is very helpful for testing. Device Central is an emulator that allows you to test your mLearning apps on your PC and see how they’ll render on a variety of cell phones.

Have you tried building mLearning apps? If so, share some tips here!