A modern programming language that makes developers happier.

kotlinlang

Which is the difference betwen
```val stateHolder = remember { MyState() }```
and
```val stateHolder by remember { mutableStateOf(MyState()) }```
Checking <https://github.com/android/nowinandroid/blob/d15c739812f25401b21614fe0f7e18534d285921/app/src/main/kotlin/com/google/samples/apps/nowinandroid/ui/NiaAppState.kt#L54|nowinandroid> sample, they use a NiaAppState that they declare using the first way, without mutableStateOf. Supposedly, mutableStateOf is necessary to listen to changes in variables, so, why not using it?

For example, in this case, which approach is necessary and why?
```@Stable
class MyState{
    var currentStep by mutableStateOf(Step.ARE_YOU_SATISFIED)
        private set

    fun updateCurrentStep(value: Step) {
        currentStep = value
    }
}```


maybe it's because currentStep is already a mutableStateOf? and the value of MyState is not changed but the value of it's internal variable does?

Yeah having two "layers" of mutability is not what you want basically ever.
This article <https://blog.zachklipp.com/two-mutables-dont-make-a-right/|https://blog.zachklipp.com/two-mutables-dont-make-a-right/> isn't focused on exactly this I think, but it may still be useful for you to read.