Skip to main content

LAUNCHED: State management for prototypes


Show first post

205 replies

Peter_Roper

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


David_Nichols1

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
  • 10 replies
  • February 24, 2022

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


Luigi_Chelli

+1, it’s really bothering me


joshmillgate

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


Louisa1
  • 2 replies
  • March 14, 2022

+1 for this feature


Alex_Carvalho2

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

+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

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

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


Adam_Hay
  • 1 reply
  • March 25, 2022

i am finding myself in this very situation with multi-tier navigation. everything works as expected on the initial path, but when returning to the origin page, the specific secondary flyout menu used to first navigate is stuck in an open position, where I would like it to return to its original state. totally agree with the proposed solution of being able to set the origin back to its initial state upon navigating to a new frame.


Johann2
  • 20 replies
  • March 29, 2022

Workaround:
State stays persistent even in multiple nested interactive component. You can go very far with this approach.

Only reason I would need frame to frame persistence is to reflect some kind of logic or content change.


Nicholas_Del_Conte

+1 this has been going on for ages. It’s a stupid bug and must be fixed. Devs please fix this.


Alex_Harbuzinski

+1 As well. My clients think my prototypes are broken since they can’t preview animations multiple times when they get into pages. Please make component resetting come true.


raul_cerda1

+1
I need this for my prototypes as soon as possible.


Terry2
  • 1 reply
  • April 11, 2022

Same case here


Wolfgang_Hahner

+1
I agree, this is hard to explain to clients!


Henry_Harding

Bump. I’d really like a way to reset a variant back to it’s original state. I constantly run into this issue with my prototypes that use forms or flyouts. The best solution I’ve found is to close and refresh the page, which is painful to do and is not at all practical for demos and presentation.


paulina.ciastek

+1 Same problem here


Richard11

Same. I have a screen with a loading bar component that upon 100% completion goes to a results page. When I link back to that screen with the loading bar, it still shows 100% for a split-second before going to the results page again. The components need an original state that is always loaded every time the user navigates back to that frame.


Regi
  • Active Member
  • 20 replies
  • April 27, 2022

having the same problem. I’d like to either ‘reset’ or choose a state the interactive component is in when going between frames (using same component). The current implementation requires re-creating a noodle of pages (as someone else just mentioned) making them useless.


Josh_Bernard

+1
Looking to be able to return all interactive components to default state


Regi
  • Active Member
  • 20 replies
  • April 29, 2022

Just had a question about this the other day. Same - interactive components are only useful for a 1 page prototype at the moment. +1 for the need to implement this.


JohnDashiell

After hours of trying to get a button to reset, I finally figured out a very simple workaround. Use Touch Down to reset to the initial state and use Touch Up for what you’d normally use just regular Touch for. Make sure to set the delay and ease to 1ms so you don’t see the reset. Let me know if you’re having trouble and I’ll try helping out.


JohnDashiell

Basically, it won’t work if you have any ease at all. Putting it to 1ms allows the processing to occurs before Figma has time to prevent the reset.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings