Component States to Development (Design Specs)
How can we export Hover states to development?
In the specs there is only one state in the component. How will development see all states?
Kat Arnold commented
This would be extremely helpful to both designers & developers to be able to see the component states in the design specs link.
Irritating for sure and would welcome an update, but does it not just mean a bit more work for dev teams?
Wow, I can't believe we're at the point where developers can't see the hover state on buttons. EVERY freaking mobile or web app has buttons and a good UX expects hover state to indicate when a user is about to click on it..
My export to developers is useless, they still need the source file.
How in the world did someone miss this feature during initial development?
Gabriel Corral commented
Can also confirm this is a serious issue and should be addressed ASAP. What's the point of components if you can't translate that into code. My fastest workaround would be to modulate the different sections of the proto and duplicate the artboards for each state, its a pain but it should work.
Pete Conway commented
I am stunned that this wasn't implemented along with the component states functionality right at the very beginning, and that there wasn't clear information about the fact that states could not be exported for development.
This is absolutely a business critical feature for us. I've been working on a large project for many months and have just been informed by our development team that they are unable to access the design specs of the different states of the components I've built. We have designed hundreds of screens using components, some of which have up to 9 or 10 different states, and to try and unravel this and change all the designs, files and flows to not use components, or to manually export each state would take weeks worth of effort.
I'd appreciate it if someone could get in touch to discuss this with me and let me know when the fix is due to be released as it will have a significant impact on our project timescales. If there is a quick alternative to getting the dev teams what they need in the meantime I'd be really grateful!
Especially when I wont to share with developer, Our team need this.
I just found out about this when my colleague told me (in the final stages of a project!) that he was only able to inspect the main menu of my design. This feature should get more priority since the component feature is gonna be a big hurdle for the developers who get the handoff. My solution with a link for every part of the component was not well received. there are 20 links
Lucas Nieboer commented
Absolutely needed. Please provide an update ETA or roadmap for up-and-coming changes.
This update is absolutely essential for our whole design team.
Any update? We need this.
Really disappointed to hear from another commenter that this might be a low priority in the backlog. This is causing our team a HUGE headache. An ETA would be great.
Jennifer Gueringer commented
Please provide an update for when this will be released. This is a priority need.
This is a high-priority item for our entire in-house creative team. Can we get an update on when this will be released?
Any update on this? This would have a really positive impact on our business!
Can we get an update on when this will be released? This is a high priority need for our work.
Can we get an update on when this will be released? This is a high priority need for our work as well.
Is there an ETA yet on when this feature will be implemented - it's causing challenges for us as well.
Jenny Kon commented
Feature in the backlog sounds like it's NOT a priority
Matt Brett commented
Indeed, the lack of hover states in development mode is currently the only thing that's forcing me to export assets manually for developers.
Inc Beats commented
Without development this feature is just a pain