Skip to content
← 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.

713 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  ·   ·  Report…  ·  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
  • Victoria Borrowdale commented  ·   ·  Report

    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.

  • Scott commented  ·   ·  Report

    I can think of SO MANY uses for this feature!

  • Lucas Sterrett commented  ·   ·  Report

    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  ·   ·  Report

    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

  • Bartolomeo D'Alia commented  ·   ·  Report

    Please Adobe, do this!!
    It is very difficult to manage UI Kits without this feature....

  • Mo commented  ·   ·  Report

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

  • Cedric commented  ·   ·  Report

    +1. Would be so useful!
    Thank you, Adobe.

  • Brady Allen Young commented  ·   ·  Report

    @Adobe may we please get this feature??? 🙏 So frustrating when working with on one project with multiple files and iterations, redoing all the work of creating states when I just need to make an independent master

  • Cognisant commented  ·   ·  Report

    This is a crucial feature for collaboration between multiple people on a project. I'm struggling right now. If one is not able to move a master component to another file, how are multiple people supposed to collaborate on a project? Atleast being able to change an exisiting component status to master component will hep this a bit.

    Get on this feature @Adobe!

  • Anonymous commented  ·   ·  Report

    I literally can't believe this hasn't been implemented yet. I found a half decent work around, but its not the best.

    1. You copy the component to another document
    2. Right-Click the asset and select "reveal component in "assets"
    3. Right-click the component in the assets panel and select "make local component"
    4. then click the Pencil/Edit State button in the component panel on the top left, this will generate the "master" component of the copied component.
    5. copy this new master back over to your original document.

    This works perfectly only one layer of component. If you have components inside of components, they will probably get a bit messed up. But it still might save you some time.

  • Bertrand commented  ·   ·  Report

    I heard little details are the product. It seems you did not have to create a design system without this feature. I am about to break my computer everytime I need to create a new component based on a previous one.. Please hear our voices.

  • Zahier Zulkafli commented  ·   ·  Report

    And here we are again waiting for genie to grant our 4th wish. Was it the 3rd or 4th, I can't remember.

  • San Rabid commented  ·   ·  Report

    Please, we need this feature implemented!

  • Thomas Hale commented  ·   ·  Report

    This would save so much time in having to replicate states that are similar between components. For example, my design system has table cell components that have different height variants (as well as all the other "states" you might expect of such a component), thus if I want to create a component where all the states are virtually the same name and only difference is the height, I have to do a lot of work to replicate that structure of states, naming.

  • Fanny.B commented  ·   ·  Report

    This feature is so useful, a +1! I'm agreed, it's not efficient to rebuilding from scratch a component and so annoying..

  • Joo Chung commented  ·   ·  Report

    Adobe appears to care very little about things that actually improve the user experience of this software. So many basic, basic features are lacking, such as this one. Other functions overtly obliterate user work, which leads to having to do workarounds for functionality that really should be as basic as being able to copy and paste. Get your shit together Adobe.

  • C. Lockeby commented  ·   ·  Report

    Here's another +1 for this idea. Ungrouping and rebuilding all states isn't an efficient workflow!

1 2 3 5 7