The document discusses the implementation of Android clean architecture, detailing the various layers such as presentation, domain, and data layers, along with concepts like repository pattern and interactor boundaries. It also includes code snippets for user authentication, data retrieval, and managing UI elements, emphasizing the principles of organized and maintainable code structure. Furthermore, it highlights the advantages of this architecture in terms of simplicity, scalability, and teamwork efficiency.

1. Android Clean Architecture
Cauê Ferreira
@CaueFerreira

2. Cauê Ferreira
@CaueFerreira
caueferreira
Developer

3. +100k clientes
+300 parceiros integrados
+1 bi/ ano
+200 colaboradores
+ 8 anos de operação

4. App
user
password
Login
User name
email
age

5. User name
email
age
products
product 1
product 2
product 3
product 4
User name
email
age
products
product 1
product 2
product 3
product 4
amount of money
last order

9. MoipAccountManager.retrieveOauth(getActivity(), externalId -> {
loginProgressDialog = setUpProgressDialog(getActivity());
loginProgressDialog.show();
AccountApi.getAccount(MoipSharedPreferences.getInstance().getExternalId(), account -> {
MoipSharedPreferences.getInstance().saveAccount(account);
ContaMoipApplication.getInstance().identifyPerson(account);
toDashboard();
loginProgressDialog.hide();
}, error -> {
loginProgressDialog.hide();
MoipSharedPreferences.getInstance().clear();
});
}, () -> {
MoipSharedPreferences.getInstance().clear();
});

10. private void toggleViews(final RelativeLayout parent, final boolean enable) {
parent.setEnabled(enable);
for (int i = 0; i < parent.getChildCount(); i++) {
View child = parent.getChildAt(i);
if (child instanceof ViewGroup) {
} else {
child.setEnabled(enable);
if (child.isClickable())
child.setClickable(enable);
}
}
}

11. private void loadData() {
String fakeEmail = "";
if (order.getCustomer().getEmail() != null) { ContaMoipApplication.getInstance().loadGravatar(order.getCustomer().getEmail(), profileImage);
txtEmail.setText(order.getCustomer().getEmail());
} else {
ContaMoipApplication.getInstance().loadGravatar(fakeEmail, profileImage);
txtEmail.setText(fakeEmail);
}
txtData.setText(Date.parse(order.getCreatedAt(), Date.BRAZILIAN_DATE));
txtDetail.setText(" ");
txtOrderValue.setTextWithCleanAmount(order.getAmount().getTotal());
txtMoipTax.setTextWithCleanAmount((long) order.getAmount().getFees());
txtLiquidValue.setTextWithCleanAmount(order.getAmount().getTotal() - order.getAmount().getFees());
txtDueDate.setText(Date.parse(order.getUpdatedAt(), Date.BRAZILIAN_DATE));
}
private int getLayoutStatusColor(final OrderStatus status) {
switch (status) {
case PAID:
return getActivity().getResources().getColor(R.color.paid_order);
case REVERTED:
return getActivity().getResources().getColor(R.color.refunded_order);
case NOT_PAID:
return getActivity().getResources().getColor(R.color.not_paid_order);
default:
return getActivity().getResources().getColor(R.color.other_order_status);
}
}

12. View
View Model
Presenter
Controller
Request Model
Response Model
Boundary
Boundary
Interactor
Entity Gateway
Entity Gateway
Implementation
Database APIs
Entity
Entity
Entity

13. View
View Model
Presenter
Controller
Request Model
Response Model
Boundary
Boundary
Interactor
Entity Gateway
Entity Gateway
Implementation
Database APIs
Entity
Entity
Entity
Interactions have: Application specific rules

14. View
View Model
Presenter
Controller
Request Model
Response Model
Boundary
Boundary
Interactor
Entity Gateway
Entity Gateway
Implementation
Database APIs
Entity
Entity
Entity
Interactions have: Application Independent rules

15. View
View Model
Presenter
Controller
Request Model
Response Model
Boundary
Boundary
Interactor
Entity Gateway
Entity Gateway
Implementation
Database APIs
Entity
Entity
Entity

16. View
View Model
Presenter
Controller
Request Model
Response Model
Boundary
Boundary
Interactor
Entity Gateway
Entity Gateway
Implementation
Database APIs
Entity
Entity
Entity

17. View
View Model
Presenter
Controller
Request Model
Response Model
Boundary
Boundary
Interactor
Entity Gateway
Entity Gateway
Implementation
Database APIs
Entity
Entity
Entity

18. View
View Model
Presenter
Controller
Request Model
Response Model
Boundary
Boundary
Interactor
Entity Gateway
Entity Gateway
Implementation
Database APIs
Entity
Entity
Entity
The principles of clean architecture

19. Presentation
Layer
Model
View
Presenter
Domain
Layer
Regular java
objects
Data
Layer
Repository Pattern
Interactors
Boundaries

20. Presentation
Layer
Model
View
Presenter
Domain
Layer
Regular java
objects
Data
Layer
Repository Pattern
Interactors
Boundaries

21. RepositoryInterface
Repository
Implementation
getUserById()
getAllUsers()
getUserByName() cloud
database

22. A glimpse about Repository Pattern
* It contains some business rules
* Should be named after an object that holds its content
moneyRepository
documentsRepository
cardsRepository
wallet
getMoney
getDocuments
getCards

23. Presentation
Layer
Model
View
Presenter
Domain
Layer
Regular java
objects
Data
Layer
Repository Pattern
Interactors
Boundaries

24. House Entity
House

25. Presentation
Layer
Model
View
Presenter
Domain
Layer
Regular java
objects
Data
Layer
Repository Pattern
Interactors
Boundaries

26. Presenter
showLoading
renderUserList
hideLoading
user 1
user 2
user 3
user 4
user 5
user 6
user 7
user 8
user 9

27. Reactive Approach
View
Presenter
Domain Use Case
Repository
Subscriber<T>
Stream

28. Our Case
https://pokeapi.co/
* list all pokemons
* show some details of the chosen pokemon

29. You’ve already seen it?
probably all logic from our app
api entities been used everywhere
two package containing view level
wtf?

30. What we want
presenter domain data

31. Fragment
presenter domain data
pokemonListFragment

32. Interface with view methods
presenter domain data
pokemonListFragment
listPokemonView

33. Presenter with fragment logic
presenter domain data
pokemonListFragment
listPokemonView
pokemonListPresenter

34. Case with business logic
presenter domain data
pokemonListFragment
listPokemonView
pokemonListPresenter
pokemonListCase
pokemonListRequest

35. Case interface with data connection
presenter domain data
pokemonListFragment
listPokemonView
pokemonListPresenter
pokemonListCase
pokemonListRequest
pokemonCase

36. Repository
presenter domain data
pokemonListFragment
listPokemonView
pokemonListPresenter
pokemonListCase
pokemonListRequest
pokemonCase
pokedex

37. Rest API
presenter domain data
pokemonListFragment
listPokemonView
pokemonListPresenter
pokemonListCase
pokemonListRequest
pokemonCase
pokedex
pokemonApi

38. Mapper from data object to business
object
presenter domain data
pokemonListFragment
listPokemonView
pokemonListPresenter
pokemonListCase
pokemonListRequest
pokemonCase
pokedex
pokemonApi
pokemonEntityMapper

39. Response from our request
presenter domain data
pokemonListFragment
listPokemonView
pokemonListPresenter
pokemonListCase
pokemonListRequest
pokemonCase
pokedex
pokemonApi
pokemonEntityMapper
pokemonListResponse

40. Mapper from business object to request
model
presenter domain data
pokemonListFragment
listPokemonView
pokemonListPresenter
pokemonListCase
pokemonListRequest
pokemonCase
pokedex
pokemonApi
pokemonEntityMapper
pokemonListResponse
pokemonModelMapper

41. Zero to hero
now after
"By the Flames of the Faltine!"

42. Why should I care?
* Makes changes less impactful
* Easier to change the project
* Increase productivity with multiple people
* Enhance test environment