New and returning users may sign in

We're glad you're here

Please sign in to leave feedback

Signed in as (Sign out)
Close
Close
← Adobe XD: Feature Requests

Request details

Feedback

Adobe XD: Feature Requests: 01 : Design mode

Categories

  • CATEGORIES
  • All ideas
  • My feedback
  • 01 : Design mode 1365 ideas
  • 02 : Prototype mode 369 ideas
  • 03: Share mode 50 ideas
  • 04 : Sharing on the web 214 ideas
  • 05 : Asset exporting 157 ideas
  • 06 : Extensibility 38 ideas
  • 07 : Integration with other tools 118 ideas
  • 08 : Mobile (iOS) 25 ideas
  • 09 : Mobile (Android) 19 ideas
  • 10: Developer Handoff 139 ideas
  • 11: Plugins 135 ideas
  • Other 109 ideas

(thinking…)
  • Searching…

    No results.

    Clear search results
    • Adobe XD: Feature Requests 2,865 ideas

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.

  •  
    Screen Shot 2019-11-07 at 8.04.39 PM.png 329 KB
671 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  ·  November 16, 2019  ·  Flag idea as inappropriate…  ·  Delete…  ·  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
Tweet
  • Remove
Attach a File

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
  • Brady Allen Young commented  ·  August 10, 2020 12:52  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    @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

    Submitting...
  • Cognisant commented  ·  August 10, 2020 00:54  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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!

    Submitting...
  • Anonymous commented  ·  August 06, 2020 08:04  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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.

    Submitting...
  • Bertrand commented  ·  August 06, 2020 02:18  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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.

    Submitting...
  • Zahier Zulkafli commented  ·  August 04, 2020 22:28  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

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

    Submitting...
  • Paul commented  ·  July 31, 2020 04:16  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    +1

    Submitting...
  • Anonymous commented  ·  July 30, 2020 13:18  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    How is this not a thing?

    Submitting...
  • San Rabid commented  ·  July 24, 2020 10:07  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Please, we need this feature implemented!

    Submitting...
  • Thomas Hale commented  ·  July 23, 2020 14:58  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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.

    Submitting...
  • Fanny.B commented  ·  July 23, 2020 13:59  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

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

    Submitting...
  • Joo Chung commented  ·  July 22, 2020 13:17  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    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.

    Submitting...
  • C. Lockeby commented  ·  July 22, 2020 11:53  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

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

    Submitting...
  • Evangelion Netai commented  ·  July 22, 2020 08:54  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    yes pleaseeee need

    Submitting...
  • Anonymous commented  ·  July 10, 2020 03:44  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    It would be a huge improvement to create new master components from the overrides of a component.

    currently, i have to ungroup the component and create a new one, if i want to create a new master component from override styles.
    but therefore, i have to recreate states etc., which could be easily adjusted otherwise.

    Submitting...
  • James Duffield commented  ·  July 10, 2020 03:00  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Having to recreate all states on a new component is a real pain. This is 100% needed.

    Submitting...
  • Mirek Ždímal commented  ·  July 02, 2020 13:11  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Yes please.

    Submitting...
  • Anonymous commented  ·  June 23, 2020 14:20  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    + 1 for a master component duplication method

    Submitting...
  • Josh On commented  ·  June 18, 2020 12:45  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Just ran into this again.
    It is really important - the use case I have is that I have an alternative navigation on some screens and now I have to rebuild the whole nav component...

    Submitting...
  • Amanda Staunton commented  ·  June 18, 2020 00:49  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Please work on this Adobe, this would be a major time saver. It's frustrating to have to remake a component that has multiple states.

    Submitting...
  • Tony Ward Arts commented  ·  June 12, 2020 09:36  ·  Flag as inappropriate  ·  Edit…  ·  Delete…

    Absolutely my #1 need right now! Please make it happen... Working on my own website design and this is crucial.

    Submitting...
← Previous 1 2 3 4 5 6 7 Next →

Adobe XD Feedback : Feature Requests & Bugs · UserVoice Terms of Service & Privacy Policy · Adobe Terms of Use · Adobe Privacy Policy