Clean Architecture in Android

This talk is for clean architecture and how to apply it in android development for members at PrimeLabo

Transcript

1. Clean Architecture in Android Development Ban Chinh Thanh (@thanhbc1990) Prime Labo Co. VN Android developer
2. Ban Chính Thành • A Little ninja at PrimeLabo • Android developer Email:chinh.thanh@primelabo.com.vn Github: http://github.com/thanhbc
3. What is Architecture?
4. • MVP, MVC, MVVM • Gson • RxJava • Retrofit • Dagger NO!
5. Tools • MVP, MVC, MVVM • Gson • RxJava • Retrofit • Dagger
6. –Robert C. Martin (Uncle Bob) “Architecture is about Intent, not Frameworks”
7. Architecture is about intent
8. Architecture is about use case
9. Generally in Clean, code is separated into layers in an onion shape with one dependency rule: The inner layers should not know anything about the outer layers. Meaning that the dependencies should point inwards.
12. Why Clean Architecture?
13. It makes your code • Independent of Frameworks • Testable • Independent of UI • Independent of Database • Independent of any external agency
14. Some vocabulary • Entities: These are the business objects of the application. • Use cases: These use cases orchestrate the flow of data to and from the entities. Are also called Interactors. • Interface Adapters: This set of adapters convert data from the format most convenient for the use cases and entities. Presenters and Controllers belong here. • Frameworks and Drivers: This is where all the details go: UI, tools, frameworks, etc.
15. Android?
16. The Objective is the separation of concerns by keeping the business rules not knowing anything at all about the outside world!
18. Presentation Layer
19. Presentation Layer • Where the logic related with views and animations happens • There is no logic inside them other than UI logic • Presenters in this layer are composed with interactors (use cases) that perform the job in a new thread outside the android UI thread, and come back using a callback with the data that will be rendered in the view
20. Domain Layer • Business rules here: all logic happens in this layer. • All the external components use interfaces when connecting to the business objects.
21. Data Layer All data needed for the application comes from this layer through a UserRepository implementation (the interface is in the domain layer) that uses a Repository Pattern with a strategy that, through a factory, picks different data sources depending on certain conditions.
22. Android demo
23. References • Clean architecture: https://8thlight.com/blog/uncle-bob/2012/08/13/ the-clean-architecture.html • Repository pattern: http://martinfowler.com/eaaCatalog/ repository.html • MVP Pattern: https://en.wikipedia.org/wiki/Model–view–presenter
24. THANK YOU! Twitter: @thanhbc1990 Personal email: thanhbc1990@gmail.com