I'm starting to think about switching our company to Figma 🤣

Hello dear XD Team,
I enthusiastically switched from Figma to XD. And then I have to realize that this function does not exist! Is there a reason for this?

In reality, the states in Adobe XD is not used which means you will fall into a pit when you use the states of components so messy and a bad experience.

That is not to be called a design system haha.

I've been building quite a few design system and this limitation one is by far to most irritating part when it comes to my team using published libraries.

The ability to mark elements as persistent through all states as someone mention in the comment below, is quite fundamental to this overall feature to work properly or at least to feel complete.

2022... not solved yet.

Adding another comment to this thread. We need the ability to mark elements within a component as persistent through all states of the component. This gives all elements within a component the option to be persistent or state-specific.

@elain (adobe) - this isn't a bug, it's a missing feature of the component system.

Thanks!

We NEED XD to keep the labels through ALL STATES/ variants we create so we don't have to change the labels for all states of our component it makes us waist so much time and kills workflow.

Properties on components and their states/variants need to apply separately.

Seems to be the same request as https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/38973007-allow-component-instance-overrides-to-be-inherited, which has considerably more votes. All who voted here might consider voting for the request linked above, too.

Bump! This would save me tons of time... it's like XD doesn't even want to be a design program.

Heyyyyyyyy adobe can you pleeeaaaaase at leaaaaast consider the fudging feature?
Figma had this forever! Gosh using component is sooo frustrating in XD. You can tell by how many letters I had to my words :(

We need a component with the option to keep text persistent. Every time I make a new iteration of a button I have to change the text in every single state of the button.

If I have 10 buttons with 3 states each, that's so much editing of text.

It's not just buttons - cards, simple text links, any component with text and a state other than "default" requires editing of every single state. There should be an option to keep any selected layer persistent across all states.

I can't even count the number of times I've been presenting a prototype, showed a hover-state and was disappointed to find the hover text was wrong.

Working with components becomes a very cumbersome content management task when working with multiple states.

Simple example: a button component with standard, hover and active states. Re-use this component for another button and change the text – I have to update the text in each state separately.

Or have a pic that zooms on hover.

Would be best if I could designate a "variable" like text-field or pic-frame, once filled in in the "standard" state, it carries it´s content troughout different states and ONLY applies changes to it (color, size, …)

Working with components becomes a very cumbersome content management task when working with multiple states.

Simple example: a button component with standard, hover and active states. Re-use this component for another button and change the text – I have to update the text in each state separately.

Or have a pic that zooms on hover.

Would be best if I could designate a "variable" like text-field or pic-frame, once filled in in the "standard" state, it carries it´s content troughout different states and ONLY applies changes to it (color, size, …)

I have created many button states on my main UI (the base of my design system).

BUT when I'm prototyping or building a screen with my UI kit and I change the copy of the "rest" state, this copy doesn't change for the rest of the states which forces me to modify it, EVERY time, BY HAND.

This (as you can imagine) is time-consuming and not ideal.
Id' love if you just allow the component to inherit the copy of the rest state.

Please do this quickly - this is a huuuge time-waster.

See also: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/39051064-create-new-main-component-from-existing-component

A duplicate of a component as a new base for another element could help here to keep also other properties e. g. width.

Description: I want to create a button with text and different states as a component in the library. Each state should show the same text. Only element properties like the color of the button, the button outline and the text color should change from state to state. In the component instance it should be able to change the text in the default state and then all states take and display this text.

Current behavior: When I create new states of the button, each state gets a copy of all button elements. If I now use this button from the library, I get an instance, where I can change the text of the button. But the text will only be overridden in the current state and not in all states at once. I need to go to each state and change the text to the desired button name. This is much work when having a lot of states and a lot of different buttons.

Solution: Add the property “Keep text of the Default State” as an option for a component instance.

Value: It saves time in the prototype creation phase if I only need to change the text of the default state in an instance of a button component with many states.

A checkbox to ALLOW for text propagation would be an invaluable addition for designers, not only for their workflows but for developer handoff. As someone who wears both hats, I tend to be a developer-friendly designer.

To ensure consistent typographic styles, including padding, I create a "Text | Content" component. I can then toggle between text states as if they were HTML classes or HTML tags (H1, H2, H3, P, etc.) While this approach is faster and more flexible than having separate components per tag/class, I have to copy and paste the text from one state to another if I decide to change my styling from an "H1" to an "H2", for example.

This feature would speed up my workflow while ensuring consistent typography in my designs.

Hahaha, a blast from the past indeed, but a bit more useful for components than what we have now imo

Wow -- that Flash reference brought back some painful memories!