Android apps architecture

A quick comparison of used architectures in android applications. MVC/MVP/MVVM, android architecture components and clean architecture.

Transcript

1. ANDROID APPS ARCHITECTURE BAJIC DUSKO
2. Bajic Dusko ABOUT ME Senior android developer @ codecentric AG @bajicdusko on Twitter and GitHub
3. WHY ▸ Scalability ▸ Reliability ▸ Maintainability ▸ Implementation cost ‣ Reusability ‣ Separation of concerns ‣ Independence of libs ‣ Testability I am worried about: How can I help myself?
4. OLD WAY Everything is in activity - activity is everywhere One module ‣ app ‣ ui activities fragments util ‣ core api database provider model
5. MVC Not a web MVC! MODEL CONTROLLER VIEW What can we achieve ? Separation of business logic from 
 presentation To write less code What do we have? Controller as central point of 
 implementation Stateless views When to use ? Small projects Demo
6. MVC MODEL CONTROLLER VIEW BAD Highly coupled Hard to test Not scalable GOOD Less boilerplate Very easy to start with Separates business-presentation
7. MVP VIEW VIEW INTERFACE PRESENTER MODEL
8. MVP What can we achieve ? Decoupling Scalability Testability Reusability of presenter When to use ? In big teams On large projects What do we have? Independent presenter View hidden behind interface VIEW VIEW INTERFACE PRESENTER MODEL
9. MVP BAD More boilerplate Harder to maintain all interfaces GOOD Scalable Testable Modular Separation of concerns Reusable VIEW VIEW INTERFACE PRESENTER MODEL
10. MVVM VIEW VIEW MODEL DATA MODEL
11. MVVM VIEW VIEW MODEL DATA MODEL What do we have? MVP like structure Event publisher What can we achieve ? Decoupling Scalability Testability (IOC) Reactive approach When to use ? In big teams On large projects When all teammates are ready for such 
 approach
12. MVVM VIEW VIEW MODEL DATA MODEL BAD Different paradigm Depends of third party library GOOD Scalable Testable Modular Separation of concerns Reusable
13. ANDROID ARCHITECTURE COMPONENTS ‣ Lifecycle @OnLifecycleEvent(Lifecycle.Event.ON_RESUME) @OnLifecycleEvent(Lifecycle.Event.ON_PAUSE) ‣ Room SQLite Reactive ‣ LiveData Rx-like
14. CLEAN ARCHITECTURE ‣ Repository pattern ‣ Builder pattern ‣ Dependency injection ‣ Modulized ‣ Model per module ‣ Interfaces
15. THANK YOU!