Currently my favorite architecture is the Clean Architecture, with MVVM in the presentation layer.

# android-architecture

[Diefferson]

Currently my favorite architecture is the Clean Architecture, with MVVM in the presentation layer.

[Alexander Khyzhun]

Hello, could you please show me some of your projects (might be test-projects)?
I’m just interested in how you did it.

[Diefferson]

https://github.com/diefferson/Android-Kotlin-Clean-Architecture

[Diefferson]

This is a simple example of architecture that I am using

[Alexander Khyzhun]

thanks

[florent]

I don't really see the advantage to have 3 modules (data, domain, presentation), it is impossible to create a instant app with this architecture. Moreover, the package used are not really useful because every that they contain will be available via a simple search. For example the classes of the package repository can be found by typing Repository in Android studio search

[gildor]

it is impossible to create a instant app with this architecture

It’s not true, you just need 3 levels per each feature module

classes of the package repository can be found by typing Repository

What do you mean?
You can actually hide one module from another. Not sure about this particular sample

[panwrona]

I can tell clean architecture is a lifesaver in some cases. Right now my colleagues are 1 month ahead of backend and are doing UI with mocked data. So the work will be done only in domain and data when API is ready

[Diefferson]

I never worked with Instant Apps, is necessary an specific separations of layers?

[gildor]

Instant apps require to use multiple modules (feature module), so each module must be separated from others, so if you use clean archticture approach with separation of layers to modules, you need own set of layers for each module, or you can share some parts of course