Create new master component from existing component
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.
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.")
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.
Just to clarify what I expect this to do.
- Select an existing master component (eg a button with several states)
- Create a copy of that component as a new component (eg button with leading icon)
- All states are retained in the copied component and I can edit the new version
This would make creating variations of a primary component a breeze. Alas …
Today I have to
- Create an instance of the component
- Ungroup it (which really means unlink and ungroup, btw)
- Regroup the elements
- Turn that into a new component
- Make my small tweak
- Recreate all the states
I could also copy it to another doc, make it local there, rename and modify it, and copy it back in.
In either case, the workaround is absurd.
As has always been typical of Adobe products, Components persist as an abandoned feature while Adobe sends it's product dev team on tangents to create features to support marketing headlines.
Rolv Skjærpe commented
Please, can we have this?
I need to add a new state to one instance of a component, but I don't want to add this new state to the master component, but Adobe XD requires me to edit the master component for this update. So now, I have to rebuild a complex component for a single use - which seems unnecessary.
Please can we add this? I've spent days worth of time recreating stuff when this "feature" could have made it possible within seconds. Making component variations is an EXTREMELY common use case.
Mark Ocampo commented
Not being able to duplicate components without it being an instance is severely affecting the user experience and workflow negatively
This should've been part of the initial release seeing how much time you already save when using components. Having to recreate a component (not to mention its states) is a waste of time when you could easily "set instance as new master component" or "create master component from this instance" when working with components...
This needs to be added ASAP!
What is going on here? I am SOOOOO tired of making new component -> stack, padding, fill color, states upon states all over again again and again.
1 component done -> Dublicate and change what needs to be changed. voila!
Once this feature hits I will have to redo + 100 components from scratch, again :/
disappointed again. Really need to recreate the same appearence component from zero because I cannot transform into main component again.
I thought I was working on 5 Main components. And after making all my edits, realized they were all "Instance" not "Main" because I'd saved the document under a new name. So now none of my component changes rippled through the document! If I ungroup the components, I will lose my hover states.
So YES. We need the capability to change an Instance of a component to either override the main, or be a new component, with all states inherited.
Matthew Prina commented
I've voted for the "Duplicate Master Component" feature but I like this too because it would be cool to create a master (main) component from an instance of a component.
Think about it. You design a component that you're using a lot and in one instance you notice that the component needs some improvements. You make the necessary improvements to that instance. Now you decide you want all the components to look/function like that instance. If you could have the option to 1."make new main component from this instance" and 2."make this instance the main component" - it would be super helpful.
Matt Prina commented
This would be a great improvement. I find myself wanting to do this all the time. It would save a lot of time.
Also came here expecting to find an answer to this problem, and ended up disappointed because I see that Adobe hasn't implemented the functionality to create a master component from an instance component yet, even though people has been asking for it since two years ago. This would be indeed very useful and I am just another example who really needs it as well. It seems like Adobe doesn't have people working on real life projects who could realize what are the little and simple improvements they could do that would greatly facilitate the designers work, what a shame.
Lawrence Alberto commented
I wish they make this a priority as it will cut a lot of tedious work when setting up main components.
Mike M commented
This is needed so badly. It's super annoying and tedious to have to make multiple versions and alterations of an instance component for states and interactions to show clients, and when an option is chosen, we have to go and re-create the one chosen if it's not the master component.
It's insanity that we can't do this.
I just made 6 states. Then realized I need 6 individual components instead so that each "state" can have an independent trigger. If we could duplicate master components, then I would be able to duplicate, rename, and delete the superfluous states.
You are probably adding 2-3 hours of work to my day but not having this simple feature. And this happens to me all the time.
PLEEEEAAASE! The lack of this feature is driving me crazy!
Yes Please!! I spend so much time dealing with visuals independently because of this issue
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.
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
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.