Here's hoping it hasn't been too many times... Is ...

# compose

[Saiedmomen]

Here's hoping it hasn't been too many times...
Is is intended/ok to have State in ViewModels?

[Sean McQuillan [G]]

Yes*

State<T> is intended to be consumed by compose. If your ViewModel is holding UI state for compose-only code, then it works great as a UI-state holder similar to LiveData and is often more concise than alternatives.

The idiomatic form of state in a ViewModel looks like this:

class MyViewModel: ViewModel() {
    // define a state object & limit writes to only inside this ViewModel
    var clicks by mutableStateOf(0)
        private set

    fun increment() { clicks++ }
}

[Sean McQuillan [G]]

There's a section on this in the state codelab: https://developer.android.com/codelabs/jetpack-compose-state?return=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fcompose%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fjetpack-compose-state#8