[Summary]
MVI helps maintain a single source of truth for the state of the view
overall (error, loading, success, empty).
StateFlow obviates LiveData with more capabilities along with
multiplatform support, unlike LiveData.
[Fix]
Add a DataState sealed class to model the view state, add Android lifecycle-ktx to collect the StateFlow in the MainActivity with lifecycleScope. Transform DataState from a sealed class in Kotlin shared to an enum in Swift.
ben-whit-ley
commented
3 years ago
[Summary] MVI helps maintain a single source of truth for the state of the view overall (error, loading, success, empty).
StateFlow obviates LiveData with more capabilities along with multiplatform support, unlike LiveData.
[Fix] Add a DataState sealed class to model the view state, add Android lifecycle-ktx to collect the StateFlow in the MainActivity with lifecycleScope. Transform DataState from a sealed class in Kotlin shared to an enum in Swift.
[Testing]
https://github.com/touchlab/KaMPKit/issues/161