My goal is to have a trustable source of truth of my design system outside codes. I already tried hard, but can't do that in a scalable manner, there is always a huge gap, overly because a few features are missing. Flex behaviour, Grid behaviour, consize padding and margin. Maybe they are hard to create or have performance constraints.

To be scalable and to enable my design system to evolve, I build things using principles of the Atomic Design Methodology. Without the above features, having a single tweak on font size on a deeply nested component like a input label will break design on whole pages.

A designer usually can't reason about code, but both designers and devs can reason about a tool like adobe-xd. That's why my source of truth must be outside codes.

A tool like this would reduce the need for using Storybook (except for testing purposes).

Situation:
I create a component to represent a live video chat head in a group chat app. I will use a static image for the prototype. The chat head will have several states, including hover, selected, muted, etc. I need to create 30 of these. After I built the component with all the states, I created a repeating grid of them so that I can drag my 30 photos into the components.

Problem 1:
The drag fails to propagate the photos to the other 29 instances in the grid... it only puts one photo into the drag targeted instance

Why this is important:
Because the expectation has been set that this is how repeat grids are supposed to work... there are several daily challenge videos showing how great this is. The fact that I'm putting it into a component vs a basic shape shouldn't matter.

Problem 2:
For the lucky instance that did receive the photo, it only got put it into the circle shape of the current state. The circle shape was named the same across all the states. It should have propagated to all the states in which it existed. Alternatively, I should have the ability to flag certain objects to simply be fixed across all states... maybe they have to be placed in the default state to be eligible for this ability to be flagged as constant across states.

Why this is important:
Because since the above repeat grid drag didn't work, I'm faced with having to drag a photo into each of 6 states for each of 30 components... that's 180 RSI inducing drag gestures. With this problem addressed, it's only 30.

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

◆ 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.

First of all thanks for the latests updates in November – they are great ?

My team often struggles to find the needed character style in the assets panel. In the 'List View' you can give the fonts certain names; eg: H2 Titles 50/60 px.
image: List View

When we switch to the 'Grid View' (which portrays the components larger and thus more useful in that case), then the given name unfortunately disappears and only the font names are visible, which we can do very little with.
image: Grid View

It would be great to get this issue improved in the near future!

Below we have provided a possible solution:
character-styles_Grid-View.png

Thanks a lot!

Best regards,
Serkan Zararsız

Component states are awesome, but right now the size increase for a complex component is not scalable. After doing some testing, components appear to increase their size proportionally to the number of states.

For example if I have a Default state, create a new state and move the components, say in a mask, to do an animation the size has now doubled. Then if I copy that to a new artboard, it doubles again, because both states get carried around. Therefore what originally would have been a master with an instance in 2 separate artboards with size 2X is now size 4X because there are two instances with 2 states. Add another unused state and it is now 6X

I understand why this method would be used, but it has not been scalable for some of our work.

Any plans to address this?

When you have a layer within a group selected, then collapse the group and hide it, the group expands again.

I understand the thought behind this would be to always show the selected layer in an expanded hierarchy, but during my workflow it seems very counter-intuitive and different from the way I have been accustomed to expect adobe products to behave.

I would like to see this changed so when I have a layer selected within a group and I collapse the group and then hide it, the group stays collapsed with the group becoming the main selection instead of the sub layer, that way if you happen to forget where your selection was you at least have the group already selected and can dig through those layers.