I could really use this feature in prototype now. I have a sidebar with a ton of filters where I have expanded/collapsed states. Right now the expanded state in prototype just goes over the other elements.

The Problem: I have two components A & B. In A's default state component B is y px beneath A. Component A size expands or contracts by z px and changes to a new state. Currently, component B is now y + z px from the bottom of component A.

The Solution: Components that can change shape between states should "push or pull" other components by fixed padding defined assumed by the system or defined by the designer. This behavior should be able to be chained between multiple components & other objects.

Applications: Expandable lists, expandable cards, & my quality of life improves.

Savings: No need to create an endless number of artboards to express simple behavior between components or super long write-ups to hand off to a developer.

Current Time Cost: Per component, n, that has a number of states, y, on the artboard a designer has to create (n*y)! number of artboards to describe the screen behavior. This is a massive pain in the butt! It costs countless hours of write-ups and reconciliation with developers.

This wold be a really cool thing to implement. You already to auto-animate so creating a stack that animate should be relatively simple. Let's say you have a stack of expanding components. Then as each component expands, the stack responds and expands as well.

Two adjacent buttons [components in this case] each with similar states (one hover and one dialog popup) are not behaving as per the expectation. When the pop up dialog state is active, the other button is overlapping onto the dialog. Check the video. This is a limitation. Creating a separate artboard and linking to it should not be the solution when you have components in place. I am unable to use two components with states adjacent to each other or one below the other.

Also, it would be nice to see a component with expanding state pushing the component below and likewise pulling it back to its original position when in collapsing or default state. This could help in a lot of situations. Example - accordions.

With the new update the stack and scrolling verticaly/horizoontaly.

Create Component -> Repeat Grid -> Ungroup -> Group - > Create Stack ->inside the stack main component -> Create new state (After) -> On after state(Make the space vericaly larger) ->Default to normal state back -> press preview.

Result : Inise Xd Programe, is shows that the component is pushing the stack. When preview mode, doesnt push the stack accordingly.

Elaine,
While you can achieve a lot using auto animate, it is still a scripted flow. The idea behind creating common components is to be able to build a non scripted flow.

When a component or an object expands, you may want to push other content with it. This could be solved by pinning individual objects and components to each other.

The attached screens shows 3 accordions made using XD's new component feature. Once I open Item 2, I'd like item 3 to be pushed down. This is not possible today, instead item 2 overlaps all other contents below it.

Yes! This could be an easy feature but it takes upwards of 20-30 minutes to duplicate artboards and link them all with specific transitions. They could easily make a collapsible accordion menu.

Also mabe a horizontal Accordion for menues.

I would like to be able to create an accordion that forces all elements below it down. I'm guessing the best way to do this is use overlays and and have the ability to fix the overlay to the accordion button and switch states of said button (closed/open)