UDF architectures, primarily MVI are getting more and more attention, especially with the rise of Compose. But MVI has its own issues, such as need to mock different classes in Unit testing as well as combination of sync and async work straight at the place when a user action comes. At Squire we transitioned from MVI based on RIBs and MVICore to our internally-written Runtime following The Elm Architecture principles. I'm going to present the reasoning, the learnings and the way we did it in the apps for hundreds of thousands people. I'll showcase a live coding example where we will create a full-blown screen built on MVU under 20 minutes. And I'm sure that will make you try the approach 😉 You'll get: Understanding the drawbacks of MVI / MVVM compared to MVU. Understanding of the applicability of the MVU. Being able to reason about the Runtime handling the Side Effects and how can it be used to increase testability of code. Being able to understand how a Feature is structured in MVU and why based on a real-world example." [color=#111111][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][size=2][font=Verdana, Arial, Helvetica, sans-serif][h2][b][url=https://github.com/Gaket/presentations/blob/master/2022/MVU/From%20Ribs%20to%20MVU.pdf]Slides[/url][/b][/font][/size][/font][/size][/color][/font][/size][/color][/color][color=#111111][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][size=2][font=Verdana, Arial, Helvetica, sans-serif][/h2][/font][/size][/font][/size][/color][/font][/size][/color][/color]