HS Android - Clean Architecture

Andrei Lisun, Android developer
What is good software architecture and why every Android developer should care about implementing it? I’ll answer this question by talking about golden rules of good architecture. Also, I’ll show how this rules can be applied in Android development using Clean Architecture.

Transcript

1. Clean Architecture Andrei Lisun
2. Why? “My apps work without any architecture” • Architecture makes it easier or harder to think about problems you need to solve. • Architectural decisions stick with your app.
3. Trends change quickly, but some basic principles are timeless
4. • UI can be changed easily • DBMS can be changed easily • No Android framework dependencies = local unit tests Independent of UI, DB, Frameworks
5. • Elements have singularity of purpose Separation of concerns
6. • More local unit tests = better • Allows to cover at least business logic Testable
7. • Encourages to write code without repetition DRY
8. Independence SoC Testable DRY
9. Model-View-Presenter
10. View Presenter Repository Remote data source Local data source Realm, SQlite Retrofit UI • Activity, Fragment • Presents data in a way decided by the Presenter • Fully passive • Has reference to Presenter
11. View Presenter Repository Remote data source Local data source Realm, SQlite Retrofit UI • Makes queries to the Repository • Updates the View • All business logic here • Has reference to the View and Repository
12. • Responsible for managing data • Manages in-memory cache • No business logic here View Presenter Repository Remote data source Local data source Realm, SQlite Retrofit UI
13. View Presenter Repository Remote data source Local data source Realm, SQlite Retrofit UI
14. Independence View Presenter Repository Remote data source Local data source Realm, SQlite Retrofit UI
15. Independence SoC Testable DRY View Presenter Repository Remote data source Local data source Realm, SQlite Retrofit UI
35. Move to Repository? • No business logic in Repository • Repository is already quite large
36. Extract Class?
37. View Presenter Repository Remote data source Local data source
38. View Presenter Repository Remote data source Local data source
39. Use Case Use Case View Presenter Repository Remote data source Local data source ...
40. Use Case Use Case View Presenter Repository Remote data source Local data source ... Layers
41. Use Case Use Case View Presenter Repository Remote data source Local data source ... Data Layers
42. Use Case Use Case View Presenter Repository Remote data source Local data source ... Layers Domain Data
43. Use Case Use Case View Presenter Repository Remote data source Local data source ... Layers Domain Presentation Data
44. Use Case Use Case View Presenter Repository Remote data source Local data source ... Clean Architecture Domain Presentation Data
45. Use Case Use Case View Presenter Repository Remote data source Local data source ... Domain Presentation Independence SoC Testable DRY Data
69. • Testing is easier • Easy to add new features • Code is more maintainable • Bugs are easier to isolate Pros
70. • Lots of details • More code to write Cons
71. Clean Architecture Sample: https://github.com/googlesamples/android-architecture/tree/todo-mvp-clean/ Clean Architecture Sample(separate modules): https://github.com/android10/Android-CleanArchitecture Android Architecture Telegram group: https://t.me/Android_Architecture