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.

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?

We need the specs for states and hovers pls!!

Any updates on this issue?

The fact that you still have not provide us with any sort of way to get the state of a component is unbelievable. All your efforts should have been focused on that task since (or even before) that update released on Nov 2019.

É necessário que os desenvolvedores possam ver as informações do estado!
Obrigado!

Yes, please add support for inspecting all states!

開発者がステートの情報を確認できるようにしていただきたいです。
よろしくお願いいたします！

If. page I am inspecting has a component on It. I would like to be able to inspect that component and all of its states

it should be a priority! how come you support component states but neglect how to share them! Am I supposed to create a screen for every instance of the components i use!

Any updates about this?

No updates yet???

Guys, this is causing a back and forth between the developers building our designs. Please seriously consider this request.

Very important must have feature

Six months passed and nothing? Adobe is kidding us? An expensive signature plan to don't be heard? A so simple feature which should be always there. Come on Adobe!

Same here.

I can't believe these are not exported. Very fundamental!

The lack of development specs for component states is causing major roadblocks for my team. Please add this feature!

Is there a way to view code snippets for buttons in their default and hover states when a prototype is shared with developers?