If we can use a view model, is it considered bad practice to use

rememberSaveable

instead? For example, is it bad practice to remember the index of the selected tab bar inside a composable function instead of a view model? And if so, are there any boundaries?

I don't think so. It all depends on who needs to have access to the information. Storing everything in the viewmodel will make your viewmodel bloated and harder to maintain. There is information that is only pertinent to the composable and, in that case, a

rememberSaveable

or a state holder for somewhat more complex logic is the right approach.

If you haven’t seen it, @Manuel Vivo gives a great explanation of the differences between

rememberSaveable

,

ViewModel

,

SavedStateHandle

and persistent storage in

Thank you, I will take a look :)