Currently (XD 24.0.22.19), if I drop an instance of a component and then adjust part of it (text in a button, size of the instance, etc.), that override is only applied to the selected state of the instance. So, if I have a button with many states (normal, hover, disabled, active, default action, etc.) I have to manually apply that override to each state of the instance. This is extremely tedious and error prone.

Please provide the ability to have an override of an instance be inherited by all states in that component instance.

It would be great to have a way to duplicate a master component - create a copy within assets panel. If I have a component that has several states and I need to make a dark mode version of that component, I would like to just duplicate that component and make my changes instead of having to recreate it from scratch as a master component.

I noticed that if I add a component with multiple states to the shared library, only the currently active state is stored. Please allow storing the components with all of its states in the library.

The current feature of switching on/off snapping by holding "Cmd" in Mac or "Ctrl" in Windows doesn't work properly. Additionally, we couldn't align shapes or objects with one another as there isn't feature to turn on/off the snap to pixel grid for the entire document.

I have animated icons with auto animate and wish to use them in two sizes: Small size in the menu and big size in the features page.
When I scale up or down the component it only scale that one specific state. We need it a way to scale all states so we can have a few less components. and a fast workflow.

Sometimes you need to reorganize your design system files. Once you have created a master components, you cannot move it to another file, and you are stuck with the current file forever.
It would be great if you can just move your Master Component from one document to another.

The new stacking function is very good and complements the padding function.

However, on some occasions the direction of the stacks is not necessarily (from top to bottom) or (from left to right).

I believe that adding two more stack options: (from bottom to top) and (from right to left) can improve the creation of interfaces more easily.

It would be helpful to apply multiple paragraph styles within the same text box. This is particularly helpful for long bodies of text such as visualising a blog page. Currently you have to split each header, sub head and body copy block into separate text boxes.

Our preferred workflow is to have a Xd-beta file for new development. When changes here are implemented the design gets moved to another file.

However, when copying artbords that contains components with overrides, these overrides are lost when the artbord is pasted in a new file. (both Xd-files are connected to the same master component file)

Would love if this could be fixed.

I'd love to be able to rearrange the component state order in the property inspector (the panel on the right in Design mode & Prototype mode). I would also love to be able to resize the section for component states. Currently it maxes out at 4 before you need to scroll.

For example, when you have a button with several states containing a label and you want to change the default text label, you have to update every state of the component one after one.

It will be nice to be able to define a text as persistant inside the component states.
Perhaps a simple checkbox in the Properties?!
Or a way to link/bind only some states and not some others for more flexibility!

Create component - + New state (bigger than the default) - Merge the component with another one or another element into a stack -

Preview mode - click the component to change state and the stack doesn't respect padding .

It would be great for the user to be able to choose how they want to view their layers—like sketch or like current XD. Let the user decided which works best for them. I like seeing everything, not just the artboard I am on.

Horizontal and Vertical options are nice, but in development there are many cases where you need to use both, especially for any items that wrap. I've included an idea to offer both options that will make stacks even better.

this is bad UX!

Command-Shift-S

the standard keyboard shortcuts, which you also know from other adobe products, should save the file locally and not to the cloud.

Command-Option-Shift-S

the extended keyboard shortcut can save the file in the cloud.