Forum Discussion
xAPI Full Capabilities in Rise
I'm building a number of Rise modules for a client and they love the platform, however they are looking for a solution that will allow them to capture robust metrics from the learning using xAPI to show how learners are interacting with the content. Examples include tracking Knowledge Check selections and attempts, interaction with audio, video and interactive blocks, etc. Currently the xAPI tracking in Rise is no different than what SCORM provides. Alternatively, could the content be exported in a way that allows developers to add in their own API statements post export? Data and analytics are becoming a massive ask from our clients and I'm still only able to accomplish this by building our own custom platforms.
More crickets from Articulate. At this point it seems clear that they either can’t add this capability or do not wish to. Very disappointing.
Rise 360 does support xAPI for Page clicks ("Experienced & progressed tags"), BUT it only reports an unreadable ID URL code to the LRS, not the Page/Unit Title. That ID number is worthless in the reporting. The Page Title in the xml file, so Again I ask Articulate why they can't report that human readable title to the LRS.
Example:
Jerry Donney experienced 'http://trNN5DPQAKpd4JcdC0GTEKI1idMMX9Zb_rise/J8ronUihB1-PRqoQ__6pDHTQjHm4nDAs'
Jerry Donney progressed 'http://trNN5DPQAKpd4JcdC0GTEKI1idMMX9Zb_rise'
We could use Storyline blocks to add code, BUT the problem remains that Articulate will not fix the "PLAY" arrow on Storyline blocks (in Rise). which means you can't hide the code undercover. User is forced to see and to click the big Play Arrow on all mobile devices :-( Please tell us that is getting fixed soon.
It's a similar level of frustration with quiz reporting. Trying to correlate useful data like the most frequently selected incorrect answer, or the hardest question is totally ridiculous.
This thread has been open for 3 years and there's not a sniff of progress.
I have given up hope, and now we're using Adapt to supplement the lack of meaningful data. I love Rise and I would really like it to be the product it deserves to be, but that feels a long way off right now.
Rise has its own LMS now. It offers full trackability of its rise elearning. I guess the reason why Articulate has been cautious about fully enabling xAPI statements is because it will direclty compete with its own LMS. Just a theory. And adding another vote to this.
This theory is correct. In other posts I've seen about this topic, the company's response has been to use Rise.com (the LMS) if you want any kind of useful data. As someone who works in higher education, I get the sense that Articulate products are more geared towards corporate training because there's no way colleges and universities are going to dump their LMS and adopt Articulate's LMS.
So far we have nearly 65 comments on this thread, most of them "votes" for this feature. How many more are needed before Articulate addresses it?
Just like all the other 3-4 year old Rise threads, it won’t get addressed because there is no clear route to monetisation. It’s disappointing, but I’ve been through all the stages of grief and I’m at acceptance.
Just had another client ask me about xAPI capabilities and Rise. any updates on this?
It's been almost four years and many users have been asking to develop the feature. Any updates?
This is another 2 year old thread with people looking for some kind of communication. Is there any chance of getting an actual update or some kind of roadmap?
Would like to know of the status on this request. RISE is a great rapid e-learning dev tool, but without the ability to control xAPI statements (and output more than basic SCORM), it is hard to justify adoption. xAPI 2.0 is due to be ratified in 2022 by the IEEE as the new standard for interoperable learning data but if designers cannot implement it (it is not truly supported) then the rapid development will be offset by the lack of data we can acquire from our design, and DATA is going to win out in the end. We must be able to measure, report on and improve our learning.
As designers we must learn to look behind the promises of xAPI support (and we are); it often feels much like buying "Organic" Food.
