From scratch to a scalable and maintainable architecture in Android 

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 ➢ [email protected] 

Experiences https://play.google.com/store/apps/details?id=leadis.co.ekosave_mobile 

Experiences https://play.google.com/store/apps/details?id=org.pfccap.education 

Experiences 

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. 

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. 

Continuous Improvement SOLID ➢ Single Responsibility ➢ Open / Close ➢ Liskov substitution ➢ Interface Segregation ➢ Dependency Inversion 

Continuous Improvement ➢ Quality Attributes. ➢ Software Architecture ➢ Design patterns. ➢ Reuse. ➢ Maintainability. ➢ Usability. ➢ Portability. ➢ Analyzability. ➢ Reliability. ➢ Performance. 

Continuous Improvement ➢ Reuse. ➢ Maintainability. ➢ Usability. ➢ Portability. ➢ Analyzability. ➢ Reliability. ➢ Performance. ➢ SEPARATION OF CONCERNS ➢ DRIVE YOUR UI FROM A MODEL 

Continuous Improvement Callbacks Memory leaks 

Continuous Improvement ➢ Retrofit. ➢ Observers. ➢ Called from the presenters 

Architecture 

uhmmm... 

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. 

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. 

Clean Architecture 

Clean Architecture ➢ Repository Layer. ➢ Builder. ➢ Use Case. ➢ Factories. ➢ Command Pattern. ➢ Dependency inversion. 

Clean Architecture 

Continuous Improvement Remove Callbacks and add RX. 

Continuous Improvement Dependency inversion 

Continuous Improvement Remove Interfaces Interface Segregation Remove o add components Add external components. Architecture - Android Libraries - Dependencies 

Components Architects 

Components Architects 

Continuous Improvement 

Continuous Improvement 

Continuous Improvement 

Continuous Improvement 

Continuous Improvement 

https://www.facebook.com/escueladevhack/ Escuela de Hackers www.devhack.co https://github.com/escueladevhack