Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Forgetting Android Jorge J. Barroso! Tech Lead Android Core! jbarroso@tuenti.com! @flipper83
Any fool can write code that a computer can understand. Good programmers write code that humans can understand.! Martin Fo...
1 Solid
Single responsibility principle Open/closed principle Liskov substitution principle Interface segregation principle Depend...
Clean Architecture2
A good architecture allows you to defer framework decisions. A good architecture allows frameworks to act as plugins to th...
UI External! Interfaces Db Push Network Storage Interfaces Interfaces Business Model Interactors Interactors
UI! Layer UI! Layer UI! Data Model Data Mapper Boundary Interactor Bussines! Data Model Data! Storage Test! Storage Data M...
FeedViewModel FeedBoundary FeedListFragment FeedProvider GetFeed GetFeedImp List<Hipster> User! DataSource! Net UserDataSo...
Conclusion3 http://www.flickr.com/photos/inf3ktion/
Good Layer Responsabilites
Easy to test and mock
Easy to add or modify code
Easy to hide implementations
Easy to find smells
Async code
Duplicate data model
Change your mind
Not silver bullets
http://jobs.tuenti.com! jbarroso@tuenti.com! @flipper83
Forgetting android
Forgetting android
Upcoming SlideShare
Loading in …5
×

Forgetting android

3,092 views

Published on

This talk is about use clean architecture on android development.

Published in: Software, Technology
no profile picture user

  • Be the first to comment

Show More

Forgetting android

  1. 1. Forgetting Android Jorge J. Barroso! Tech Lead Android Core! jbarroso@tuenti.com! @flipper83
  2. 2. Any fool can write code that a computer can understand. Good programmers write code that humans can understand.! Martin Fowler
  3. 3. 1 Solid
  4. 4. Single responsibility principle Open/closed principle Liskov substitution principle Interface segregation principle Dependency inversion principle
  5. 5. Clean Architecture2
  6. 6. 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”
  7. 7. UI External! Interfaces Db Push Network Storage Interfaces Interfaces Business Model Interactors Interactors
  8. 8. 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
  9. 9. FeedViewModel FeedBoundary FeedListFragment FeedProvider GetFeed GetFeedImp List<Hipster> User! DataSource! Net UserDataSourceLikeDataSource Like! DataSource! Parse API UserApi API Retrofit! api Parse! api
  10. 10. Conclusion3 http://www.flickr.com/photos/inf3ktion/
  11. 11. Good Layer Responsabilites
  12. 12. Easy to test and mock
  13. 13. Easy to add or modify code
  14. 14. Easy to hide implementations
  15. 15. Easy to find smells
  16. 16. Async code
  17. 17. Duplicate data model
  18. 18. Change your mind
  19. 19. Not silver bullets
  20. 20. http://jobs.tuenti.com! jbarroso@tuenti.com! @flipper83

×