We’ve recently been delivering simple content just-in-time for access through the websites that are designed to run on mobile devices.
It was easier said than done, here are some lessons we picked up along the way.
Upside Learning has moved into providing solutions that include mLearning in some form or the other. In some cases, the solution revolved purely around mobile technology. We often answer the same questions repeatedly – where do we use it? How do we use it? What devices are suitable? While the answers depend a lot on the context in which the question is asked, there is a fair bit of common ground in each answer.
Right now, everyone wants to develop applications for mobile devices and in particular for the iPhone, as it has changed the way we look at mobile devices. There is lots of material available about iPhone development on the web but very little about how to go about it. While working on IPhone development I have collected some links and we thought of creating a training plan for iPhone development for other Upsiders.
As I mentioned in my last post about Rapid Prototyping mobile apps, I’ll be discussing levels of fidelity and how you could determine which level works for your mobile application design project. Fidelity indicates how closely a prototype resembles the final product. The term ‘fidelity’ is also commonly used in simulations and means essentially the same thing. There is a range of fidelity and mobile app prototypes can be placed along that range from low to high.
As we move more and more into the mobile space, we’ve found that there are several things very different from conventional courseware. One of the things that come to my mind right away is that in mobile, we are doing away with storyboards. Content is viewed differently, it’s data that has to be managed and rendered within the limitations placed by a variety of mobile devices.
This is the 3rd and final post of the series on creating successful m-learning strategy based on the workshop I attended at mLearnCon. You can read Part 1 and Part 2 here. In this part I am covering the Tool and Techniques discussed in the workshop.
The moment you start thinking about tools the varied platforms and their differences come up as real challenges. You could create simple HTML based courses (nuggets) or even simpler good old SMS based assessments.
We have been interacting with a number of clients, understanding their requirements and discussing possible learning solutions, and one thing that stands out in these discussions is the surge in the demand for mLearning solutions.
Am I glad to hear this; it was high time India jumped on the low-cost tablet and its happened!
Kapil Sibal announced it, and described it as a dream project. The tablet is intended for children from the primary to university level. With a package pricing approaching 35 USD, and finally to cost even less, it seems economical as well.
Recently, the first mLearnCon covering the A-Z in mobile learning was held in San Diego. Amit had summarized about it in his posts on How To Create Successful M-Learning Strategy: mLearnCon – Part I and Part II and Interesting Mobile Statistic.
Last week Google launched App Inventor a visual development tool to build Android applications. This tool will allow anyone to create an Android app without writing even a single line of code.
The App Inventor comes loaded with many blocks for creating UI elements, programming blocks, storage blocks, social blocks, media blocks etc, these blocks can be arranged in to logical sequence by drag and drop to develop an application.
This is the second post in a series of three I am writing. The posts are a review of the workshop I attended at mLearnCon on creating successful m-learning strategy (part 1 of the series is here). These are the three most important items I wish to share from the second part of the workshop.
