Is it true that for a pure Compose app, we should ...

# compose

[Afzal Najam]

Is it true that for a pure Compose app, we should set android:configChanges="orientation|screenSize|screenLayout|keyboardHidden" ?

[louiscad]

Everything actually, which is more than that.

[Afzal Najam]

Interesting. Thanks! I guess I gotta try and see how the app works after setting that. Didn't realize that was the recommendation.

[louiscad]

It's not properly documented yet, but Adam Powell from Google participated in a discussion on this Slack not long ago. You can probably find it by searching with the right keywords.

[Afzal Najam]

Think I found it: https://kotlinlang.slack.com/archives/CJLTWPH7S/p1618760581089700?thread_ts=1618691113.058800&cid=CJLTWPH7S

[Arkadii Ivanov]

It is still not clear how Compose will deal with configuration specific resources in this case. And I am afraid it won't.

[louiscad]

Compose dedicated functions like stringResource should trigger a local recomposition on config change.

[Arkadii Ivanov]

Yeah, it hooks to AndroidComposeView.configurationChangeObserver under the hood.

[Arkadii Ivanov]

Then shouldn't this be a recommended approach and the ViewModel be discouraged from using?

[louiscad]

It should, and eventually, it will, as you can see in the linked thread above your messages.

[Arkadii Ivanov]

Tried it just now without any issues. Strings/dimensions/etc are updated, UI state is preserved, looks fine.