The usage of

android:configChanges

with some flags (

orientation

for example) will be the standard in the future? I think that Compose can manage better the responsibility. In case of an affirmative reply, extending the ViewModel should be useless?

Are you sure is ViewModel’s only responsibility is against orientation changes? What about

Do not keep activities

and even fragments?

There will have only one activity, zero fragments

on an old project, before arch components, we had similar setup. ViewModels worked well then. but I see no point in avoiding it now.

Yeah, but I am not talking about old code. I see no reason to use fragments with a new project which uses compose

ViewModel also has some saved instance state APIs for working with process restart, but compose has savedInstanceState APIs as well

@Javier I think for Compose only app, Animation while going from potrait to landscape should be achievable now.