How to write your own MVI library and why you shouldn't
Matthew Dolan & Mikołaj Leszczyński
Senior Android Engineer & Android Software Architect
Model-View-Intent is a simple architectural pattern in principle, but questions come up when you try to implement it yourself. We draw on our 2+ years of experience with orbit-mvi, our MVI library, to show best practices for using an MVI system in your application.
How do you integrate with Android? What happens when you rotate your device? What about navigation or one-off events? How do you make the system type-safe? What about developer experience? If you’ve ever had similar questions come to our talk!
Matt Dolan has been developing with Android since the dark days of v1.6. When he's not eating doughnuts he's passionate about bringing developers and designers together to #buildbetterapps
Android Software Architect at Babylon health, previously at Just Eat. Still searching for mobile architecture nirvana. Massive fan of reactive patterns and Kotlin. Has been recently dabbling in some functional programming concepts. Looking forward to teaching his daughter programming once she's old enough. Boardgamer and motorcyclist.