so a change that will trigger recomposition must be a change as .value on a Flow

# compose

[oday]

so a change that will trigger recomposition must be a change as .value on a Flow

[Csaba Szugyiczki]

Flow -> State

[oday]

change a flow’s .value, trigger the collectAsState that collects it, triggers recomposition

[Csaba Szugyiczki]

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

[oday]

yes correct