My colleague Mark Wilcox, now the product manager for Oracle Virtual Directory but formerly a developer at WebCT, wrote me with some good advice to mLearning developers:
I wrote the first mobile app for WebCT as my last presentation at WebCT’s user conference before leaving. That may have been the first ever mobile app for any LMS, now that I think about it.
Here is the advice I would give for apps that are thinking of a mobile strategy:
- Focus on having a decent experience using the Android and iPhone browser. Luckily it’s basically the same browser. Nozbe – which is a new Getting Things Done service – does this very well. I have it linked off my iPhone home screen and it looks/acts just alike an app at that point.
- If your app has data that updates – for example discussion forums, calendar reminders, notices of new assignments – make sure those area available as RSS/Atom feeds. This makes it possible to consume them in a number of different formats and opens possibility to get a mobile app using one of the app-generation services like AppMaker or MobileRoadie.
- I would stick with a mobile web only strategy unless you have a true compelling reason to build an app. One reason could be that you need to send push notifications – a mobile Web can’t yet do that, but a mobile app can. Another could be to control the brand experience. For example you don’t want people to have a bad idea about your product because you let a 3rd party app be the mobile app and it’s not implemented well. I wouldn’t try to prevent those apps if you have a public API , but I would want to make sure I had the best app optimizing the experience. I think EBay has done this particularly well. Oracle has also released a few iPhone apps which give an idea of how to take subsets of functionality and optimize them for the mobile phone.
