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?
This is now available for you in today’s release of XD 34. You will need to re-publish your design specs to access component states.
Michael Stevens commented
I was trying to accomplish this tonight and ended up here. So there is no way to download the hover state asset even though it's marked for export? that's disappointing :( Any chance of opening this up again?
Veerle Pieters commented
Not working still. Was looking for solution and ended up here. July 24th 2021 and not working still. It only appears if I ungroup the component... :(
Sorry, but in version 38 this doesn't work properly … and i can't believe that it does in Version 34 … please this is absolutely no missing feature – this is a bug! Hoverstates aren't a new shit … thanks for taking action
I am seeing a bug were the component states are not generating downloadable assets for all states. I am only able get one state of the component to export. I am seeing that whatever is the bottom-most layer is the only one that creates the download link when publishing the share link for development. However, when I publish the count of downloadable assets says all the states are getting exported even though they are not.
To the two comments below, I was able to see the specific state's specs (like a hover state) by clicking the element, clicking the desired state in the 'Components' list, and then re-clicking the element, which loads the appropriate specs (not the most intuitive flow, but hey it's there).
This is not implemented! Using XD 184.108.40.206
Kenneth Kawamoto commented
I don't think this is implemented, Elaine...?
Finally, this is a step in the right direction, but keeping track of all the components and navigation between is a bit hard.
Melba Searcy commented
Yes! We need hover states in dev specs!!!!
Would be great if development would be able to see the hover states, and also having the color of that hover state showing in the list for them.
Reno Ren commented
When share on the web, developers can"t view the different state of Components, so they can not view the style of Components on the different state
In my prototype I maked a button blue as default and red as hover and I animated it, so I can see this button working in preview mode when mouse hover. But, when I share the prototype as developer mode the developer can't see status hover (red) only default (blue).
This is needed ASAP
Any update on this??? Been long time Having hard time, still cant share specs for all states of my components.
Hi Everyone, as you can see above, the feature was started and then went to backlog. It only has 345 votes which makes is a lower priority feature. So please upvote.
Often times developers will ask me for different colours on icons, then I have to make those changes and add a copy of the component in that new colour onto the canvas of the design system XD link I set up.
I'd suggested they use SVG's but to no avail.
Can you please make the instances of a component downloadable. Maybe have a check option in the Share panel.
i tried to add to my post, but i couldn't... here's a video explaining the issue.
when i share my design for "development", the developer is able to navigate through the prototype, able to download assets and take code snippets, which is super awesome, BUT the issue here is when you go to "specs" to download assets and take the text etc, the prototype goes to default state of the design, and by that the developer can't take all the assets, only the ones in the default page of the design.
when i am using your wicked prototype abilities, stats and all that, i lose all that, now i have to design tons of other pages with different stats and different content etc, it's like i have to build another plain old school prototype so the developer can grab the assets.
what i was expecting, it could be a good possible solution to this, is when the developer goes to a certain "state" in the prototype, when they jump to the "spec" mode, the prototype stays in the same state, doesn't reset to default screen, and then they can grab all the assets they need.
that's what i thought will happen, this will cut down time on prototyping for stakeholders and re-prototyping for developers.
when i share my design for "development", the developer is able to navigate through the prototype, able to comment, and able to download assets and take code snippets, which is super awesome, BUT the issue is when you go to "specss" to download assets and take the text etc, developers goe to default state of the design, ignoring the prototype, and by that the developer can't take all the assets, only the ones in the default page of the design.
when i am using your wicked prototype capabilities, stats and all that, i lose all of that, all the efforts put to make the prototype is gone, now i have to go back to "old school" prototyping, design tons of other pages with different stats and different content etc, so developers can take all the assets they need.
the expected behavior, or maybe that's just me, is when the developer goes to a certain "state" in the prototype and they toggle to "specs" mode, the prototype stays in that same state so developers can take the assets they need, rather than reseting to default design screen.
that's what i thought will happen when i shared my design with the developer, if that solutions works, this will help cut down time on prototyping for stakeholders and re-prototyping for developers.
Courtney @ Global Work & Travel commented
Come on Adobe, reply to this...whats the point of us spending hours prototyping component states if the developer cant delve in to the states and see each components styles? is this a joke, why no reply to this absolutely unbelievable over sight?