i did originally play with multiplatform saved state but to be honest the way state saving works on iOS didn't sit well with me - i was looking at it from a process death point of view but the lifecycle of the data is longer than that of SavedStateHandle

what I like about SavedStateHandle is the “auto setup/restore” it offers, I was thinking trying using multiplatform-settings, but that means I have to manually save the state every reduce operation 🤔 makes sense? Then in the container init I check if I have something cached, on

override fun onCleared()

I call .clear() problems: • saving in cache upon any reduce may not be optimal • how do i clear this cache when user kills the app manually, in other words, how can I distinguish between system kill or user kill (the latter I want a cache cleared)? 🤔

@appmattus actually theres a way to solve problem 2

how do i clear this cache when user kills the app manually, in other words, how can I distinguish between system kill or user kill (the latter I want a cache cleared)?

a very very 🔨 time one 😅 , clearing cache if splash launches 😬

<intent-filter>
    <action android:name="android.intent.action.MAIN" />
    <category android:name="android.intent.category.LAUNCHER" />
</intent-filter>

it works but i don’t like it very much…

I was imagining the VM also observing the state flow

dunno 🤔

I’m very happy with the state of orbit, thanks for your work guys

in its example: https://github.com/dbaroncelli/D-KMP-sample/blob/main/shared/src/commonMain/kotlin/eu/baroncelli/dkmpsample/shared/viewmodel/StateManager.kt I could be wrong, but I get the feeling this class tries to implement an MVI logic

I did not found state restore, maybe I’ve missed it.