Kotlinx Coroutines recently introduced the
StateFlow API, described as “A Flow that represents a read-only state with a single updatable data value that emits updates to the value to its collectors”. This is generally seen as a replacement for
LiveData on Android but also, importantly, something that can be used in shared Kotlin Multiplatform code.
We've released kotlinx.coroutines 1.4.0 with the new StateFlow and SharedFlow, which provide a more elegant way to handle state in Kotlin programs with coroutines.— Kotlin (@kotlin) October 30, 2020
Give them a try and share your feedback with us! https://t.co/EkCW5E83eu
In a previous post I started exploring use of Kodein-DB NoSQL database. In this initial implementation we fetched data from remote endpoint at startup and stored that data in the DB (along with api in respository to read that data). What we’d generaly want in this scenario is a more reactive approach where UI layer is notified of any changes to DB and makes updates accordingly. As such I’ve made some changes to BikeShare repo that now uses
Kodein-DB api to register for updates to DB along with use of
StateFlow in the repository class. In our
ViewModel then we can now take advantage of
Flow operators available to map that data to version required by
Jetpack Compose UI code.
CityBikesRepository (part of shared Kotlin Multiplatform code) now includes following. We have a
StateFlow value representing the list of bike share networks (grouped by country)….which is updated whenever that list chages in the DB.
BikeShareViewModel in turn was updated to include following. The data from the repository just includes country code so we’re using Flow’s
map operator to convert to version that also includes the country name. This is relatively basic example but one of the strength’s of using
StateFlow here (code had been using
LiveData in a previous version) is the rich set of operators now available.
Finally the Jetpack Compose code can use
collectAsState() extension function to convert that to a
As with any new capability I think patterns will emerge over time as to how best to utilise
StateFlow (and also new
SharedFlow). What we’ve shown here is relatively basic example where
StateFlow seemed to fit well. Depending on nature of data and how it’s updated it may be more appropriate to use
Flow itself (still with use of
ViewModel perhaps utilising new
And this btw is what Jetpack Compose UI that uses the data looks like
Featured in Kotlin Weekly Issue #222
Exploring use of StateFlow in a Kotlin Multiplatform project https://t.co/FrDrPGeVpV— John O'Reilly (@joreilly) October 31, 2020
This outlines some changes made to BikeShare repo (https://t.co/9ghVs8MAOj) to start making use of StateFlow in shared #KMM repository (building on use of Kodein-DB NoSQL database).