SCORM vs Custom API: Integrating Games with Learning Management Systems

When an educational institution commissions a game, one of the first questions on the requirements document is: "Will it integrate with our LMS?" The answer is almost always "yes." The follow-up question - how - is where the real engineering decisions begin. Our educational work ranges from The Language Conservancy (Vocab Builder) to projects delivered during previous agency tenures for institutions including Cambridge University Press, the BBC, and European university consortia through the EU Horizon 2020 programme (Navigo). Institutional projects repeatedly raise the same integration questions: where the game runs, how identity is passed in, what progress must be reported, and which system owns the learning record. This post compares the two primary approaches to LMS integration - SCORM (the established standard) and custom APIs (the flexible alternative) - and provides practical guidance on when each approach makes sense.

What Problem Are We Solving?

Before comparing solutions, it is worth being precise about what LMS integration actually needs to accomplish:

• Launch - the LMS needs to open the game in the right context (correct student, correct assignment, correct lesson).
• Track progress - the LMS needs to know how far the student has progressed through the content.
• Report scores - test results, quiz scores, and performance metrics need to flow from the game back to the LMS gradebook.
• Record completion - the LMS needs to know when the student has finished the activity so it can unlock the next one or mark the assignment as done.
• **Resume