The development of Experience API has transformed the world of corporate training. This brand new specification for learning technology has opened the floodgates of knowledge.
Tin Can API, as Experience API is sometimes called, is an embodiment of innovation in the field of learning. This API could change the very face of learning because of the following reasons:
It helps break the barriers of network connectivity
This is arguably the most revolutionary development in the world of learning. Experience API helps effectively overcome the problem of loss of tracking course progress due to network interruptions.
Whenever a learning activity takes place, its outcomes are translated as Tin Can statements. These are stored on the device and when the connectivity is resorted, the collected statements are sent to a Learning Record Store.
This helps the trainee to pursue learning in a highly flexible manner. The cherished objective of anytime, anywhere learning is now fully realized.
Browsers no longer constrain access to learning
The problems associated with accessing courses on browsers are now history. Experience API has eliminated the dependence of the learner on this software, which are used to access data from the World Wide Web.
This novel development in the field of learning technology uses the power of APIs to facilitate communication, which is based on client server architecture. This facilitates the usage of Tin Can API in any application or script.
The learning potential of Mobile Apps is realized
Mobile Apps are the future of learning. The developers of Tin Can API understand this very well and have designed this innovative API to efficiently track learning from these incredible software applications.
Using Experience API, creators of learning activities could develop native apps that could be used to download several activities, store them on these gadgets and record Tin Can statements when these learning activities are carried out.
Cross domain learning is facilitated
One of the major issues encountered in SCORM, the technological predecessor of Experience API was the access of the content in one domain by the LMS in another domain.
This problem has been effectively solved by Tin Can API works via web services and data could be accessed from any server, eliminating the cross domain scripting problems.
Learning can be started on one device and ended on another
Experience API facilitates the learner to initiate a learning activity on one device (e.g.: Desktop) and complete it on another platform (e.g.: Mobile).
This is possible because the content is not stored in the LMS. This enables the developers of the learning activity to create different versions of it for each platform. This could be achieved by using a “state” API, which facilitates the storage of as many document pairs as the learning activity wants. By creating a “state” that could be shared across a single learning activity on different devices, platform transition is facilitated.
The LRS is “empowered” to see that learning activities on multiple devices as logically being the same activity enabling the trainee to learn on different platforms.
Thus, Experience API paves the way for hassle-free learning, bulldozing the technical barriers to acquisition of knowledge and skills. How do you view Tin Can API? Do share your thoughts with us.