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....
It was always pretty shocking/insulting when the staff asks US why we need a certain feature. Are they not an eLearning company??? I believe this is just a stalling tactic. Shady how silent the staff have been on this thread considering the demand for this BASIC 'feature'.
I asked this 9 MONTHS ago, crickets.
"What is the rational for ignoring this basic 'feature' request?"
I am already getting a new laptop soon with Adobe products on it. I plan to do the same thing, MAYBE use Articulate here and there, but not as the primary authoring tool.
Then again I don't think a subscription expense for this out-of-date product (Articulate) is worth it, will probably just dump Articulate company-wide.