From_scratch_to_a_scalable_architecture.pdf

From scratch to a scalable and maintainable architecture in Android

Transcript

1. From scratch to a scalable and maintainable architecture in Android
2. Juan Guillermo Gómez ➢ Co-Leader y Co-Founder del GDG Cali. ➢ CEO DevHack. ➢ Consultant and advisor on software architecture, cloud computing and software development. ➢ Experience in several languages ​​and platforms. (C, C#, Java, NodeJS, android, GCP, Firebase). ➢ Google Developer Expert (GDE) in Firebase ➢ BS in System Engineering and a MS in Software Engineering. ➢ @jggomez ➢ jggomez@devhack.co <vanity> </vanity>
3. Experiences https://play.google.com/store/apps/details?id=leadis.co.ekosave_mobile
4. Experiences https://play.google.com/store/apps/details?id=org.pfccap.education
5. Experiences
6. First Steps ➢ App without layers ➢ Spaghetti code. ➢ Without design patterns. ➢ Async Task memory leaks. ➢ HttpClients, JSONObjects. ➢ Unreadable. ➢ Unmaintained code. ➢ Unmaintained code database. ➢ Sqlite memory leaks. ➢ Low reuse.
7. First Steps ➢ App without layers ➢ Spaghetti code. ➢ Without design patterns. ➢ Async Task memory leaks. ➢ HttpClients, JSONObjects. ➢ Unreadable. ➢ Unmaintained code. ➢ Unmaintained code database. ➢ Sqlite memory leaks. ➢ Low reuse.
8. Continuous Improvement SOLID ➢ Single Responsibility ➢ Open / Close ➢ Liskov substitution ➢ Interface Segregation ➢ Dependency Inversion
9. Continuous Improvement ➢ Quality Attributes. ➢ Software Architecture ➢ Design patterns. ➢ Reuse. ➢ Maintainability. ➢ Usability. ➢ Portability. ➢ Analyzability. ➢ Reliability. ➢ Performance.
10. Continuous Improvement ➢ Reuse. ➢ Maintainability. ➢ Usability. ➢ Portability. ➢ Analyzability. ➢ Reliability. ➢ Performance. ➢ SEPARATION OF CONCERNS ➢ DRIVE YOUR UI FROM A MODEL
11. Continuous Improvement Callbacks Memory leaks
12. Continuous Improvement ➢ Retrofit. ➢ Observers. ➢ Called from the presenters
13. Architecture
14. uhmmm...
15. Clean Architecture ➢ Separation of concerns. ➢ Dividing the software into layers. ➢ Independent of frameworks. ➢ Testeable. ➢ Independent of the UI. ➢ Independent of the database. ➢ Independent of any external agency.
16. Clean Architecture the primary purpose of architecture is to support the life cycle of the system. Good architecture makes the system easy to understand, easy to develop, easy to maintain, and easy to deploy. The ultimate goal is to minimize the lifetime cost of the system and to maximize programmer productivity.
17. Clean Architecture
18. Clean Architecture ➢ Repository Layer. ➢ Builder. ➢ Use Case. ➢ Factories. ➢ Command Pattern. ➢ Dependency inversion.
19. Clean Architecture
20. Continuous Improvement Remove Callbacks and add RX.
21. Continuous Improvement Dependency inversion
22. Continuous Improvement Remove Interfaces Interface Segregation Remove o add components Add external components. Architecture - Android Libraries - Dependencies
23. Components Architects
24. Components Architects
25. Continuous Improvement
26. Continuous Improvement
27. Continuous Improvement
28. Continuous Improvement
29. Continuous Improvement
30. https://www.facebook.com/escueladevhack/ Escuela de Hackers www.devhack.co https://github.com/escueladevhack