Forgetting Android

Architecture is About Intent, not Frameworks. In this talk we talk about how we can prepare our Android application to use the Android framework as a tool instead of cramming your app into their limited constraints.

We are focussed on SOLID principles and concepts like testability, independency of UI, decoupled code, etc. are a fundamental part of this session.

Transcript

1. Forgetting Android v.2 Jorge Juan Barroso Carmona jorge@karumi.com @flipper83 +JorgeJBarroso Android expert
2. Basho. Poet Karumi is the beauty of ordinary things spoken of in a simple way.
4. Any fool can write code that a computer can understand. Good programmers write code that humans can understand. Martin Fowler
6. 1 Solid
7. Single responsibility principle Open/closed principle Liskov substitution principle Interface segregation principle Dependency inversion principle
8. Clean Architecture 2
9. 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 External Interfaces Db Push Network Storage Interfaces Interfaces Business Model Interactors Interactors
11. UI Layer UI Layer UI Data Model Data Mapper Interactor Bussines Data Model Data Storage Test Storage Data Mapper Data Mapper Storage Data Model Test Data Model
12. FeedViewModel FeedBoundary FeedListFragment FeedProvider GetFeed GetFeedImp List<Hipster> User DataSource Net UserDataSource LikeDataSource Like DataSource Parse API UserApi API Retrofit api Parse api UI Layer Domain Layer use Cases or Interactors Data sources
13. FeedViewModel FeedListFragment FeedPresenter GetFeed Hipsters User Repository Like Repository User Data source UserApi Like DS Retrofit api Db View Syncronous LikeApi Retrofit api Parse UserDB Parse Parse UI Layer / MVP Domain Layer Use cases Data sources Hipsters Read only
14. Conclusion 3 http://www.flickr.com/photos/inf3ktion/
15. Good Layer Responsabilites
16. Easy to test and mock
17. Easy to add or modify code
18. Easy to hide implementations
19. Easy to find smells
20. Async code
21. Duplicate data model
22. Change your mind
23. Not silver bullets
24. Find me I am very social! jorge@karumi.com @flipper83 +JorgeJBarroso Questions?