i recommend not using viewmodels (the library), but for the general concept of view models you should be posting back to the main thread before they are cached

i recommend not using viewmodels (the library)

I'm very interested on knowing the reason behind this opinion

It's just a service locator that survives rotation

I see. Then what would an alternative be? I see the VMs as a way to keep alive everything that should be alive during the natural use of an app, basically relying on the

onCleared

call to tell me the app is not in use anymore. How else can I get to that point? If I go back to pre-VM times, I can only remember having to deal with presistance, services and loaders/headless fragments. That or resetting everything every time the screen is rotated (or another config change)

Move the entirety of state outside the activity and the only responsibility of things in the activity is to bind UI models. Activities are a porthole to state.

that's exactly what my activities/fragments are right now. But ViewModels are holding that state and mutating it

in reverse order of lifetimes: the activity non-config instance, the application instance, the process lifetime (i.e., static scope)

do you have an example of how you keep the state in android in your Sdk Search project or is it different due to multiplatform (no need to link it, just need to know if I can find something there that might be interesting)

It uses the activity non-config instance to retain the presenter through configuration changes. There's only one screen, though, so it can get away with this. I keep meaning to figure out a way to make the app more complex so I can design something more robust but just haven't had the time.

Cool. I'll take a look. Thanks 👍