How do Flow, StateFlow, and SharedFlow differ in the context of reactive programming?

In Kotlin (especially in Android), Flow, StateFlow, and SharedFlow are different types of data streams with different properties:

• Flow: a cold stream that starts emitting data only upon subscription. Each subscriber receives data from the beginning, and data is not retained between subscriptions.

• StateFlow: a hot stream that always holds the current state (value). When a new subscriber joins, it immediately receives the latest value, and then all subsequent updates. It is used to represent state that can change over time.

• SharedFlow: a hot stream that can have multiple subscribers and does not store state by default (but can be configured with buffers and replay). It allows broadcasting events to multiple subscribers without retaining the last value.

Example:

val flow = flow {
    emit(1)
    delay(1000)
    emit(2)
}

val stateFlow = MutableStateFlow(0)
stateFlow.value = 1

val sharedFlow = MutableSharedFlow<Int>()
sharedFlow.emit(1)

• Flow is suitable for sequential computations and one-time data streams.
• StateFlow is for storing and observing state.
• SharedFlow is for broadcasting events, such as navigation or messages.

This helps in building reactive UI and data handling in Android apps.