so a change that will trigger recomposition must b...
# compose
o
so a change that will trigger recomposition must be a change as .value on a Flow
c
Flow -> State
o
change a flow’s .value, trigger the collectAsState that collects it, triggers recomposition
c
In this sense yes. But you do not need a Flow to create State. You might as well create it on its own with mutableStateOf, or from an RxJava Stream, or a LiveData. I just wanted to emphasize that the change of your State will be the reason ultimately for your recomposition, no matter what triggered it
o
yes correct