pablichjenkov

> Do we know if this is resolved by compose compiler 1.4.0 and Kotlin 1.8.20? I'm seeing similar mentions in other related issues such as https://github.com/JetBrains/compose-multiplatform/issues/2901#issuecomment-1504894914 Yeup, got fixed in...

The question here is how to determine onCreate/onStart/onResume/ and the counterparts onPause/onStop/onDestroy in a Desktop App? If the lifecycle was simpler, like onCreate/onStart/onStop/onDestroy Then you could use the WindowState.isMinimized to...

Like I said, I believe it is a subject that will require some consensus. It is right that Android APIs are really well designed but some of them are a...

Yeah you're right, the focus does map well to resume/pause. I know iOS UiViewController can be mapped too, not sure about the 'browser'. Perhaps as you said, the reason might...

You don't have to write it in androidMain and copy to commonMain. You write it in commonMain and reference it from androidMain. ``` // This is in androidMain files or...

It has to be in the root Composable right Ivan? On another hand I really think bringing process-death/activity-resrorarion recovery concepts to compose is adding unnecessary complexity. That should be part...

I understand, what happens is sometimes `rememberSaveable` is misused / overused, saving state that perhaps don't belong there. But definitely the data or ui-state that goes into the database shouldn't...

If you plan to refactor I would suggest not using the Renderer.clone() technique when creating new Renderer instances. I suggest to delegate the Renderers creation to the outter layer. Like...

Also related: https://github.com/JetBrains/compose-multiplatform/issues/2785

> Bumping this up! Any info? What makes it different than just getting the size of your root composable and using CompositionLocal to pass it down the tree?