The new year is just around the corner, literally just a couple weeks away. And with every new year comes new expectations and resolutions.
While resolutions are often at a personal level, I am going to suggest that the elearning industry collectively makes a resolution together.
Whether you are an instructional designer, product creator, manager, or CEO – if you are involved in the elearning industry then our resolution for 2016 is this:
No more SCORM.
It has been a few years now that we’ve had Tin Can (Experience) API available to use.
Authoring tools make it simple to publish to Tin Can API.
There are some pretty great platforms that have emerged that make reporting easy with Tin Can API.
Listen, I understand that old habits are hard to break.
That’s why it’s important for all of us to support each other in this new resolution.
Just like many people have a workout partner to hold them accountable for going to the gym, elearning professionals need to hold each other accountable for promoting Tin Can API.
What does that mean exactly? It means creating less articles like this:
It’s time we really make an effort to start educating the masses about Tin Can API. It can be through casual conversation, articles, use-cases, infographics, or what have you.
The point is we need to commit or we will be stuck in the past forever, never quite shaking technology that is over a decade old and unable to keep up with the latest technological trends.
Together we can do this! 🙂
Hi James
I keep seeing this SCORM and TIn can
Would appreciate an article on what Scorm and TIn can are in a nutshell and the benefits of implementing them.
Here’s a nice infographic explaining SCORM. Here’s another for Tin Can API.
I agree. No more SCORM, use xAPI. It gives us more opportunity to capture data happening within and external to the LMS. Learning Locker is a great LRS to capture xAPI data.
So happy that I selected Leardash after I had enough confusion between M or WP based LMS.
Yes, No More SCORM
Wow. Way to throw iSpring under the bus.
Thanks for the comment Taylor. iSpring is actually pretty great. I don’t think linking to one of their articles is throwing them under the bus, but rather highlights the opportunity available to the major industry players (like iSpring) in leading the industry shift to Tin Can.
Hi all,
I’m pleased to inform you that iSpring included support for Tin Can API in May 2015, seven months prior to the publication of the SCORM article in the screenshot. We periodically provide updated walkthroughs on our blog for new readers to learn about things like SCORM and Tin Can, but as the author notes, the demand for SCORM is now dwindling. Another piece of great news is that as of June this year, iSpring 8.5 supports the new cmi5 standard, which combines the interoperability of SCORM and the flexibility of Tin Can.
Thanks for checking in, and stay tuned for more updates!
-Brian Tarr
iSpring Solutions