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

Shape/component fill container (stack).
Example:

Let's say I have a horizontal stack with two squares and 20px margin between them. It would be really helpful if I could set one or both squares to fill the stack (container). This way If I want to resize the stack as a whole the two squares would automatically resize.

This does wonders for responsive layouts.
Figma has this feature already and it works great.

Love what you are doing with XD, I've been using it since day 1 and this is he only thing that's missing for me.

Keep up the great work and I hope someone reads my message :)

I work on a path planning project.
User must preview the path.

I NEED to produce several iterations of the same path animation, with different colors or informations.
XD will allow me to implement the path representations in the app, without reproducing the user journey in After Effects : It becomes "real"
Then I can test each version of the path, very easily, and get precious feedbacks

After Effect is the tool => export a transparent video
because AFAIK it doesn't export transparent gif

Back into XD, my app structure (background, menus, etc) remains unchanged, and we can test every specific path planning representation…

#WeNeedTransparentVideoSupport :D

Without any duration or Mb/Mo limitation… 15 Mo, seriously ? ;)

Thanks

A busy design session may result in "orphan" Character Styles which are not named or do not conform with the standards. For example, I want all body copy to be 14pt but a few instances were wrongly created at 13pt. Currently, I click one instance of the 13pt, then "Add Character Style to Assets". I can then use the "Highlight on Canvas" feature to SHOW ever instance. But I cannot apply the 14pt style to them because they are not SELECTED. If "Select on Canvas" were an option, I could apply the correct 14pt style to all of the 13pt instances with a single click.

The many comments on Xd websites make it clear that users strongly dislike the tedious method of 1. Highlighting instances, 2. Visually scouring every dartboard for the highlights, 3. Hand selecting each instance, 4. Styling those characters, 5. Repeating the whole process again for the next section of the Xd canvas.

I'm not a programmer. But common sense suggests that if Xd can locate all of those instances to highlight them, then surely those instances can be selected.

Please. Do this. Right away.

My request is two fold but both relate to shadows.

In brief

Include shadow properties that related fully to CSS
Include the ability to save named shadow profiles for reuse

Details

Include a crucial forth property to drop shadows that is actually part of the CSS spec and will enable designers to more accurately communicate their specifications to developer – include SHADOW SPREAD.

Example declaration in CSS;

box-shadow: [x-offset] [y-offset] [blur] [spread]

Additionally, please include the ability to save drop shadow profiles so they can be updated easily and will be applied to all relevant designs. It is time consuming to update all drop shadows on larger designs.

For example, create a drop shadow and give it a name like "shadow low". Updating the named shadow profile will apply those changes, in the same way updating a character style or colour profile would.