It would be great to have the Alias, Size, and Custom Tokens available in XD for when I'm designing. Currently my color tokens only show the global versions, and I can't add additional swatches if they share a hex value. We don't want developers using global tokens if an alias or component token exists, so it would be great to have these available to me as I design.

Colors. Why can't I add them straight up? I know all the colours i need to use? Why can't i just create them? Why do i need put something on an art board first? I am doing something wrong?

The asset management is strange. Figma does it better. Copy them.

Components can be very different from one another and the initial state can mean different contexts to the user.

Let us be able to rename the component's default state, so it can make more sense during the component building process.

With a component selected, a keyboard shortcut to cycle through its possible states would save a lot of mousing between artboards and the LHS panel. This is particularly true for screens with multiple components. If they could all be selected and reset to default and cycled through their states, this would be a helpful addition

The padding tool is great, but for some cases, it would be great to have a possibility to leave it undefined. Example: I have a component that has a background and a text in it. I want to use it in a way that the background will take all the available space on the right of the text, regardless of the length of the text inside. Now I will not be able to do it otherwise than manually adjust the padding for each instance of this component.

It would be beneficial for us to sort the Components list by name (Alphabetically). Reason being, when we attach the Cloud doc to a new project file, components seem to be in a random order. If we could re-sort the list alphabetically on each file, it would make organization of large counts of components much easier.

Instead of creating components, Icons could have a separate category in assets. This could help organize the project and could be used to generate a separate zip file for download for the developers.

Paste appearance now works for individual items. It would be time saving if I could copy the appearance of a group of objects and paste it into another one with the same objects and different appearance.

Would love the feature within "Padding" to add "auto" as a value. This would work well when designing tables that need to keep the same width, but may have different text widths.

The Padding auto side will automatically adjust to keep the item at its current width.

Since our team is using multiple shared design libraries, it would be nice to be able to open more than one library when working on a document.

For instance, I'd like to be able to have both the brand library and the current document assets open at the same time.

Especially if one could be on a floating palette.

It seems clickable area is set to the exact size of closing icon? Could you make it a bit bigger?

I occasionally come up against a situation where I have created two components that I realize should have been a single component.

When this happens I must repeatedly highlight the redundant component on the canvas and manually replace the component.

It would be great to have a way of simply replacing all occurrences of the redundant component.

In an ideal world, this function would be a smart replace where object attributes from the replaced component instances were applied to an object in the new component instance where its name and type matched.

Having copied a component from a different document and made it local, I think it would be more logical if the component was also tagged as the main component instead of just an instance.

This was the behaviour that I naturally assumed was taking place when I first did this because whenever I create a component in other circumstances the selected object is the main component.

When you implement the duplicate component functionality I would also argue for the duplicate component to be tagged as a main component.

Have the possibility to "Reset to Main State" all the instances of one component present in the document in one click.

I'm working on a file with 60+ artboards, with lots of components and subcomponents. Sometimes the instances of my components don't update automatically when I edit the main state, so I have to do it manually for each one of them.

Give an option to enable & disable or remove decimal points in x,y & degrees & components.

Why don't we remove points as all users use only whole numbers (30px/30deg/30 x, 30y) and not (30.736px/30.37deg/30.48 x, 30.74y)

As far as I have worked with teams & users in the industry we only use whole numbers as decimals create issues with development and QA.

When padding is on and you move some elements, the width/height of the grou changes. It's a problem when you want to for example have specific width of the element (i.e. background shoud be 1920px wide or button should be 48px in height, when you turn on padding and change font size your button is not 48px anymore).

In UI design, 3d elements become real trend and have the possibility that create obects with bevel propieties would be awesome. thanks.

sorry for my bad english...