📚 Android Sample App using modular, clean, scalable, testable Architecture written in Kotlin that presents modern 2019 approach to Android application development, latest tech-stack and best practices. Application is based, apply and strictly complies with each of the following 5 points: • A single-activity architecture, using the Navigation component to manage fragment operations. • Android architecture components, part of Android Jetpack give to project a robust design, testable and maintainable. • Pattern Model-View-ViewModel (MVVM) facilitating separation of development of the graphical user interface. • S.O.L.I.D design principles intended to make software designs more understandable, flexible and maintainable. • Modular app architecture allows being developed features in isolation, independently from other features. For more technical details please check the project readme. Project link: https://github.com/VMadalin/kotlin-sample-app

Really nice, may I ask you, how did you made diagrams (subjecting they are hand painted)?

Thank you, Michael. I made them with draw.io, using a

comic

option on elements

I have also 2 other questions. 1. Did you thought about having "java/kotlin" modules without dependecy to Android? 2. Did you evaluated or made your thougts about Kotlin/multiplatform sharable modules ?

1. Of course, you can check the

buildSrc/commons/kotlin-library.gradle.kts

is a base to create such modules. But for the moment isn’t being used.

Exactly its about code sharing, to avoid code duplication, but not only between apps but also between platforms. I have to study your repo more deeper.

Wow @Michal Harakal that was a very nice graph, I appreciate your dedicated time on make this and encourage you to post a PR to add it on the readme of project 🙂 (if you want). Basically the relationship between

app -> features

is established indirectly by dynamicfeature. And is necessary for have access to navigation graph. In the other hand, the

features -> app

relationship is used for these reasons:  1). Have access to coreComponent initialised on application. This happens because the AppComponent depends on CoreComponent. 2). The app defines the styles, this way you could easily have 2 applications with different styles.

I am not sure if it is what you have expected, but at least we can start work with https://github.com/VMadalin/kotlin-sample-app/pull/1