Skip to main content
Shane
February 26, 2021

LAUNCHED: State management for prototypes

  • February 26, 2021
  • 205 replies
  • 21529 views

Just struck a pretty simple use case/scenario where I need the component to reset it’s state when I leave the frame. This has been touched on elsewhere, but this is such a common and key use that I thought I’d put it in it’s own thread.

Scenario:
I’ve got a dropdown menu with three items in it, with each item changing what columns are visible in a table and some other control states. I have three frames, each with a view of the table setup as it should be, and want to use the dropdown items to navigate between the frames - basically faking the table state change. All of this works perfectly, however when I navigate back to a previous table view state, the dropdown component is already in it’s open state - not what I want.

Current workaround: none that I can come up with (other than not using interactive components at all for this, and just using multiple frames for the dropdown open/closed states as I would previously)

Suggestions:

  1. Have a “reset component on leaving this frame” setting for instances of a component on a frame - useful for this situation and others, but needs to be a setting so that components that should keep their state between frames can do so (light/dark toggle maybe? Something like that).
  2. Do it all in a single frame, with the dropdown component changing the the state of the table component - no frame navigation required. Would work nicely for the particular use case I’m working with here, but not sure it would solve all similar situations.
  3. Do both 1 and 2. This solution is my preferred solution 😉 😆

EDIT:
Other threads that relate:

205 replies

Peter_Roper
February 17, 2022

This would be super useful. IC feels redundant for our team without this feature.

David_Nichols1
February 19, 2022

I’m having the same problem with Variants persisting when navigating across pages in an interactive prototype. Similar to previous comments, I have a navigation component that remembers the state in which you left it (e.g. not the default state) when returning to the homepage.

Marcus_Harvey
New Participant
February 24, 2022

Same. This makes interactive components rather un-useful for many purposes.

Luigi_Chelli
New Member
March 3, 2022

+1, it’s really bothering me

joshmillgate
March 9, 2022

Would love to see this implemented, makes prototypes much more viable.

Louisa1
March 14, 2022

+1 for this feature

Alex_Carvalho2
March 15, 2022

Is anyone in Figma listening to the community? Seems like some of these bugs are quite easy to correct, why spend so much time in between updates, when small stuff could be handled. Resetting interactive components is essential in animation, so users can go back and repeat steps, or simply not having to restart a prototype from the beginning (which can be quite time-consuming)

Lauren_Aldrich
March 18, 2022

+1. I have spent hours trying to find a work-around for this issue to no avail. @Figma_Support please fix this as soon as possible.

Jeffrey_Gadzala
March 18, 2022

Same challenge. Would be nice to have the ability to either:

A) automatically reset an interactive component when the page with said component is navigated to
B) define two interactions that execute simultaneously with the same trigger

A solves most issues talked about here; B solves my particular issue and adds functionality to the prototype feature set.

Joakim_Pahlman
March 20, 2022

I really need this for a choose favorite function im designing:)