448 votes72 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
1,206 votesfeature-under-review · 286 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →
814 votes116 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
An error occurred while saving the commentNathan commented
Component state are great. However this is one of the features that is sorely needed now that we have states. Input and button states are a good examples of how organization of multiple states really matters. For instance, in an input I could need an input without a label or with a label, and without helper text or with help text, and need to show each of these in default, focus, error, and disabled states. Additionally, I made want to add or remove the required tag as needed.
One could argue that I could simply make 4-8 separate master components. However, if the intent is of the program is rapid prototyping, and I believe the intent of states is to improve this by not having to create repeat components that are, for all intent and purposes, closely related at the atomic level. The examples provided are additional artifacts that modify an atom (the most basic usable element), they are not atoms themselves.
I would not expect all sizes of each atomic element to be kept in state. However, there is not reason to consider this as well. I think the general idea is to keep your components tab as clean as possible. Particularly if an organization is trying to drive their design governance, in part, through XD.
Something as simple as not being able to reorder these makes the state less useful and, in some cases, causes outright confusion when consumed by those that did not create the component and it's corresponding states.