Forgetting android
11 likes•3,447 views
This document discusses principles of clean architecture and how to structure Android applications according to those principles. It recommends separating an app into layers including UI, business logic, data access, and external interfaces. Each layer only knows about the layers immediately around it, allowing independence and flexibility. The document provides examples of how to implement clean architecture in Android with features like view models, boundary classes, and data mappers. Overall it promotes writing code that is easy to test, modify, and maintain as requirements change over time.
Forgetting android
- 1. Forgetting Android Jorge J. Barroso! Tech Lead Android Core! [email protected]! @flipper83
- 3. Any fool can write code that a computer can understand. Good programmers write code that humans can understand.! Martin Fowler
- 5. 1 Solid
- 6. Single responsibility principle Open/closed principle Liskov substitution principle Interface segregation principle Dependency inversion principle
- 8. A good architecture allows you to defer framework decisions. A good architecture allows frameworks to act as plugins to the app.! Robert Martin “The database is a detail, a hardware detail. We would not use one at all if all our data could fit in memory for ever”
- 10. UI! Layer UI! Layer UI! Data Model Data Mapper Boundary Interactor Bussines! Data Model Data! Storage Test! Storage Data Mapper Data Mapper Storage! Data Model Test! Data Model
- 12. Conclusion3 http://www.flickr.com/photos/inf3ktion/
- 14. Easy to test and mock
- 15. Easy to add or modify code
- 16. Easy to hide implementations
- 17. Easy to find smells
- 18. Async code
- 20. Change your mind