The Biggest Flaw with Articulate Rise
Last year Articulate unveiled a new offering (or several new offerings to be more accurate) under the umbrella of “Articulate360”.
The entire presentation is quite impressive. This presentation is equally matched by the updates they made to their line of products.
For years Articulate has been known for Articulate Studio, Articulate Storyline, and a smattering of other tools designed to make it easier for elearning developers to create their courses.
They now introduced an exciting mobile learning component in Articulate Rise and it looks great… or at least it looks great on the surface.
You see, from a visual standpoint the platform looks great, and if it is anything like other Articulate products then the learning curve will be quite minimal. But when you look under the hood you might be shocked at what you see (I know I was).
This is a big deal.
It’s a big deal because the industry adoption of Tin Can API has been an uphill battle given how firmly SCORM has been entrenched in the market. When one of the largest industry players neglects Tin Can API for their newest offering it does the elearning industry a huge disservice.
I couldn’t find anywhere that indicates Tin Can API is on the Rise roadmap (if you happen to know where it is then please post it in the comments), but it’s silly that it’s not included from the get-go to be honest.
I can’t help but wonder: why release a cutting-edge tool that neglects cutting-edge reporting technology?