In this episode, we continue our discussion from episode 148 on evolving android architectures. We collected some of the questions from the community and try to answer them.
Download episode directly
In this episode, Donn and Kaushik talk about the state of android architectures and how they’ve stared to evolve. Kaushik recently worked on a project of coming up with an evolved version of an MVVM architecture, very similar to what the Android community now calls MVI.
Special request: if you have follow up questions or clarifications or things you’d like to see specifically with respect to this dicussion, hit us up on the Discord #fragmented-podcast channel with your thoughts and we’ll make sure to address them in future parts!
Salient features of the pattern:
I. Screens are driven by a single ViewModel
II. Screens listen to a single Observable exposed from the ViewModel
III. Events are sent into the VM through a single function processInputs
IV. Break(ing) the Chain VI. Testing strategy
In this episode, he breaks down the pattern for us. He tells us how to implement it, how it helps with testing, the benefits of the pattern and some of the pitfalls. Recording this episode was riveting for us and we dive into some juicy technical details. Listen on!
MVI like patterns
Hannes series on MVI for Android (must read!) :