Forum Discussion
Image link in Rise
Four....years....three years of being strung along only to be told it's not coming. I am in awe at the lack of meaningful responsiveness from the development team. While I value tremendously the creativity and imagination of this community of designers, it seems like half the posts are about designing work arounds for basic features this software should have out of the box.
Years ago, a "helpful" suggestion from Staff was usually a work around for a young and promising product, with confidence that the product was evolving and these issues would be addressed. Now, a "helpful" suggestion from Staff means "wait four or five years and we might get around to looking at it a bit before telling you it's 'not on our roadmap.'" Basically, if it doesn't already exist, good luck asking. But meanwhile, look at how accessible we are! Confidence in "adding it to our feature request list" is shot. Just say no.
I am also breathless with dismay that, years into this thread discussion/request, a member of Staff came to the group to ask why we might need/want clickable image links in Rise...and expected the customer to take time out busy schedules to provide specific examples. This is such a basic, obvious feature...I can't tell if they were stalling for more time or if the developers truly don't understand the business their customers are in.
This week, our team formally opened discussions about sunsetting Articulate as our primary design suite and demoting it to a basic solution for occasional use, rather than a creative one for innovative learning.
Four years....
Hi Julia,
That's precisely what we were doing. Our roadmap was to invest in many new licenses but now we've decided to keep to one and invest elsewhere. Shame as this really has potential if the basic functions had been comprehensively designed out. There are at least a dozen missing unfortunately, including image links. What about knowledge checks that allow users to generate guesses without being told they're wrong or right after and just use as a discovery based primer for the feedback content that follows.. We feel basic pedagogical approaches are not being acknowledged by this authoring platform.
The hard pill to swallow is that this really could be great, but just isn't adapting to multiple customer needs simultaneously - and we're talking about the basic stuff here.
- JuliaMays3 years agoCommunity Member
Hi Jonny,
I completely agree. The list is long, and some of it is just plain silly. Being able to add a thumbnail over a Rise video. Being able to adjust the compression amount on imported videos. Basic Knowledge Check controls that allow us to match the response options to the nature of what we're trying to teach. Let's not even get started on the request for the Morph transition....
In the end, it comes down to time. If I'm spending more time compensating for Articulate's shortcomings than I am designing product, I'm losing productivity. I spent over an hour yesterday compensating for blurry videos imported from crystal clear original files. Pulling individual, renamed videos out of the Storyline output file, matching them to the original video file, renaming that original file to the new rename, and then overwriting the video inside the Storyline output file...just to undo the consequences of video compression that I can't control.
A few weeks ago, I had to pull twelve individual videos into Vyond, drop a screenshot still pic in as a single first frame of the video, re-render that video and then replace the original video in Rise...all to get a thumbnail shot...a feature that already exists in Storyline.
Storyline blocks are not the blanket answer to missing basic features, either. They can be cumbersome, don't always quite play nicely with the LMS, and again...I'm wrangling two software packages to produce one result when I shouldn't be.
I just can't swallow the "not on our roadmap" response anymore.