jshvarts/MosbyMVI

This system is an Android application development framework that implements the Model-View-Intent (MVI) architecture pattern. It provides a complete, functional example of this pattern, including data repositories, use cases, and UI components for handling states and interactions. The project also includes build configuration refactoring and static code analysis tools to support development.

The app now includes a complete MVI (Model-View-Intent) demo application. This introduces a new main activity and presenter that handle button clicks, display loading states, and render greeting text using RxJava observables. The change also adds supporting components including a view extension for visibility, a domain use case, a data repository, and a sealed class for view states, effectively providing a functional 'Hello World' example of the MVI pattern.

app/src · high confidence

The 'Hello World' demo application and its associated common modules have been removed. This includes the deletion of the \GreetingRepository\, \NotesRepository\, \GetGreetingUseCase\, \GetNotesUseCase\, \NoteEntity\, and \MainActivity\ from the \common\ and \hello-world\ directories. Consequently, the app no longer provides the basic MVI (Model-View-Intent) example that previously displayed a greeting and a list of notes.

common, hello-world · high confidence

The project build configuration has been refactored to replace the centralized 'libs' map in the root build.gradle with explicit version variables and direct dependency declarations in the app module. This includes updating RxJava, RxAndroid, Timber, and RxBinding versions, and removing the Butterknife dependency in favor of RxBinding. Additionally, the 'common' module has been removed from the build, and the 'hello-world' module has been renamed to 'app'. A new Detekt static analysis plugin (version 1.0.0.RC6) has been integrated into the build process.

(dependencies) · medium confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 63 → 56 (-6.7)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 100 (+0.0)
• Architecture 100 → 94 (-6.1)
• Maturity 59 → 59 (+0.0)
• Readiness 44 → 31 (-12.3)
• Security 100 → 100 (+0.0)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• No architecture or usage documentation for Mosby integration.
• No exposed public API
• Test reliability not included
• The README explains what MVI is but does not describe the project structure or how to add Mosby dependencies. (README.md)
• early-stage repository — too little history to judge knowledge freshness
• git history depth insufficient
• git history depth insufficient
• single-maintainer — knowledge-concentration (bus factor) risk

• Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• No ADRs found
• No dependency advisory monitoring

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

jshvarts/MosbyMVI 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 a surveyor at a repository you know and see whether you agree with it.