After SCORM 1.2 and SCORM 2004, e-learning tracking was no longer limited to launches, completions, scores, and LMS-bound runtime data.

xAPI introduced a different mental model.

Instead of asking, “Did the learner complete this course?”, xAPI makes it possible to ask, “What learning experiences happened, across which systems, in which context, and what do they tell us?”

This series explores xAPI from a developer and implementation perspective. We will move from the basic structure of xAPI statements to deeper decisions around verbs, activities, IDs, profiles, launch, validation, reporting, and real-world LMS coexistence.

The goal is not only to understand what xAPI is, but to understand when it is useful, how to design it responsibly, and why many xAPI projects succeed or fail based on decisions made long before the first statement is sent.