is there an alternative to

androidx.lifecycle

in kmm?

What kind of lifecycle? Only android has a really complicated lifecycle. Desktop is basically run and go and it will always run the same no matter how much time passes or if its in focus

Desktop pretty much has the same lifestyle because the lifecycle maps to states of a window manager regardless of the OS. Android apps can be run in floating window mode on large display/desktops, so it only makes sense desktop applications could get the same lifecycle. Pause/resume is focused, start/stop is on visible, create/destroy is effectively the window instantiation lifecycle

so this is a mobile kmm (android and iOS) and I want to use this in the shared - commonMain. so is there a way to make it work? otherwise, is there a known an alternative in iOS? then I can do

expect

and

actual

implementations

@Mitchell Syer having onAppMinimized/onAppInBackground would be helpful to stop some stuff / analytics

in my case I use the function for such usecases

you have to do an expect class for every import you're not getting in "pure" kotlin, in android will be the class import, in others you have to invent

yeah, looks like I’ll have to do that anyone have an idea of how to receive onStart an onPause events from iOS?

LaunchedEffect vs DisposableEffect

will check

YW

DisposableEffect won't do the job for minimizing the app