is there a way to handle life cycle as we are not ...

# compose

[Napa Ram]

is there a way to handle life cycle as we are not using fragment and only one activity is there is project, i need inform view model
1. when compose screen created
2. when app go in background
3. when moving from one screen to another and when we are coming back to same screen
4. basically all lifecycle event

[Johan Reitan]

Have a look at this post that explains the new lifecycle api: https://medium.com/androiddevelopers/a-safer-way-to-collect-flows-from-android-uis-23080b1f8bda

[Alex]

Just do it in the activity and pass the values to the viewmodel, which then in turn can expose StateFlows to inform your composition

[Napa Ram]

in my project there are around 15-20 module it will be difficult to handle everything in one activity a

[Napa Ram]

is compose not giving anything regarding lifecycle

[Johan Reitan]

Yes, you have the repeatOnLifecycle that’s explained in the linked post above. They even have an example with Compose at the end

[Ian Lake]

Lifecycle events are still a thing in Compose: https://kotlinlang.slack.com/archives/CJLTWPH7S/p1630080009198100?thread_ts=1630078038.194200&cid=CJLTWPH7S

[Michael Paus]

I am wondering how the lifecycle handling concepts explained in the article will map to Compose Desktop where you are facing the same problem but don’t have all these Android specific APIs available. Or am I missing something here?