Universal plugin SDK

Interoperability: universal plugin SDK

In short:

  • The Universal plugin SDK is an open-source framework for developing edtech plugins that are compatible with all major educational software (build once, plug to many)
  • The Universal plugin SDK will allow data space participants to easily integrate any solution into any other without having to develop integrations each time


Start date: T0 + 16 months (T0 = expected: Q1 2023)
End date : T0 + 36 months
Duration (in months): 20

Where we are now

  • The work will start Q2 of 2024. Want to learn more and join the effort: join here!

Objectives and Expected Outcomes

The objective of this building block is to specify and develop a software development kit (SDK) for the development of universal plugins, i.e. plugins that are compatible with the main softwares used in education and training. Most software such as Moodle, Blackboard, Canvas, Microsoft Teams for Education or Zoom allow the enrichment of their functionalities via plugins/APIs. Each of these platforms actually requires specific developments, according to different languages (php, C# .net, etc) and/or different data models. Each integration/plugin development represents a significant cost for edtech companies who usually only integrate or develop the plugin for the main softwares reinforcing data centralization.
This task aims to develop an open-source framework for developing plugins that are compatible with all major educational software (build once, plug to many). This would simplify plugin development in a similar way to what React Native has been able to do for multi-OS (iOS/Android) mobile app deployment and what IMS has started to do with the Learning Interoperability Tool (LTI) standard.
A framework that fills in the missing pieces of interoperability would therefore reinforce the dissemination of innovative products and services developed by the European edtech ecosystem. It should also be noted that this would allow for the operationalization of the right to data portability, which is supposed to be guaranteed by the RGPD but which in practice generally only translates into the possibility for users to recover their data in .zip format. With more interoperability between LMSs, the learner will be able to more easily allow the circulation of his data from one software to another without being locked in (vendor lock-in).


  • State of the art of the plug-in frameworks of the main software and tools used in the field of education and training in France and in Europe from the list identified in the working groups of the Data space Education & Skills (i.e. Moodle, Teams, Zoom, LTI)
  • Modeling of priority functionalities
  • Design of the development kit (SDK: Software Development Kit) and generic and reusable modular elements (templates)
  • Development tests from the SDK
  • Drafting of public documentation, hosting and putting it online


T0 + 16
Documents : Specification and state of the art
T0 + 24
Development of the SDK in beta version (v0)
T0 + 32
QA test report
T0 + 36
Final version (v1) of the SDK and public documentation