Our presenters do not retain state. You're free to hook up the regular save instance state stuff lik...

# squarelibraries

[jw]

Our presenters do not retain state. You're free to hook up the regular save instance state stuff like Compose UI does though.

[spierce7]

var count by remember { mutableStateOf(0) }

This is state in the presenter, right? Do you just mean once the UI has been navigated away from it, all state is lost?

You’re free to hook up the regular save instance state stuff like Compose UI does though

I haven’t tried this is compose multiplatform yet. I’ll look into it. Thanks

[jw]

That is state, but it's not retained across recreation

[jw]

You would need to use rememberSavable or whatever

[saket]

I haven't used Molecule yet, but I'd assume that values saved using remember will be remembered during the lifecycle of your presenter. It's upto you how you manage/retain your presenters.

what jake said

[saket]

Can rememberSaveable be used from molecule? If yes then I'd imagine they're saved in the same way as Compose UI -- by hooking into a state registry owned by your app.

[jw]

Yes but you have to hook it up yourself. We don't do anything with it.

[Paul Woitaschek]

Why do your presenters never retain state?

[saket]

are you asking why is state not retained across presenter recreations?

[Paul Woitaschek]

Yes

[Paul Woitaschek]

For example say we have a form, user adds something, leaves the app to find some date he needs, system kills app, user returns.

[saket]

he they need

I imagine those form values will be retained by your UI and not your presenter

[jw]

Yep. That's done at the UI layer.