Tin Can API

[sachintholia]

After SCORM 1.2 now we have Tin Can API Which is being adapted very quickly with elearning community. Docebo cloud also have started.
Is our team ready to work with this and improve Docebo Open Source. Does this system upgrade required or current system is good enough at this point of time.
Any suggestions / comments ?

[max]

Hi,
good point.
In our market (Italy, US) Tin Can is still not an issue, but it's true that it will be a long transition and development, so we better start early. Authoring tools already publish in Tin Can, but customers still ask (ask us) for Scorm. And produce Scorm themselves.
In our roadmap, we'll think about Tin Can not before next year.
Have you already made some thoughts or worked on this issue?

[ee0pdt]

I think the problem with Tin Can is that it generates a lot of data and I've not seen a good solution for how to report on it yet. But the ability to use it within mobile apps does make it tempting...

[max]

Hi and welcome on board, ee0pdt. Even yours is a good point, and interesting thought. Actually, if not with mobile apps, scorm works at least with mobile devices.
Concerning reporting, maybe one could settle for the lowest common denominator at the beginning and add other layers of data reporting later.

[ebsi]

It could be a good solution to develop a player which will play tin can api content and be able to set the details of a learning record store. I use Grassblade LRS and its very good and has good reporting combined with Articulate Storyline 2 content exported to Tin Can API.

The LRS costs USD 199 which is a good investment for the money given all the functionality it provides.

Happy new year!

Thomas

[canelli]

We will very happy to implement Tin can API . Why did you not sponsor the development ?

[ebsi]

How much would such development cost?