The #1 Benefit of Tin-Can API
As many learning professionals know, mLearnCon has recently taken place showcasing many of the today’s leading practices and technologies for mobile learning. This conference, put on by the eLearning Guild, is the only conference dedicated to mobile learning today.
The conference gives a glimpse into where e-Learning and mLearning is headed in the near future, and one of the topics many looked forward hearing about was the announcement of Tin-Can API.
Not too long ago, I wrote about Tin-Can, and discussed some of my initial thoughts regarding the potential difficulties the project might encounter. However, since my original post, I have done some more reading on the project, its intended purpose, and ultimate goal for learning. I must say, the more I read, the more I am seeing the advantages of this SCORM evolution.
Rather than go on about the techy aspects of Tin-Can API, I prefer to look at outcomes, particularly the benefits that these outcomes offer – and the one benefit that resonates the most with me is Tin-Can’s recognition that humans are always learning… that the transmission of knowledge cannot be restricted (be it by an LMS or internet browser).
If you think about it, many LMS platforms today are rather confined in the way that the learning experience is structured. This, in part, is due to the technology that we had available when standards like AICC and SCORM were first created. Using newer, lighter technology, Tin-Can API opens the way we can document and administer eLearning/mLearning initiatives to a point where the internet, even computers, aren’t needed (as strange as that may seem).
This whole concept can be tough to wrap your head around, but I think it is a defining difference (and advantage) to what today’s technology enables us to do with our learning efforts. In fact, it is this very reason that we are strongly considering implementing Tin-Can API protocol in the initial release of WPLMS (as opposed to a future release, as originally thought).
However, this is not to say that the current SCORM/AAIC methodology has no value – not at all. Fortunately, traditional learning delivery is possible with Tin-Can API, so that option is still very much available.
If you haven’t taken a good look into Tin-Can API, I would suggest you do – if for nothing more but to keep up-to-date with industry happenings. It could very well be the new standard in our industry for years to come.