SharedFlow<\/code> and StateFlow<\/code> are hot streams, but they serve slightly different purposes. Let’s answer with practical examples to better understand their use cases.<\/p>\n\n\n\nSharedFlow<\/h3>\n\n\n\n
SharedFlow<\/code> is like a broadcast channel<\/strong>. It can emit multiple values, and multiple collectors can listen to those values. It doesn’t have an initial value, but you can set how many values you want to replay to new collectors.<\/p>\n\n\n\nExample:<\/strong> Imagine a chat application where users can send messages. When a user sends a message, all online users should receive it. SharedFlow<\/code> can be used to broadcast these messages to all online users.<\/p>\n\n\n\nval messagesFlow: SharedFlow<String> = MutableSharedFlow()\n\n\/\/ User A sends a message\nlaunch {\n messagesFlow.emit("Hello from User A!")\n}\n\n\/\/ User B and User C are listening to the messages\nlaunch {\n messagesFlow.collect { message ->\n println("User B received: $message")\n }\n}\n\nlaunch {\n messagesFlow.collect { message ->\n println("User C received: $message")\n }\n}\n\n<\/code><\/pre>\n\n\n\nStateFlow<\/h3>\n\n\n\n
StateFlow<\/code> is a state holder<\/strong>. It always has a value (initial or updated), and it emits the latest value to its collectors. It’s useful when you want to represent a piece of state that can change over time.<\/p>\n\n\n\nExample:<\/strong> Consider a music player app. The player has a state (playing, paused, stopped). You can use StateFlow<\/code> to represent and observe the current state of the player.<\/p>\n\n\n\nval playerState: StateFlow<PlayerState> = MutableStateFlow(PlayerState.STOPPED)\n\n\/\/ Somewhere in the app, the state changes\nlaunch {\n playerState.value = PlayerState.PLAYING\n}\n\n\/\/ Another part of the app observes the player's state\nlaunch {\n playerState.collect { state ->\n when (state) {\n PlayerState.PLAYING -> println("Music is playing!")\n PlayerState.PAUSED -> println("Music is paused!")\n PlayerState.STOPPED -> println("Music is stopped!")\n }\n }\n}\n\n<\/code><\/pre>\n\n\n\nIn this example, whenever the player’s state changes, the observing part of the app will react accordingly.<\/p>\n\n\n\n
While both SharedFlow<\/code> and StateFlow<\/code> can be used to emit and collect values, SharedFlow<\/code> is more general<\/strong> and can be used for broadcasting multiple values to multiple collectors. In contrast, StateFlow<\/code> is specialized for representing and observing state changes.<\/p>\n\n\n\nIn the context of Android development<\/strong>, StateFlow<\/code><\/strong> is particularly beneficial when used with Jetpack Compose and ViewModels. It provides a seamless way to observe and react to state changes in the UI, ensuring that the view layer always reflects the latest application state.<\/p>\n\n\n\ntl;dr:<\/strong> SharedFlow<\/code> broadcasts multiple values to many collectors, like chat messages to users. StateFlow<\/code> holds and emits the latest state, like a music player’s status. Both are hot streams with distinct use cases.<\/p>\n\n\n\n
![\"\"](\"https:\/\/androidpro.io\/wp-content\/uploads\/2023\/06\/Projekt-bez-nazwy-5-1024x1024.png\")
<\/figure>\n<\/div>\n<\/div>\n<\/div><\/div>\n\n\n","protected":false},"excerpt":{"rendered":"