The Experience API—formerly known as the Tin Can API—is the new thing in eLearning. Not tied to learning management systems (LMSs), able to use in almost any form you can imagine, and much more flexible in where, how, and what data it can help collect, the Experience API (xAPI) is the clear successor to the Sharable Content Object Reference Model (SCORM). You are most likely familiar with SCORM and how that SCORM-compliant content looks, feels, smells, sounds, and tastes. xAPI presents a whole new set of senses with which to deal. xAPI-compliant content can look and act very different from its SCORM counterpart. For example, xAPI-compliant content no longer needs to launch from within an LMS. And speaking of LMSs, yours might not speak the language of xAPI, so even after you do all the work to build your amazing new course, your LMS might not be able to use it!

In this session, you will explore what makes xAPI tick and what makes it different from SCORM. You will examine the evolution of requirements as you move learning content from SCORM to xAPI. You will look at some possible pain points and traps that you might fall into along the way. But rebuilding your content isn’t enough to make use of xAPI. You also need a Learning Record Store (LRS) to receive xAPI statements. You will review some available LRS options and learn what you need to know to make an informed decision. You will leave this session understanding the risks, the potential benefits, and the work it will take to convert your content from SCORM to xAPI.

In this session, you will learn:

  • What the Experience API (xAPI) is, how it works, and what is required to use it
  • The key differences between the Sharable Content Object Reference Model (SCORM) and xAPI
  • How to convert from SCORM to xAPI
  • The risks and benefits of converting your content from SCORM to xAPI

Intermediate and advanced  designers, developers, project managers, and managers. Attendees should be familiar with SCORM and general LMS concepts.