The following documentation is to explain and document the integration of xAPI with Hype. It's in the form of a Hype extension.
I'm an instructional designer, so the documentation is created from a learning designer's perspective.
This document looks at:
- What is Hype?
- What is xAPI?
- Why we are integrating Hype and xAPI?
- Hype project structure when using the xAPI extension.
- How did we integrate Hype and xAPI?
- Sending a statement.
- Pulling data from an LRS.
We won't be teaching you how to use Hype or xAPI. You will have to do your research on xAPI, and how to use Hype. These are both powerful tools in the hands of a learning designer.
Also, as within the spirit of Hype as an application, this extension is open. There are a lot of open doors that can be used to make its interaction with xAPI very dynamic. I am sure many designers/developers will be able to do amazing things with this extension, but I'm not one of those designers/developers that can just jump in and fly. It's baby steps for me. I first want to know how to do the basics well, and then as I explore HypeXAPI, I can get more creative.
The value of xAPI === quality of your data. Which means that if you work creatively with your statements, it could decrease the quality of your data. Make sure that you document any variation in statements properly, because it is not going to make sense to someone else, or even yourself later.