Ensure component states are supported by XD development API
I'm using a platform, called Zeroheight, to create my company design system. It has a plugin that integrates with Adobe XD.
I'm trying to display, on my design system, all the components states and be able to interact with them on the platform.
I was informed by the support team of zeroheight that the adobe XD API doesn't support states and for that reason, they can't have access to components states.
This would really add value to my work! Thanks.
Thanks for your feedback! You should definitely reach out on this site as well: https://forums.adobexdplatform.com/
Supporting component states would be a huge plus!
My company would like to use Zeroheight as a platform, to create the new company design system. It has a plugin that integrates with Adobe XD.
I want to display, on the design system, all the components and be able to interact with them on the platform. They have a inspect mode, where developers can easily display all the information about the selected component.
I was informed by the support team of zeroheight that the adobe XD API doesn't support properties like corner radius and shadows, so they can't be displayed in zeroheight inspect mode.
It works with other design tools like figma though...
Could you somehow add that information to the XD API?
We are now trying to find out if we have to switch to figma for our new design system.
Daniel Wilcomb commented
I would like to add my $0.02 here as well. My team also uses Zeroheight, and having the ability to support states on components in the design system would go a huge way to making the development workflow smooth. (In particular, showing states on icons - hover, active, disabled, etc - with downloadable assets for each state.)
Same here, I am also using zero height and it would be great if the XD API could support component states !
Carlos R commented
Just echoing support here. Right now I'm outputting a design asset for each state, which means I have to kind of "blow up" my design system doc with all the component states set up individually so they can be output to the zeroheight API.
In order for us to use component states and easily display them in design system documentation with Zeroheight, we need the XD API to support states. Otherwise, using states is actually creating more work on us for the Design System Documentation.