With LiveData we could easily reach the same logic...

# coroutines

[Eric Ampire [MOD]]

With LiveData we could easily reach the same logic, so I would like to know the difference between LiveData and StateFlow.

class DownloadingModel {

   private val _state = MutableStateFlow<DownloadStatus>(DownloadStatus.NOT_REQUESTED)
   val state: StateFlow<DownloadStatus> get() = _state

   suspend fun download() {
       _state.value = DownloadStatus.INITIALIZED
       initializeConnection()
       processAvailableContent {
               partialData: ByteArray,
               downloadedBytes: Long,
               totalBytes: Long
           ->
           storePartialData(partialData)
           _state = DownloadProgress(downloadedBytes.toDouble() / totalBytes)
       }
       _state.value = DownloadStatus.SUCCESS
   }
}

[louiscad]

LiveData is Android only and doesn't come with Flow operators.

[Adam Powell]

Also LiveData isn't thread-safe and can only be mutated or observed on the main thread

[Eric Ampire [MOD]]

Another question : Once the state changes, and the observer consumes or collects this new state, the channel becomes empty or it converts the last state.

In other words, can StateFlow easily manage navigation between different views of the application?

[Adam Powell]

no, for those cases you want something more like a channel or channel.receiveAsFlow()

[Adam Powell]

LiveData shouldn't be used for this either for similar reasons

[Adam Powell]

but people try to put that square peg into the round hole anyway because there's no LiveChannel or similar 🙂

[Eric Ampire [MOD]]

Okay thanks