◆ Overview
After releasing "State" feature, it's been able to prepare complex interactions like "hover." Following feature may help to reduce required time preparing a new component with similar behaviors/instructions.

◆ Actual
New component with state settings every time when a similar behavior is expected in different look and feel.
(Currently, preparing another XD file is believed to be the only solution to avoid this by selecting "Make it as local component" after loading it from another XD file.")

◆ Expected
By select "Use it as a new Master Component" is to make a new Master component instead of copying it as an instance component.

◆ Why is this valuable to you?
When using a single, new XD file and load a master component from other XD files, it is possible to make it "local component"; however, it is unable to make it happen within the same XD file.

This helps to reduce time to prepare a set of basic state setting from the beginning each time. This also helps NOT to get affected unconsciously on the new component by editing the template master component by someone else.

Since Co-Editing feature is now beta version, some larger project may have a couple of co-editors of components on the same XD file in the future. While a group of designers keeps upgrading a basic behaviors for future use, another group of designers is working on on-going project to finalize a specific look and feel based on the template component.

I want the option when setting up character styles that there doesn't need to be a color associated with the character style.

For example, I set up my H1, H2, H3 with their respective font families, font weight, & font size. But my design has different background colors. Sometimes my H1 is lack on a white background, which is how I set it up in the Character Styles. While other times my H1 is white on a black background,. But if I change the H1 to white it no longer correlates to the H1 I setup in my character styles unless I create another H1 variant that has the color white.

I would like if my character styles were color agnostic so I can make sweeping changes when editing my text without having to create multiple color variants of my character styles

Currently when working with multiple documents, if you have overwrites on a component. And you modify that component, and then paste the component or artboard into a file that has an outdated version of that component.

It will paste the components but reset the overwrites and set the component back to it's default state. It doesn't inform the user about why it just resetted all their content. Which can be extremely annoying to the user, as this seems very weird. (Which is why there are also several support tickets of people running into this issue).

After talking with support, I now understand why it happens. However I strongly believe that informing the user about this issue would greatly improve the user experience. We didn't understand why it happened, and as such spend 6 hours readding content to the document.

I have made a simple quick mockup what this model could look like to indicate what I mean. This is obviously just a quick draft, and the style and copy should be better. However I feel like any information to the user would be better then just resetting all overwrites and not telling the user why they where reset. (As it's quite easy to miss if a libary or document assets are outdated)

While Adobe XD Team has certainly done an amazing work toward design systems creation in the tool, it still lack a bit of power.

Actually, it's quite tedious to create, maintain and use a design system in XD. Especially when working with multiple variants of a component.

Let's say I need too work on an app design and I want create my buttons in my design system : primary, secondary, alert, w/icon, large, small...

With the current XD, I only have 2 solutions and both have are really time consuming to maintain :

1. I need to create a separate component for each variant. So, let's say I have 12 variants, even if the required change affect a shared property, I still need to do 12 changes, one by one. And I don't even count the states and interactions related to each variant, which increased the time loss exponentially... By the way, the style panel being tiny, it rapidly become cluttered.




2. I can also created a component and put also variants in state but then, interactions are not inherited from on state to another. Besides states space/scroll area is not very tall, so with so much states to remember (cause we can't reoder them) out of sight it isn't as efficient as it could be. Plus it feels a bit weird to use states for variant as they are more than states.

A good solution for that would be to have a main component which could host variants inheriting its properties, states and interactions. Then the main component itself would be the default variant.

Ideally, variants would be organised in at least 2 levels of inheritance :
Main component > Variant LV1 >Variant LV2

For instance :
Button > Secondary > Large