RubyLichtenstein/Dogiz

This system is an Android application for browsing and managing dog breed information and images. It provides features to view breed details, browse associated images, and save favorites. The architecture is modularized into domain, data, and UI layers, utilizing modern Android development practices like Jetpack Compose and Hilt.

Introduced new domain-layer components to support image browsing and favorites functionality. This includes the DogImage data class and ImagesRepository interface for fetching images by breed, as well as FavoritesRepository and associated use cases (GetFavoriteImagesUseCase, ToggleFavoriteUseCase) to manage user favorites.

domain/src/main/java/com/rubylichtenstein/domain/images · high confidence

The repository is initialized with the core application code, including a detailed README and blog post describing the app's architecture (Clean Architecture, Hilt, Jetpack Compose, etc.), alongside a MIT license file and a Gradle script for JaCoCo code coverage reporting.

(repo-wide) · high confidence

The application now includes a new domain layer for handling dog breed data. This introduces a data model (BreedEntity) and a use case (GetBreedsUseCase) that fetches breed information and formats it for display, including capitalization and sub-breed grouping. The repository interface and data models (BreedInfo) are also added to this layer. Additionally, a shared string extension for capitalizing words has been moved to the domain package.

domain/src/main/java/com/rubylichtenstein/domain/breeds · medium confidence

The application's Java/Kotlin package name has been changed from 'dk.shape.dogbreeds' to 'com.rubylichtenstein.dogbreeds'. This change includes renaming the main application class, the main activity, and the associated unit and instrumented tests to reflect the new package structure. Additionally, the 'MainActivity' has been simplified by removing the 'DogBreedsTheme' wrapper and directly rendering the 'AppNavigator'.

app/src · high confidence

The data layer has been reorganized under the new \com.rubylichtenstein.data\ package, moving classes such as \KtorHttpClient\ (formerly \MyHttpClient\), \BreedsApi\ (now \BreedImagesApi\), and repository implementations to their respective sub-packages (e.g., \breeds\, \images\, \favorites\). The \KtorHttpClient\ implementation was simplified to return raw response objects directly instead of wrapping them in a custom \ApiResponse\ sealed class, and the \DataModule\ was updated to provide these new implementations. Additionally, new unit tests were added for \ImagesRepositoryImpl\ to verify the local/remote data fetching logic.

data · high confidence

The UI module was restructured, moving all UI components from the app module to the ui module under the package com.rubylichtenstein.ui. This includes a new UiState sealed interface for managing loading, success, error, and empty states, replacing the previous AsyncState. The Favorites screen now uses a Molecule-based ViewModel (MoleculeViewModel) to handle state and events, introducing a FavoritesPresenter for UI logic. The BreedsScreen was updated to use the new UiState and UiStateWrapper, and the app's navigation and theming (DogBreedsTheme with light/dark color schemes) were integrated into the ui module. Additionally, a DogImage composable was created for image loading, and tests were added for the new state management and presenter.

ui · medium confidence

Added unit tests for the domain layer, including test cases for the GetBreedsUseCase, string extension functions, and the favorite and image-related use cases (GetFavoriteImagesUseCase, ToggleFavoriteUseCase, GetBreedImagesUseCase) along with their corresponding fake repositories.

domain/src/test · high confidence

The project has been refactored from a single-module structure into a multi-module architecture consisting of :domain, :data, and :ui modules. The :app module now depends on these new modules, while the :domain module provides shared business logic, :data handles data layer concerns, and :ui manages the user interface. This change also introduces KSP for annotation processing (replacing Kapt for Hilt) and updates various dependency versions, including JUnit 5.10.0, Coroutines 1.7.2, and Hilt 2.47.

(dependencies) · high confidence

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

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

• Code Health 100 → 100 (+0.0)
• Architecture 96 → 86 (-10.5)
• Maturity 55 → 55 (+0.0)
• Readiness 57 → 57 (+0.0)
• Security 80 → 88 (+8.1)
• Domain Modelling 100 → 70 (-30.3)

• Change coupling: BreedsScreen.kt ↔ ImagesGrid.kt (ui/src/main/java/com/rubylichtenstein/ui/breeds/BreedsScreen.kt)
• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• No exposed public API
• Test reliability not included
• single-maintainer — knowledge-concentration (bus factor) risk

• Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
• Documentation: no contributor guidance (README.md)
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• Medium: security finding (details withheld)
• Medium: security finding (details withheld)
• No ADRs found
• No dependency advisory monitoring
• Workflow token permissions not restricted

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

RubyLichtenstein/Dogiz 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.