Animation in Storyline through the Morph Transition

Agreed.  this is an ongoing active thread, and you've got customers going from discussing work arounds to discussing alternative software solutions.  I do appreciate the staff update, but the answer is coming across as dismissive.  Why is this not a higher priority?  Our work in Articulate has to compete with work produced by designers using your competitors' software, and as the months go by, my work is starting to feel clunky and old fashioned without this option. Please consider reevaluating your priorities and moving this request up. 

 Everyone ... I think the issue here is that:

•  Obviously, Articulate doesn't care about its customers.  If they did they would listen to customers.  Pure arrogance.  Same excuse again and again.
•  And Articulate doesn't have the developer knowledge and skills to develop the Morph transition. 

Agree, Articulate's answer is dismissive.  It's not a higher priority to them because of their arrogance.  They don't listen to customers. 

We shouldn't plead with them.

We need to move on and use a competitor's product, to a competitor that cares about the users of its product.

If we can influence more Articulate users to leave Articulate for the competitors, then watch how Articulate will be begging customers to come back by offering all sorts of enticements. 

I agree if they can revisit their priorities and I believe that they are listening to their customers it's just that Morph is not with a very high impact as we can proceed with alternatives. I visited their feature roadmap and I'm looking forward to those. Let's also consider their process as we all know that even in our own processes  and business requirements we sometimes or most of the time prioritize things based on impact, need, time and effort. Take care everyone!

I think it either: it would require a larger chunk of DEV time than Articulate is willing to allocate, or the way their development architecture is set up, it might not actually be possible for them to execute.

Software companies never admit that they can't actually do something, so they rely on the PR technique of stating that they're choosing not to do it. I think that if they could do it cheaply enough, they'd have done it years ago. Unfortunately, it's now been five years. Perhaps it's time to reinvent the wheel and blow-up the old code and start anew. You've gotten a LOT of miles out of this code, Articulate!

Very well said Patrick, I agree. 

Thanks. I also think that Articulate might not truly understand WHY we like the Morph transition. It's not really about the "animation" per-se. It's about how much (and what kind of) animation we can get—for the least amount of TIME invested. It's SO EASY to use. I see all kinds of suggestions for complicated workarounds, but those people don't seem to understand. I want to make these transitions in PowerPoint, and I want them to remain intact in Storyline. I can get so much out of that transition. Articulate needs to take to heart that we often have to develop to multiple platforms. Articulate 360 is not a one-stop-shop. The relationship between what I do in PowerPoint and what I do in Storyline—is symbiotic. Articulate needs to be going where PowerPoint is going.

And would it kill you (after this many years) to do a Mac version?

Hi Everyone! - As Lead Customer Advocate at Articulate, my goal is to work directly with our product team to voice your needs. I take into account every insight shared in our E-Learning Heroes community, and evaluate 100+ feature requests every week.

I understand your passion for this feature and share the same enthusiasm when I bring requests to our team.

To add more context, the need for Morph Transitions has impacted a low number of users, and that contributes to the priority we give it. Industry trends, new ideas, and complexity of a feature also weigh in on our decision process, but none of these factors have managed to move this one past the items currently on our product roadmap.

I hope this glimpse into our feature process will help address any concerns.

Bret, not that I doubt you, but may I ask what metrics you have to illustrate this low number of users, or how you gather this data? I've used Storyline at more than one company and I've never seen any sort of survey or similar.

I am sorry you do not see the need for morph. Your competition, iSpring, allows me to retain all of my morph transitions when creating courses in PPT thru their tool. I understand adding morph to Storyline could be difficult, but I do not understand how adding morph to Articulate 360 (presenter) would be hard. I have purchased iSpring just so I have access to Morph. With the recent release of iSpring Page (basically iSpring’s version of Articulate Rise), now when I compare iSpring to Articulate… the differentiator for me is morph. We rely primarily on Articulate 360  or RISE to create our courses, so losing access to Storyline does not hurt me at this point. I prefer to stay with Articulate… but the morph feature is a ‘must have” in my world and iSpring offers me that. So for now, unfortunately, I am switching to iSpring and will not be renewing with Articulate. If you have morph by the time my renewal date comes back around, I am hopeful to return.

https://www.ispringsolutions.com/blog/ispring-supports-the-amazing-morph-transition
https://www.ispringsolutions.com/ispring-page

Brett, it impacts EVERY user who has a Morph transition in their PowerPoint deck. Remember, that transition is more than just a wipe, fade or barn-doors. It's really used as a way to quickly and efficiently animate / transition things (motion, scale, color, transparency, typography, etc). People heavily use this transition. You just might not be hearing much from the users because they already know to prepare their work differently. It takes time to make noise.

I logged in to say the same thing. If Articulate are only going by the number of users who actively contact them and ask for a feature, they're misreading their audience. For every one of us who has commented in this thread, there will be hundreds who don't bother reading here, but who would also greatly appreciate this feature, and make purchasing decisions accordingly.

I've also never seen a survey.

I don't want to go back to iSpring - I use layers and triggers a lot, and although you can duplicate that in iSpring, it is more labour intensive, as is any kind of navigation other than linear. It can be done though. And when I weigh up the amount of time I spend to recreate even text boxes in Storyline, because they've imported as pictures, well, the time may not be a lot different.

Hi David, 

Along with industry trends, competitor analysis, and other factors that contribute to our feature roadmap decisions - the number of users impacted is an aggregate of 360 users involved in an E-Learning Heroes post like this one, as well as all individual Feature Requests submitted to www.articulate.com/fr. 

Respectfully, I'd submit that you're not reaching a representative sample of your core users.  Typically, the most vocal and/or the most aggravated are the people who take time to log on, find a board, locate a request link, etc., and then take time to post.  That's a small percentage.   Requesting the morph transition is rather akin to requesting indoor plumbing.  If the 2 star hostel down the street (Powerpoint) has it, but the 4 star luxury chain (Articulate) doesn't, most people will just work around it until they find a way to pack up and move on.  They are spending time finding out what software that amazing design they love was created in, and after enough of the same answer, they jump ship.  Consider this board a canary in the coal mine rather than an pesky outlier, please.

Totally agree Julia. So, do we need to bombard Articulate with a feature request for morph before they will take us seriously? The number of users impacted, I believe, would be every user - the vast majority of instructional designers would appreciate this, even if they're not aware of it yet!

Hi Tina and Julia,

We treat all replies, comments, and + 1's in these E-Learning Heroes Discussions as "feature requests" too. That way we're capturing the voice of our users across multiple input points and truly looking to have many diverse voices represented. We take each submission, comment, and reply seriously to understand the value it would bring to all our customers. 

Given the continued conversations in this discussion, our team will be discussing this feature again. That's one of many steps in our process, but I hope it reaffirms that we're here and we're listening. 

If there is anything else we can do to help, please let us know. 

Yikes! I was hoping this request would be possible already. Please add me as a +1 for this request. It's a little frustrating that it is available in PowerPoint and NOT in Articulate. 

I would  also like to add my vote for Morph in transitions. I use it all the time in ppt and I think it would be yet another gamechanger in Storyline - I'll even open a bottle of champagne to add bubbles to help it rise to the top of the wish list if that helps!

I am using a workaround until this gets developed. I create the slides in PPt and export them as a movie file and use that in the background. Please prioritize this feature.

Yes, I do the same...but it's definitely not sustainable. This was something that Captivate was able to do in the early 2000's. I know that it may be a "More advanced" feature for the average Storyline user, but I feel that there are SO many benefits to having this feature and many would use it more often 

I've been using Storyline for just two weeks. and I can already see how Morphing would be a great help to me having done a lot of it in ppt. 

I think if anyone is a serious ppt user and has improved their presentations with morphs they couldn't fail to see how useful it would be here.