Hey, I am trying to achieve the following but so far have no luck: I have compose inside my app but ...

# compose

[Kata]

Hey, I am trying to achieve the following but so far have no luck: I have compose inside my app but instead of using a ViewModel I am using Redux. When my screen closes I would like to clean up the state. But what is important that when the screen is still on the backstack it should not be cleaned up to prevent the state from being lost when navigating back. I know in a viewModel word I could use the onCleared() method of the viewModel.
I would expect to have something like a DisposableSavableEffect acting like the rememberSavable that would only be called once the screen is opened and then disposed when it is removed from the backstack.
Any ideas on how to solve this issue with compose?

[Timo Drick]

I don't think that this is possible with the standard components. Than you have to write you own navigation stack. But in my opinion this is not difficult in Compose.

[Kata]

So basically the only architecture that is supported by compose out of the box it viewModel?🫠

[Timo Drick]

What you want i don't think that you can do this with viewModels. Because you do not have enough control over the lifecycle of them.

[Kata]

the init and onClear from the viewModel would be enough, they are only destroyed once the view is not in the stack

[Timo Drick]

Ok when this is really the case why you do not use them. But i think this is not correct.

[Timo Drick]

You should only depend on the states which are stored in the navigation stack you use. And the lifecycle of other components should be more or less independ.

[Kata]

I want to achieve the same thing as if you would create a viewModel and in the init you would make a network call. Now this wouldn't be called again on orientation change or on back navigation. And I am afraid compose is only set up for viewmodel architecture

[Timo Drick]

Compose is just the UI framework. But you get some helper classes for viewmodels which makes it easy to use.
But you can do what you want.

[Timo Drick]

If you want to have a component that live as long as the related screen is in the navigation stack i think than you have to implement your own navigation stack. Because this is not supported by the standard components. But as i said in Compose this is really easy. At the end it is more or less just a data struckture.

[Kata]

I feel there should be a better way than rewriting the whole navigation

[Timo Drick]

It depends on what you really need. In my opinion the official compose navigation is very limited and can only be used for navigation of main screens of you app maybe.

[Timo Drick]

Also maybe important viewModels only exists in Android so if you want to have KMM you need to use your own system anyways.

[Ian Lake]

Timo is right, there is no signal for this. Here's the still open ticket for a "permanently destroyed effect": https://issuetracker.google.com/issues/177562901

[Kata]

Nice that is a feature that would be super to have