1.
Forgetting Android
Jorge J. Barroso!
Tech Lead Android Core!
jbarroso@tuenti.com!
@flipper83

2.
Any fool can write code that a computer can understand. Good
programmers write code that humans can understand.!
Martin Fowler

3.
1 Solid

4.
Single responsibility principle
Open/closed principle
Liskov substitution principle
Interface segregation principle
Dependency inversion principle

5.
Clean Architecture2

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.
UI
External!
Interfaces
Db
Push
Network
Storage
Interfaces
Interfaces
Business
Model
Interactors
Interactors

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.
FeedViewModel
FeedBoundary
FeedListFragment
FeedProvider
GetFeed GetFeedImp
List<Hipster>
User!
DataSource!
Net
UserDataSourceLikeDataSource
Like!
DataSource!
Parse
API
UserApi
API
Retrofit!
api
Parse!
api

10.
Conclusion3
http://www.flickr.com/photos/inf3ktion/

11.
Good Layer Responsabilites

12.
Easy to test and mock

13.
Easy to add or modify code

14.
Easy to hide implementations

15.
Easy to find smells

16.
Async code

17.
Duplicate data model

18.
Change your mind

19.
Not silver bullets

20.
http://jobs.tuenti.com!
jbarroso@tuenti.com!
@flipper83