Solid principles for Android developer

Popular SOLID practices on Android

Transcript

1. SOLID FOR ANDROID P L A N DAY
2. SOLID PRINCIPLES 1. SINGLE REPONSIBILITY 2. OPEN / CLOSED 3. LISKOV SUBSTITUTION 4. INTERFACE SEGREGATION 5. DEPENDENCY INVERSION
3. SINGLE REPOSIBILITY • “A class should have only one reason to change.” • Example: RecyclerView’s Adapter: – Only adapter’s responsibility: mapping an object to its corresponding view. FAIL!!!
4. SINGLE REPOSIBILITY
5. OPEN/CLOSED • “software entities (classes, modules, functions, etc) should be open for extension, but closed for modification” FAIL!!!
6. OPEN/CLOSED
7. LISKOV SUBSTITUTION • “Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.”
8. INTEFACE SEGREGATION • “Many client-specific interfaces are better than one general purpose interface.” More complicated
9. INTEFACE SEGREGATION Multiple-method Interface
10. DEPENDENCY INVERSION 1. “High-level modules should not depend on low-level modules. Both should depend on abstractions.” 2. “Abstractions should not depend on details. Details should depend on abstractions.” Traditional application layers
11. Android UI Business Layer Data Layer
13. THANKS FOR LISTENING