Working with standards is hard work

Standards are important. At their best, they allow software and systems from independent vendors to function well together without custom work for each combination of systems.

Ideally, standards would be precise, and narrow, and suitable to the specific problem they are intended to solve. They would be consistently implemented by all parties, and these disparate systems would just work well together without any hassle. In eLearning, this isn’t the case. Getting things to work well together is frequently difficult.

At Rustici Software, we have experience ensuring eLearning technologies work well together. We focus primarily on eLearning standards (some may say, “LMS standards”) focused in corporate learning and development. Yes, this is a little niche. We found our way to this business by solving problems for customers who didn’t want to be bothered with the minutiae of thousands of pages of arcane specifications.

Over the past 15+ years, we have helped hundreds of systems and tools implement support for eLearning standards. As a result, the vast majority of transactions across the eLearning ecosystem depend on software created by Rustici Software. You can see this in action on our SCORM Stats webpage, which tracks how people are using SCORM in SCORM Cloud. Since Cloud is a well-used community tool for those testing and developing SCORM, its usage is illustrative of the overall adoption of SCORM.

Why we consider ourselves experts in the eLearning standards

  • We read the specifications. First SCORM 1.1, 1.2, and 2004 in all its incarnations.
  • We answered questions, and consulted with companies that were trying to implement these standards and work well together.
  • We discovered that the letter of the specifications wasn’t enough, and we found solutions that tolerated a variety of implementations.
  • We contributed to the evolution of SCORM, from 1.2 to 2004 2nd edition and forward.
  • We built software that integrated elegantly into other companies’ solutions, and sold it to more than half of the LMS and content providers in the eLearning markets.
  • We support our customers and anyone who asks us for help with eLearning or LMS standards problems.
  • We collaborated with the industry to identify SCORM’s shortcomings and developed the initial version of xAPI (called Tin Can API) and continue to contribute to its evolution today.
  • We support at least 300 LMSs, more than half of the LRSs that exist, and millions of content deliveries every month with our various products.

We can help you support the standards too

The software we sell solves problems developers can solve on their own. We share resources openly because we are confident that the developers, and the companies they work for, will be better off if they buy our software in order to focus on differentiating their product from competitors.

  • Find a solution for you

    If implementing eLearning standards seems daunting to you, we’re here to help. Our products are created to solve common problems and are used by the majority of eLearning applications on the market.

    Find a solution
  • Implement SCORM on your own

    If you’re building an LMS, or creating content, SCORM remains profoundly relevant. It’s adopted more widely than any other learning standard, and supporting it is a requirement in most contexts. SCORM.com is a great starting point.

    Learn about SCORM
  • Implement xAPI on your own

    If you’re building an LRS, or imagining learning activities that live outside an LMS, xAPI and cmi5 are emerging and afford you opportunities that SCORM does not. The basics are available at xAPI.com.

    Learn about xAPI

Still not sure what to do?

Don’t worry, we’re here to help. Contact us to see how we can best support you.