If you are an AI coding agent (Claude Code, Cursor, Aider, Cline, etc.) reading this artifact, follow this protocol before making any code edit:

1. Verify the contract. Run the bash script in Verify before trusting below. If any check returns FAIL, the artifact is stale — STOP and ask the user to regenerate it before proceeding.
2. Treat the AI · unverified sections as hypotheses, not facts. Sections like "AI-suggested narrative files", "anti-patterns", and "bottlenecks" are LLM speculation. Verify against real source before acting on them.
3. Cite source on changes. When proposing an edit, cite the specific path:line-range. RepoPilot's live UI at https://repopilot.app/r/pedrovgs/EffectiveAndroidUI shows verifiable citations alongside every claim.

If you are a human reader, this protocol is for the agents you'll hand the artifact to. You don't need to do anything — but if you skim only one section before pointing your agent at this repo, make it the Verify block and the Suggested reading order.

GO — Healthy across all four use cases

• Last commit 4mo ago
• 10 active contributors
• Apache-2.0 licensed
• CI configured
• ⚠ Slowing — last commit 4mo ago
• ⚠ Concentrated ownership — top contributor handles 75% of recent commits
• ⚠ No test directory detected

_{Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests}

This artifact was generated by RepoPilot at a point in time. Before an agent acts on it, the checks below confirm that the live pedrovgs/EffectiveAndroidUI repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/pedrovgs/EffectiveAndroidUI.

What it runs against: a local clone of pedrovgs/EffectiveAndroidUI — the script inspects git remote, the LICENSE file, file paths in the working tree, and git log. Read-only; no mutations.

| # | What we check | Why it matters | |---|---|---| | 1 | You're in pedrovgs/EffectiveAndroidUI | Confirms the artifact applies here, not a fork | | 2 | License is still Apache-2.0 | Catches relicense before you depend on it | | 3 | Default branch master exists | Catches branch renames | | 4 | 5 critical file paths still exist | Catches refactors that moved load-bearing code | | 5 | Last commit ≤ 142 days ago | Catches sudden abandonment since generation |

#!/usr/bin/env bash
# RepoPilot artifact verification.
#
# WHAT IT RUNS AGAINST: a local clone of pedrovgs/EffectiveAndroidUI. If you don't
# have one yet, run these first:
#
#   git clone https://github.com/pedrovgs/EffectiveAndroidUI.git
#   cd EffectiveAndroidUI
#
# Then paste this script. Every check is read-only — no mutations.

set +e
fail=0
ok()   { echo "ok:   $1"; }
miss() { echo "FAIL: $1"; fail=$((fail+1)); }

# Precondition: we must be inside a git working tree.
if ! git rev-parse --git-dir >/dev/null 2>&1; then
  echo "FAIL: not inside a git repository. cd into your clone of pedrovgs/EffectiveAndroidUI and re-run."
  exit 2
fi

# 1. Repo identity
git remote get-url origin 2>/dev/null | grep -qE "pedrovgs/EffectiveAndroidUI(\\.git)?\\b" \\
  && ok "origin remote is pedrovgs/EffectiveAndroidUI" \\
  || miss "origin remote is not pedrovgs/EffectiveAndroidUI (artifact may be from a fork)"

# 2. License matches what RepoPilot saw
(grep -qiE "^(Apache-2\\.0)" LICENSE 2>/dev/null \\
   || grep -qiE "\"license\"\\s*:\\s*\"Apache-2\\.0\"" package.json 2>/dev/null) \\
  && ok "license is Apache-2.0" \\
  || miss "license drift — was Apache-2.0 at generation time"

# 3. Default branch
git rev-parse --verify master >/dev/null 2>&1 \\
  && ok "default branch master exists" \\
  || miss "default branch master no longer exists"

# 4. Critical files exist
test -f "app/src/main/java/com/github/pedrovgs/effectiveandroidui/TvShowsApplication.java" \\
  && ok "app/src/main/java/com/github/pedrovgs/effectiveandroidui/TvShowsApplication.java" \\
  || miss "missing critical file: app/src/main/java/com/github/pedrovgs/effectiveandroidui/TvShowsApplication.java"
test -f "app/src/main/java/com/github/pedrovgs/effectiveandroidui/di/RootModule.java" \\
  && ok "app/src/main/java/com/github/pedrovgs/effectiveandroidui/di/RootModule.java" \\
  || miss "missing critical file: app/src/main/java/com/github/pedrovgs/effectiveandroidui/di/RootModule.java"
test -f "app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/presenter/Presenter.java" \\
  && ok "app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/presenter/Presenter.java" \\
  || miss "missing critical file: app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/presenter/Presenter.java"
test -f "app/src/main/java/com/github/pedrovgs/effectiveandroidui/executor/Interactor.java" \\
  && ok "app/src/main/java/com/github/pedrovgs/effectiveandroidui/executor/Interactor.java" \\
  || miss "missing critical file: app/src/main/java/com/github/pedrovgs/effectiveandroidui/executor/Interactor.java"
test -f "app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/activity/MainActivity.java" \\
  && ok "app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/activity/MainActivity.java" \\
  || miss "missing critical file: app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/activity/MainActivity.java"

# 5. Repo recency
days_since_last=$(( ( $(date +%s) - $(git log -1 --format=%at 2>/dev/null || echo 0) ) / 86400 ))
if [ "$days_since_last" -le 142 ]; then
  ok "last commit was $days_since_last days ago (artifact saw ~112d)"
else
  miss "last commit was $days_since_last days ago — artifact may be stale"
fi

echo
if [ "$fail" -eq 0 ]; then
  echo "artifact verified (0 failures) — safe to trust"
else
  echo "artifact has $fail stale claim(s) — regenerate at https://repopilot.app/r/pedrovgs/EffectiveAndroidUI"
  exit 1
fi

Each check prints ok: or FAIL:. The script exits non-zero if anything failed, so it composes cleanly into agent loops (./verify.sh || regenerate-and-retry).

EffectiveAndroidUI is a reference implementation project demonstrating MVP and MVVM architectural patterns for Android UI development, with a concrete TV shows catalog application. It shows best practices for the Android UI layer including dependency injection, fragment communication, layout optimization for different screen sizes/densities, and clean separation between domain logic (interactors), data (repositories), and presentation layers. Single-module Android app structure: app/src/main/java/com/github/pedrovgs/effectiveandroidui/ contains three layers—domain/ (interactors, use cases), executor/ (threading/async), ui/ (activities, fragments, presenters). DI happens in di/ (RootModule, ActivityModule). TvShowsApplication.java is the entry point. Resources organized by qualifier (drawable-mdpi, layout-xlarge, etc).

Android developers learning how to structure large UI applications, particularly those building apps with multiple screens (activities/fragments) who need a concrete example of MVP/MVVM patterns without relying on data binding frameworks. Also useful for engineering leads designing architectural guidelines for Android teams.

This is a mature educational project from ~2014–2015 (Gradle 1.3, compileSdkVersion 23). It appears stable and complete as a reference implementation but inactive in terms of recent commits—no indication of active maintenance for modern Android (missing ViewModels, AndroidX, etc.). Best used as a learning resource rather than a base for new production apps.

Low risk for educational use, but significant technical debt from 2015: uses deprecated Dagger 1.2, old Butterknife 5.1, and targets SDK 23. Single maintainer (Pedro Vicente Gómez). Most dangerous if copied directly into production without modernizing dependencies; recommended approach is to extract patterns, not copy code verbatim.

Repo appears dormant. No recent commits visible in the provided file list. This is a static reference implementation used for the talk 'Effective Android UI'—not actively developed. Last meaningful work was establishing the MVP/MVVM samples and speaker materials.

git clone https://github.com/pedrovgs/EffectiveAndroidUI.git
cd EffectiveAndroidUI
# Requires Android SDK 23+ and Gradle 1.3+ (or wrapper)
./gradlew assembleDebug
# Then open in Android Studio or deploy to emulator/device
adb install app/build/outputs/apk/app-debug.apk

Daily commands: Import into Android Studio → sync Gradle → run app (Ctrl+R or green play button). Builds to app/build/outputs/apk/app-debug.apk. Minimum SDK 8, targets SDK 23.

• app/src/main/java/com/github/pedrovgs/effectiveandroidui/TvShowsApplication.java — Application entry point and Dagger component initialization—all dependency injection starts here.
• app/src/main/java/com/github/pedrovgs/effectiveandroidui/di/RootModule.java — Root Dagger module that configures the primary dependency graph for the entire application.
• app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/presenter/Presenter.java — Base presenter interface defining the MVP/MVVM lifecycle contract that all presenters implement.
• app/src/main/java/com/github/pedrovgs/effectiveandroidui/executor/Interactor.java — Domain layer contract for use cases; all business logic execution flows through interactor implementations.
• app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/activity/MainActivity.java — Primary Activity and navigation hub showing how fragments are managed and presenters are wired.
• app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/renderer/tvshow/TvShowRenderer.java — Renderer pattern implementation demonstrating how to decouple view rendering from data models.
• app/build.gradle — Build configuration with Dagger, Butterknife, and quality plugins; defines compile and runtime dependencies.

Add a New TV Show Use Case

1. Create a new Interactor interface in domain layer extending GetTvShows or GetTvShowById pattern. (app/src/main/java/com/github/pedrovgs/effectiveandroidui/domain/GetTvShowsInteractor.java)
2. Implement the interactor with business logic, calling repository and converting to domain entities. (app/src/main/java/com/github/pedrovgs/effectiveandroidui/domain/GetTvShowByIdInteractor.java)
3. Register the new interactor in TvShowsModule with proper Dagger bindings. (app/src/main/java/com/github/pedrovgs/effectiveandroidui/domain/TvShowsModule.java)
4. Create a Presenter (e.g., TvShowCatalogPresenter) that receives the interactor via constructor injection. (app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/presenter/TvShowCatalogPresenter.java)
5. Register presenter in TvShowUIModule and wire into Activity/Fragment via ActivityModule. (app/src/main/java/com/github/pedrovgs/effectiveandroidui/di/ActivityModule.java)

Add a New UI Screen with MVP

1. Create Fragment extending BaseFragment (e.g., TvShowCatalogFragment) with view references. (app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/fragment/TvShowCatalogFragment.java)
2. Create Presenter class (e.g., TvShowCatalogPresenter) injecting interactor and implementing presenter lifecycle. (app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/presenter/TvShowCatalogPresenter.java)
3. Implement View interface in Fragment to receive callbacks from Presenter (e.g., showLoading, showTvShows). (app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/fragment/TvShowCatalogFragment.java)
4. Create or reuse Renderer/ViewModel to convert domain models to UI state. (app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/renderer/tvshow/TvShowRenderer.java)
5. Register fragment factory and presenter in ActivityModule for dependency resolution. (app/src/main/java/com/github/pedrovgs/effectiveandroidui/di/ActivityModule.java)

Add a New Renderer for Custom View Binding

1. Create a Renderer class (e.g., ChapterRenderer) with render(model, parent) method inflating and binding views. (app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/renderer/chapter/ChapterRenderer.java)
2. Create a RendererAdapterFactory (e.g., ChapterRendererAdapterFactory) to produce adapters for list views. (app/src/main/java/com/github/pedrovgs/effectiveandroidui/ui/renderer/chapter/ChapterRendererAdapterFactory.java)
3. Define layout XML (e.g., row_chapter.xml) and wire findViewById() calls in renderer render() method

Dagger 1.2 differences: Uses @Inject constructor annotation and @Module classes differently than Dagger 2+; won't compile with modern Dagger without refactoring. ProGuard config: app/proguard-rules.txt must be kept in sync if you add/remove libraries, especially for Dagger. Resource qualifiers are strict: Layouts under res/layout-xlarge/ only load on XL tablets; similar rules for -mdpi, -v16, etc.—easy to break with wrong naming. API level 8 minimum: Some modern Android patterns (Fragments, ViewPager) behave unexpectedly on older APIs; test on emulator API 8 if you need backward compatibility. Butterknife 5.1 caveat: Deprecated in favor of view binding; manual unbind in onDestroyView is required to avoid leaks.

• Model-View-Presenter (MVP) — Core architectural pattern in this repo; the Presenter receives user events from Views (Fragments) and delegates to domain logic (Interactors), keeping UI decoupled from business rules.
• Model-View-ViewModel (MVVM) — This repo shows MVVM without data binding (via LiveData or RxJava), proving you can separate concerns without framework magic—useful for understanding what binding libraries automate.
• Dependency Injection via Constructor — Dagger 1.2 in this project injects Presenters, Interactors, and Executors into Activities/Fragments; essential for testing and avoiding tight coupling to framework classes.
• Use Cases / Interactors — The GetTvShowsInteractor and GetTvShowByIdInteractor pattern isolates business logic from Android lifecycle; allows offline-first, testable, framework-agnostic domain code.
• Android Resource Qualifiers — This repo heavily uses layout-xlarge, drawable-mdpi, and values-v16 folders to provide different resources per screen size/density—critical for responsive multi-device Android apps.
• Fragment Communication via Interfaces — The project shows how Fragments communicate with Activities via callback interfaces rather than direct references, reducing coupling and enabling re-use in different Activity contexts.
• ThreadExecutor Pattern — Rather than hard-coding Thread pools in domain logic, this repo abstracts async execution via an Executor interface; allows swapping implementations for testing (synchronous) vs. production (background thread).

• googlesamples/android-architecture — Google's official reference project showing TODO-MVC in MVP, MVVM, and other patterns—the modern successor to EffectiveAndroidUI with up-to-date libraries.
• square/dagger — The Dagger DI framework used in this project; understanding Dagger internals helps debug module wiring and scoping issues in EffectiveAndroidUI.
• JakeWharton/butterknife — The view binding library (v5.1) used throughout the UI layer; source code shows how @BindView annotations work under the hood.
• pedrovgs/Renderers — Companion library (external dependency of this project) that provides a clean pattern for complex ListView/RecyclerView rendering—used in the TV shows catalog.
• pedrovgs/DraggablePanel — Custom UI component library (external dependency) that provides the draggable panel shown in the screenshots—example of reusable custom view packaging.

To work on one of these in Claude Code or Cursor, paste: Implement the "<title>" PR idea from CLAUDE.md, working through the checklist as the task list.

Migrate Dagger 1.2.x to Dagger 2.x with modern dependency injection patterns

The project uses deprecated Dagger 1.2.x (from 2015). Migrating to Dagger 2.x would modernize the DI setup, improve compile-time safety, reduce runtime reflection overhead, and align with current Android best practices. This is particularly valuable since the repo is a teaching tool for 'Effective Android UI' - it should model current best practices. The migration would affect di/ActivityModule.java, di/RootModule.java, domain/TvShowsModule.java, executor/ExecutorModule.java, and ui/presenter/TvShowUIModule.java.

• [ ] Update build.gradle to replace 'com.squareup.dagger:dagger:1.2.+' with Dagger 2.x artifacts and add annotation processor plugin
• [ ] Convert di/RootModule.java, di/ActivityModule.java, domain/TvShowsModule.java, executor/ExecutorModule.java, and ui/presenter/TvShowUIModule.java to use @Module, @Provides, @Component, @Inject annotations per Dagger 2 syntax
• [ ] Update TvShowsApplication.java to use ObjectGraph replacement (e.g., ApplicationComponent with inject() methods)
• [ ] Update BaseActivity.java and BaseFragment.java to use constructor/field injection compatible with Dagger 2
• [ ] Add unit tests in a new test/ directory for dependency graph validation using Dagger 2's component testing

Add comprehensive unit tests for Presenters and Interactors

The repository lacks visible test coverage for core business logic. Given this is an educational project on 'Effective Android UI', it should demonstrate testing patterns. Adding unit tests for TvShowCatalogPresenter.java, TvShowPresenter.java, GetTvShowsInteractor.java, and GetTvShowByIdInteractor.java would show how to test presentation layer logic and domain layer interactions, which is critical for maintainable Android applications.

• [ ] Create app/src/test/java directory structure mirroring source packages
• [ ] Add unit tests for GetTvShowsInteractor.java and GetTvShowByIdInteractor.java testing execution, callbacks, and error handling
• [ ] Add unit tests for TvShowCatalogPresenter.java testing view updates, interactor interactions, and lifecycle management
• [ ] Add unit tests for TvShowPresenter.java following the same patterns
• [ ] Include tests for TvShowNotFoundException.java exception handling scenarios
• [ ] Add build.gradle test dependencies (JUnit 4, Mockito) and update CI (.travis.yml) to run tests

Update build.gradle for modern Android development and resolve deprecated dependencies

The build.gradle uses outdated tools (gradle plugin 1.3.0 from 2015, support libraries 23.0.1, ButterKnife 5.1.x, Picasso 2.3.x). This educational repo should reflect current Android development practices. Updating to modern gradle plugin, AndroidX, current library versions, and adding security/code quality improvements would make it a more valuable learning resource. Target Android SDK should also be updated from API 23.

• [ ] Update gradle plugin from 1.3.0 to latest stable (9.x), compileSdkVersion from 23 to 35, targetSdkVersion from 23 to 35
• [ ] Replace 'com.android.support' libraries with AndroidX equivalents (androidx.appcompat:appcompat, androidx.fragment:fragment)
• [ ] Update ButterKnife from 5.1.x to 10.2.x and update all @Bind annotations to @BindView
• [ ] Update Picasso from 2.3.x to 2.8x, Dagger to 2.x (integrates with first PR), and renderers library to latest compatible version
• [ ] Remove deprecated 'sonar

• Add unit tests for GetTvShowsInteractor.java and GetTvShowByIdInteractor.java to verify callback behavior and error handling—currently no test files visible in the repo structure.
• Modernize Dagger from 1.2 to 2.x in di/RootModule.java and di/ActivityModule.java, including updating @Module syntax and scopes to use @Singleton/@ActivityScope properly.
• Add a README.md or docs/ section explaining the difference between the MVP sample (TvShowCatalogFragment + TvShowCatalogPresenter) and MVVM sample (likely TvShowFragment + TvShowPresenter)—currently unclear which is which.

• High · Outdated Gradle Build Tool — build.gradle - buildscript dependencies. The project uses Gradle 1.3.0 which was released in 2014 and contains multiple known security vulnerabilities. This version lacks security patches and modern security features. Fix: Update to the latest stable Gradle version (currently 8.x). Use gradle:gradle-8.0 or later in classpath.
• High · Outdated Android Gradle Plugin — build.gradle - buildscript dependencies. Android Gradle Plugin 1.3.0 is from 2015 and contains known vulnerabilities. It lacks modern security checks and dependency validation features. Fix: Update com.android.tools.build:gradle to version 8.0 or later to receive security patches and modern dependency management.
• High · Outdated Support Libraries — build.gradle - dependencies (appcompat-v7, support-v4). Android Support Library 23.0.1 (from 2015) is outdated and no longer receives security updates. AndroidX should be used instead. Fix: Migrate to AndroidX libraries: androidx.appcompat:appcompat:1.6.1 and androidx.legacy:legacy-support-v4:1.0.0
• High · Outdated Dagger Dependency Injection — build.gradle - dependencies (dagger, dagger-compiler). Dagger 1.2.x is from 2013 and is deprecated. Dagger 2.x introduced major security improvements and better lifecycle management. Fix: Upgrade to Dagger 2.x (currently 2.48.1). This requires code refactoring but provides critical security improvements.
• High · Outdated ButterKnife Library — build.gradle - dependencies. ButterKnife 5.1.x is from 2014 and no longer maintained. Modern view binding solutions are more secure. Fix: Replace with Android View Binding (com.android.tools.build:gradle 4.1.0+) or migrate to Jetpack Compose.
• High · Outdated Picasso Image Loading — build.gradle - dependencies. Picasso 2.3.x lacks modern security features for image validation and caching. No longer actively maintained. Fix: Upgrade to Coil (io.coil-kt:coil:2.4.0) or Glide (com.github.bumptech.glide:glide:4.16.0) for modern security features.
• Medium · Overly Permissive Minimum SDK — build.gradle - defaultConfig. minSdkVersion 8 (Android 2.2, from 2010) is extremely outdated. Supporting such old versions limits modern security features and SSL/TLS capabilities. Fix: Update minSdkVersion to at least 21 (Android 5.0). Consider targeting 26+ for improved security.
• Medium · Missing ProGuard/R8 Configuration Details — app/proguard-rules.txt. While proguard-rules.txt exists, the content is not provided. Ensure proper code obfuscation is configured to protect against reverse engineering. Fix: Verify ProGuard rules include minification, obfuscation, and optimization. Use R8 with modern Gradle versions.
• Medium · Missing Network Security Configuration — app/src/main/res/. No network_security_config.xml visible in resources. This could allow unencrypted traffic or certificate pinning bypass attacks. Fix: Create network_security_config.xml to enforce HTTPS-only, configure certificate pins for API endpoints, and disable cleartext traffic.
• Medium · No Evidence of Input Validation — app/src/main/java/com/github/pedrovgs/effectiveandroidui/domain/tvshow. The codebase structure shows data processing (TvShow, Chapter models) but no visible input validation or sanitization mechanisms. Fix: undefined

LLM-derived; treat as a starting point, not a security audit.

• Open issues — current backlog
• Recent PRs — what's actively shipping
• Source on GitHub

Generated by RepoPilot. Verdict based on maintenance signals — see the live page for receipts. Re-run on a new commit to refresh.