← Adobe XD: Feature Requests

Request details

Adobe XD: Feature Requests: 01 : Design mode

Categories

(thinking…)

Create new main component from existing component

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

672 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Kei ™ shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Andrew Hart commented  ·   ·  Flag as inappropriate

    I presume you will implement this with a right click option in the component panel. However if you choose to also implement this as a right click option of a component on the artboard, which adds the duplicate component to the artboard (A feature that I would like), I would request that the duplicated component be tagged as a main component, not just an instance.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Yes please! I'm struggling while creating a Design System, wanting to have nested (master) components inside other master components. It would be super helpful to define a child / copy as the new master / main component. I don't want to spend a ton of time recreating things just to have it all as a master.

    Adobe we really need this feature to excel in the pro field of UX / UI design and prototyping. Please implement it ASAP.

  • Anonymous commented  ·   ·  Flag as inappropriate

    we need to have "make a main component" to take over the component and become the main
    we need to have "convert to main component " to take the component with it's properties and make it a new main component

  • Erik commented  ·   ·  Flag as inappropriate

    I would really like to be able to create a new master component from either another master component or from a modified copy of a component. It is especially useful if you just want to try out small changes, but keep the master component as is, or if you have modified a copy of a master component to a point where you realise this is how the master component should work.

    Also, if you have set up a number of states on your master component, that you would like to keep for a new modified master, there is no way to retain them. Unlinking a copy destroys the states.

    So yes, a "duplicate component" and "create new master component from this copy" would be extremely useful.

  • Zigmas Mallol commented  ·   ·  Flag as inappropriate

    Pretty basic, very needed indeed. It's also pretty useful when creating multiple similar components, but that on design system they are not the same, development wise.

  • -M@ commented  ·   ·  Flag as inappropriate

    WHY is this still not a standard feature?? One more reason why XD is years behind other tools. ;/

  • Luigi commented  ·   ·  Flag as inappropriate

    Essential feature! We need a "Create a master component from" or a "copy aspect".

  • Victoria Borrowdale commented  ·   ·  Flag as inappropriate

    Ability to copy an existing component (to preserve its style, states etc) and make changes to it then promote it to being a new master component so that other components can be created from this new version.

    E.g designing a button style for mobile with default and selected state. Copy this for desktop but need to add in other states and copy this button style for all instances on desktop.

  • Lucas Sterrett commented  ·   ·  Flag as inappropriate

    This would be an amazing feature. I have spent hours trying to change and duplicate components that could have been done with a few clicks.

  • John Hare commented  ·   ·  Flag as inappropriate

    Yes please implement this critical piece, to keep improving a brilliant application.

    The specific problem I am addressing is building a family of tabbed dialogs where the tabs need to renamed for the specific use case. Whereas master components allows editing of items shared by all states once we are forced to create an instance each edit needs to be repeated for every state - a time-consuming and error prone process. My own preference would be for two levels of inheritance:
    1 - edits made to the default state ripple though all other states unless explicitly overwritten
    2 - genuine duplication of a master component to create a fully separated branch of the tree

    Regards

  • Mo commented  ·   ·  Flag as inappropriate

    I want this option, it will help a lot when building my UI Kit

1 2 4 6 7