Fernando Cejas

@spirosoik :smile: Thank you!

@zhengxiaopeng what is your solution then?

I'm a strong believer of having View Models and each layer should have its model to deal with. So I avoid coupling between layers. If you share Domain models with...

@RamiJemli yup

@aldoKelvianto exactly 😄

@japplin that can be interpreted in different ways but there is actually a refactor to get rid of the modules and have every feature in its own package. Neither silver...

Hello @ashraffouad thanks for the good words! I really appreciate that you guys find all this useful! By the way, very interesting stuff and I definitely encourage you to keep...

@ashraffouad unfortunately I cannot reply every single question from the community due the lack of time. Everything related with this repo is in this section. People are great contributing and...

To build on this, the idea of mapping and having your view models is that you only put in there the data you need, so you can have different UserDetailsView...

There is a totally new approach that I have been working on, written in Kotlin: https://fernandocejas.com/2018/05/07/architecting-android-reloaded/