Rationale Behind Using Only One Module "App" instead of multiple modules.

android10 / Android-CleanArchitecture-Kotlin

This is a movies sample app in Kotlin, which is part of a serie of blog posts I have written about architecting android application using different approaches.

https://fernandocejas.com/2018/05/07/architecting-android-reloaded/

4.69k stars 935 forks source link

Rationale Behind Using Only One Module "App" instead of multiple modules. #48

Closed crjacinro closed 6 years ago

crjacinro commented 6 years ago

Hi @android10

When I compared it to the java version of this project, there are multiple java modules used (data, domain, presentation) but here, in the kotlin project, it only uses one App module.

So is it correct to assume that the better way to architect projects is to use only one module? or is it a limitation currently for Kotlin?

Thank you

Zhuinden commented 6 years ago

If you check https://github.com/JakeWharton/SdkSearch/ it's just that data/domain/presentation top level isn't as good as slicing it by features

android10 commented 6 years ago

If you read the article, it clearly says the reasons why this technical decision was made. https://fernandocejas.com/2018/05/07/architecting-android-reloaded/