Forum Discussion
Entrance animation/exit animation - can we do emphasis?
I would like an object in Storyline to pulse repeatedly from the beginning to the end of the timeline. In PowerPoint I would use an Emphasis animation - is there a workaround in Storyline?
Hi everyone!
I have some great news to share! We just released another update for Storyline 360. In Update 84, we've included important fixes and new features.
One of the new features we've included is:
- Choose from a library of emphasis animations that grab learners' attention with effects like pulsing, shaking, and teetering.
Launch the Articulate 360 desktop app on your computer to take advantage of this update, and click the Update button next to Storyline 360. You'll find our step-by-step instructions here.
Please let me know if you need additional help!
71 Replies
Hey, Susan. You had us at dessert.. 🍫
I'm going to add your vote, and I promise to let this discussion know if we make this change in the future!
voting for this as well!!
I would love to see this as well!!
Thanks for casting your vote, folks! We've got our eyes on this request. 😁
Hello, I notice a number of people requesting emphasis for entrance and exit animations going back a few years, including myself. But I haven't heard if it is actually coming. Can you confirm whether or not this affect is in the works?
Thanks very much!
Deb
Hey Deb,
This feature isn't on our immediate roadmap, but I'm happy to share your experience with the team so they're aware this would be helpful for you.
By the way, replying via email includes your signature with contact information in the public forum. Feel free to edit your reply here!
Thanks Alyssa!, reply edited. :O
Could you share with us the rationale for this feature not being implemented yet? I understand that it may not be as easy we (me) may think. But as it 'seems' basic and a number of us are asking for it (its standard in other software), it might make it easier to be patient and accepting to have some clarity on the issues or delays.
Many thanks,
Deb
Hi Deb,
Our team prioritizes feature requests based on the number of users impacted/requesting it, the ease of implementing the feature, the availability of viable workarounds, and the value add to the product. This is one that folks have talked about over a length of time, but hasn't bubbled up to the top based on those other factors.
I have found a little workaround that might be helpful for some. See screenshot attached -
On this slide I want the yellow arrow to flash or blink 3 times and then disappear, so I create 3 instances of the arrow and adjust their timing to a fraction of a second, and make sure they are spaced out an equal distance. They are not perfectly aligned in the screenshot to show there are 3, but you would want to align them on top of each other, and then group if you want. Applying the fade in and fade out animations with a .1 or .2 duration will help soften the blinking effect.
Would be really great to have this built in though...
Tristia, thanks very much for sharing your workaround! I love how this community collaborates and shares. :)
Cheers,
Deb
Some of us have been asking for this (and submitting feature requests) since the first beta for SL1. :(
Hey, Deb! Even though I and others have been asking for this since Day 1, I try not to get disappointed by that (and I probably should not have posted what I did since it may have implied negativity). The length of time of a request should not be a weighing factor. There probably has not been enough total demand for it, they may deem other things more important, or maybe there are technical issues.
I really have to remember it's not my software to develop. It's theirs and they probably have a road map and goals for what they want to do. User feedback via feature requests helps with that. They pick their path and work it, probably adjusting it over time. Our choice is to trust that process and wait or to move on to another tool, or come up with some workaround.
I bet they've been inundated with thousands of feature requests through the years. Heck, if Articulate implemented everything that I wanted to see in SL, I'd keep them busy for a year or three at least. But they can't do everything. Like any software company, they only have so many resources for improving and fixing things--and also keeping up with technology changes. I don't envy what they do. :) It looks damn hard. But I do think they do a pretty good job with it,
They have their processes and we have to trust they work. I have no reason (or experience) to doubt that. If you really want something, you need to enter a feature request and maybe professionally urge others to do so. The more requests, the better. Heck, I'm notorious for repeating a feature request or two from time-to-time. ;)
And there have been times when I was sure something I requested was popular with many other folks and I found out later that it wasn't. (It's humbling to find out you're the only one requesting something. ;) )
Actually, one thing that I've always wanted since Day 1--more editable shapes--was sort of fulfilled this week with the SVG import from PowerPoint. Having direct import of SVG or the shapes in SL360 would have been better, but I'm one happy camper with what we got. :)
I think one thing that generates frustration is that some requests feel like "low-hanging fruit." That perception may be wrong, but if it is, Articulate never explains why it is wrong. So some seemingly "easy" requests languish for years and it leaves the impression that Articulate just isn't paying attention or doesn't care.
This request is a good example. There are already entrance animations, exit animations, and motion path animations implemented in Storyline, so to an outside observer it seems like adding emphasis animations would just be more of the same and not too hard to implement. Yet there's been no forward motion on this request in over 6 years.
It's definitely not at the top of my priority list (basic, foundational stuff like being able to combine ANDs and ORs in a trigger are way higher up in my wish-list), but I wouldn't complain if some of the smaller, easier stuff got released first because it makes sense to clear out some quick-fixes that people want from time to time. Maybe an adjustment in how Articulate prioritizes requests would help, giving a little more weight to something when it is easy to implement?
It's hard to give sound advice from my outside position of ignorance, but the optics of 6+ years waiting for a seemingly simple feature is not great and perhaps could be a trigger for some rethinking about how these things are prioritized internally at Articulate.
Love the tool, love these forums, but I think there is room for improvement in this area.
Respectfully,
-Ray
