android10/Android-CleanArchitecture
This is an Android application built on Clean Architecture principles, structured into distinct data, domain, and presentation layers. The system manages user data through a reactive programming model using RxJava, handling asynchronous operations, caching, and background execution. It employs the MVP architectural pattern for the UI and utilizes Dagger2 for dependency injection, with comprehensive unit testing covering the domain and data layers.
60.4
Adequate · 20 July 2026
3.3k
lines of production code
Java
primary language
1
bus factor · 12 authors in all
2
measurements over time
How it got here
2014 · Clean Architecture implementation
The project was established with a complete Clean Architecture, introducing distinct presentation, domain, and data layers. This included implementing MVP, reactive streams with RxJava, and dependency injection to structure the codebase.
10 changes
2015 · RxJava 2 migration and test coverage
The project migrated its domain layer's use cases to RxJava 2, introducing a reactive approach with Observables and Schedulers. This period also focused on increasing test coverage by adding unit tests for the DefaultErrorBundle and the newly refactored interactor use cases.
4 changes
Survey your own repository
android10/Android-CleanArchitecture was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 20 July 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 8ed4222c53 — the exact code this score is about.
- Scored under rubric rubric-2026.08.17. Score the same commit under that rubric and you get the same number.