Ezike/StarWarsSearch-MVI
This is an Android application for browsing and searching Star Wars character data, featuring a clean architecture with separate layers for presentation, domain, and data. The system implements a state-driven UI using a state machine pattern and Hilt for dependency injection, supporting offline caching and remote data fetching. It includes reusable core components, test utilities, and a centralized navigation module to manage screen transitions.
47.5
Weak · 3 August 2026
3.4k
lines of production code
Kotlin
primary language
2
bus factor · 6 authors in all
3
measurements over time
How it got here
2020 · Architecture and build system initialization
The project was initialized with a Clean Architecture and MVI pattern, supported by a comprehensive Gradle build system migration to Kotlin DSL. This period established the foundational infrastructure, including Hilt dependency injection, state management components, and modular library structures for caching, remote data, and testing utilities.
18 changes
2021–2022 · architecture modularization and feature expansion
This period focused on restructuring the application's architecture by introducing dedicated modules for navigation, caching, and remote data handling. It also expanded the user interface with a new character detail screen, supported by new data models and automated development tooling.
5 changes
Survey your own repository
Ezike/StarWarsSearch-MVI 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 3 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit f091dc9b19 — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.