3 Reasons Why I'm not Migrating LiveData to StateFlow

• nowinandroid

  58 15,215 9.7 Kotlin

  A fully functional Android app built entirely with Kotlin and Jetpack Compose

  

I have a confession to make, after reading through StateFlow and SharedFlow documentation, watching Android Developers's video, and reading nowinandroid source codes, I'm not convinced to migrate LiveData to StateFlow or SharedFlow. At least for now. Here's why:

• Mona-Android-App

  1 9 4.4 Kotlin

  Jetpack Compose app (Astro clone) with Genshin Impact theme

The stable version of Jetpack Compose is just released last year. While I do like writing UI using Compose, I think most companies still need more time to adopt Compose.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• architecture-samples

  27 43,819 1.0 Kotlin

  A collection of samples to discuss and showcase different architectural tools and patterns for Android apps.

  

For merging multiple data-sources, like network and database, I can use Repository backed with NetworkDataSources and DbDataSources. For data manipulation, Kotlin's collection has many useful functions (map, reduce, groupBy, count, etc.). If I want to ensure a data can only be emitted once, a simple modification to LiveData is enough (SingleLiveData

Suggest a related project