Is there any documentation out on how compose hand...

# compose

[Matej Drobnič]

Is there any documentation out on how compose handles state saving (for both configuration changes and process death)? I'm mostly curious about various state objects that are arbitrary classes and thus cannot be parcelized into saved state bundle.

[Andrey Kulikov]

this feature is WIP atm. it is not yet implemented thus no documentation is available

[kioba]

configuration changes can be handled without killing the Activity. Last time we checked with @AdamPowell mentioned that an annotation @ComposeActivity might be only what we need on a composable function. And the Activity will handle config changes and triggers a recompose.

[kioba]

process death is a fascinating one.
Are there any discussions around this outside of the “official docs”?

[Andrey Kulikov]

@kioba not sure what discussions do you mean?

[Andrey Kulikov]

we will support saving and restoring composable local states into SavedInstanceState in some way(the final api is to be defined). so things like scroller position will survive both screen rotation and process recreation. aside for it we will probably recommend disabling activity recreation for screen rotation via the manifest for the purely composable powered activities. given we will support interop with the regular Android Views this would not be a default behavior now

[kioba]

I was referring to solving the SavedInstanceState, I wasn’t sure if compose will initiate changes how we handle or just a cleve mechanism on top of SavedInstanceState.
saving and restoring composable local states into SavedInstanceState in some way sounds like a callback on every state objects which makes senses.