LAUNCHED: State management for prototypes

Hi, is there an option to persist component state between artboards? E.g. having a toggle on frame A and frame B that is inactive by default. After toggling state to active on frame A, navigating to frame B will reset the toggle to inactive.

Is it possible to persist state between frame changes?

Btw super happy about interactive components! What a great and powerful feature! Thanks for the beta invite!

Hey Dan! Right now we don’t support state preservation for interactive components, but it’s something we’re thinking about and would love to support in the future.

Glad you’re enjoying the feature, and keep the feedback coming!

FYI just changed the category on this one from Questions to Feedback so we can make sure to keep track of it on the product side.

Hi Kelsey, thanks for the fast reply! Would be awesome to get this feature down the road.

I discovered this when creating an actual prototype with a flow between components and frames.

When using interactive components combined with a way to go back to a previous frame (such as a back button, delete button or edit button) the interactive component will skip its variants, as if the interaction was already done, and won’t restart the variant’s interactions.

How to replicate this:

1. Use the interactive components to create a loader (loop using AfterDelay to connect the variants)
2. Create 2 pages
3. In the first page place a button that navigates to another page
4. In the second page place the loader and a button to go back to the first page
5. Click the first button
6. Wait till the loader completes the animation
7. Click the back button
8. Click the first button again

Expected result
When clicking the back button I expect that the loader has restarted the animation and will load again if pressing the first button

Actual result
The first time it will work perfectly, but when going back a second time the prototype will skip the whole animation, as if it was already executed.

I’ve prepared a simple file so you can analyse this:

I’m having a similar issue with a fly-out menu. When I open the menu and interact with it it works fine. However, when I close the menu and reopen it, it reverts to it’s last state and not the first state it’s linked to.

Yes! She same thing happened to me when trying to create a dropdown menu!

Right now, I don’t think you can do it natively. The workaround I use is to open in overlay the components you want to reset. Since an overlay is destroyed and created each time, it will reset your interactive component. The main limitation to this, since you can only have one overlay at a time, is that you cannot use other overlays. At least this is a workaround.

This is so annoying…
@Nicolas_Demange workaround doesn’t work in my case for multiple reasons:

1. I don’t want to let the user get in that state using arrow keys;
2. I cannot use it with After Delay, even if I close the overlay before everything finish.

Can we get an official response about how we can reset the state of the interactive component to the initial or desired one?

I’m sad to say, I’ve had to fall back to disconnecting all the component interactions, and then creating individual screen-level frames (screen x dropdown open, screen x dropdown closed) and all the combinatorial spaghetti that goes with that 😢 Hopefully we’ll hear something about the issue soon.