Animate individual elements separately (custom animation transitions / microinteractions)
Support for simple animation.
Example: Show/hide a slide or push menu
This would enhance a demo and engage prospects that are familar with common application patterns.

Reopening the feature request, based on feedback.
-
Nikos Pappas commented
We need this! But most of all, we need the other feature that is under review: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/13183851-text-input-field-with-actions-based-on-value
Please give us any of these two!
-
Erik commented
Go to the frame!
-
Benny Stühler commented
Time driven switch between component's states would probably solve this. Currently the states can be switched by external actions only.
^this, please allow time driven states for components!
-
Daria commented
Time driven switch between component's states would probably solve this. Currently the states can be switched by external actions only.
-
Leo M commented
I found out that creating a very simple live-looking loading event (spinner-wheel) is hard requiring multiple artboards to animate.
I wish to be able to build a self-time-animating component sitting on a single screen-artboard, while the artboard itself can be set to time-transition to another resulting artboard. (see attached)
-
Jeffrey Johnson commented
Screw simplicity. Add an animation timeline for individual components. In the very least, give us a time trigger for states!
-
Anonymous commented
Hey XD, It would be helpful at least if you allow the time trigger between the states of a component. We could use it then as an animation and the states would be the key-frames.
-
Anonymous commented
For real? The second most voted feature still gets a "Feature-Under-Review" for all most 3 years now... other companies managed to do this a long long time ago. i don't wanna say it is easy work what you guys are doing, surely not but please give a bit more feedback back to us then! otherwise this gets more and more ridiculous every day...
-
Benjamin Chasseur commented
Yes ! Have the best animation features of InVision Studio, Principle and Framer ;-D
-
Oana commented
This will work super well!
-
Anonymous commented
Idea added 5 years ago. Second largest request and reopened for 2.5 years ago as under review. It's probably a challenging task, but if it's not in the backlog by now it wont be implemented for a looong time. Love XD but this forces me to go to a competitor.
-
Steven Mancera commented
Hey Demian, consider a Timeline view based Interaction Design UI with this. Where we can have easy Properties changes on each Keyframes.
Just like on After Effects and InVision Studio (look for it for inspirations)
-
Noi commented
Without getting too mired in the details of a professional timeline, there's GOTTA be a way to simply select which element comes on first.
Like, whichever text box/gfx is on top gets the hero treatment. (Instead of which is bigger, which is what it seems to be now...? Which is REALLY annoying)
-
Adding the TIME trigger to animate between states within a component. This would reduce the need for multiple artboards to animate elements like loaders, progress bars, and all that good stuff.
-
Andrew Hart commented
This would be nice. I would suggest that this is implemented by adding a Time action to trigger s state change. State change already has auto animate so allowing a state change for an element triggered by a Time event achieves the required feature in a more general way
-
Farshad Sadri commented
That's a definite YES feature. I hope XD dev team implement it in near future. This feature alone can add so much functionality to prototypes that stakeholders can mistaken it with the finished product indeed!
-
Anonymous commented
For a start custom easing curves would help A LOT!
-
Boiba commented
Just copy Principle and be done with it.
-
Hourless commented
System may be so simple...give us ability to set delays for individual elements so auto-animate may consider them...that would be great.
-
gue commented
Is this ever going to be implemented as the feature is under review for 2 years (!) now?