At the moment state (Model) is not retains on orie...

# compose

[Kazemihabib1996]

At the moment state (Model) is not retains on orientation change. Is this supposed to change in future or we are supposed to use ViewModel with jetpack compose?

[Zach Klippenstein (he/him) [MOD]]

Since layouts in Compose are kotlin and not XML resources, you can probably handle rotation config changes yourself instead of letting the system restart your activity.

You could also use rememberSavedInstanceState.

[Leland Richardson [G]]

savedInstanceState is the persisted version of state (equivalent to rememberSavedInstanceState { mutableStateof(…) }

[Kazemihabib1996]

@Leland Richardson [G]
why it's not the default behavior of remeber?

[Leland Richardson [G]]

because there is a maximum transaction size and it would be easy to surpass it if we dumped everything into it. also, not all types are serializable

[Leland Richardson [G]]

also, slightly related, if you are running a pure compose app, you should probably turn off restarts on configuration changes

[Leland Richardson [G]]

but savedInstanceState is still needed for process death in any event

[Kazemihabib1996]

Yeah, turning it off is a good idea

[Kazemihabib1996]

thank you.

[Sinan Kozak]

About turning off configuration changes, will compose handle view/UI rotation depending on the device rotation? I can only imagine a nice continues animation from portrait to landscape. Will it be possible?

[Leland Richardson [G]]

that’s the goal. i think it would require some platform APIs to handle properly and don’t remember if they were available or not

[Leland Richardson [G]]

my desire was to have all of the configuration (orientation, screen size, etc.) all as just part of some model object that you could use in your composable if you wanted, and it would automatically adjust (recompose) whenever the configuration changed at all