If you’re at all even remotely associated with support for the eLearning industry (i.e., instructional designer, training developer, software developer, LMS vendor, social networking host provider, CRM provider, etc.) then you’ll be interested in this series.
At last year’s DevLearn conference (DevLearn11), the anticipated release of Articulate’s Storyline authoring tool was all the rage. This year (DevLearn12), the buzz was all about Tin Can (a.k.a. the “Experience API”, a.k.a. Tin Can API). In fact, so buzzy was it that I actually heard the “R” word used several times throughout the conference. And…AND, if you can believe it, the “P” word (*gasp!*) was actually used by one of the guests in a panel session.
eLearning Professionals Are Confused
The thing is, in the months leading up to DevLearn, and extending to the days following DevLearn’s opening keynote, I asked a bunch of you, my professional eLearning colleagues and friends, if you could explain to me what Tin Can was about and how it differs from SCORM. Not surprisingly, the answers the lot of you gave were all over the board; they were speculative at best. Hell, I wasn’t immune. I read the discussions on the TinCanAPI consortium website and, by DevLearn’s kickoff day, I still couldn’t wrap my head around it enough to be able to articulate a value proposition.