Kotlin Android Model-View-Whatever Architecture Example w/ Coroutines, Sealed Class, Result

This video is an edited version of a livecoding episode where I talked about the architecture I'm playing around with in SpaceNotes. I call my architecture style "Model-View-Whatever", as I'm tired of using traditional names that people don't really agree on or implement the same way. Also, I won't always have the same set of architectural objects in a given feature, if the feature is not as complicated, or more complicated. In any case, to summarize the different parts, it looks something like: - View (user interface renderer/event producer), - ViewLogic (most people call it presenter or controller), - ViewModel (mine does what the name implies, but most people fill these with logic which annoys me based on the name), - Adapter (for helping to draw streams of data in the View), - DomainLogic (helps for multiplatform support if in separate module and can act as a decision maker for complex backend logic), - RepositoryPattern (abstract the DataSources from the DomainLogic), - DataSources (self explanatory). Follow the wiseAss Community: https://www.instagram.com/wiseassbrand/ https://www.facebook.com/wiseassblog/ https://twitter.com/wiseass301 http://wiseassblog.com/ https://www.linkedin.com/in/ryan-kay-808388114 Support wiseAss here: https://www.patreon.com/bePatron?u=5114325 https://www.paypal.me/ryanmkay