This project is based in some ideas of Clean architecture I've been developing lately on another project Pokompose but dealing with the Marvel API © 2022 MARVEL.
My proposal of architecture as you can see in this diagram:
I use to work with a kind of modularized architecture separated on three layers for UI, domain and data, with a domain isolated of the framework as a pure kotlin project.
My idea with this project was to split the domain on three modules following the dependency inversion principle to decouple the side dealing with the framework for data from the other that use the UI.
Also I try to implement a pure kotlin Presentation layer that contains the UI logic in a agnostic way, so as the Data layer implements repositories and the Domain contains the use cases, I've created an EventHandler interface as a bridge between ViewModels and the use cases, it's main purpose is to contain the flow of reactions from UI events to the resulting states.
Inside the UI module you could see an architecture closer to MVI pattern, using typed interfaces for views and viewmodels, sharing a StateHolder and a specified set of ViewEvents, which allows you to have declared a clear way of communication on both directions and the different ViewStates that a view could get.
I gather here all the things I've been learning through my latest working experience:
- Asynchronous handling with Coroutines
- UI reactive state management with Flows
- Functional programming support through Λrrow
- More features like Kotlin DSL for Gradle and other things...
Although I'm not working currently with Jetpack Compose I've created this project on top of such feature as I'm learning by the way.
Written with StackEdit.