That's another valid idea - I started to go down t...
# android-architecture
a
That's another valid idea - I started to go down that route on my last project. Ultimately I don't think I settled on a good reducing function, but I was also representing state as a
sealed class
of different states which made the copying logic from one state to another a PIA. It would probably be (much) easier if it was just represented as one data class. For this project I'm already pretty deep into the MVVM/non grouped state flow, so I'm hesitant to something that's a fairly radical departure from my current architecture