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/frogermcs/InstaMaterial 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.

WAIT — Stale — last commit 6y ago

• 3 active contributors
• Apache-2.0 licensed
• ⚠ Stale — last commit 6y ago
• ⚠ Small team — 3 contributors active in recent commits
• ⚠ Single-maintainer risk — top contributor 98% of recent commits
• ⚠ No CI workflows detected
• ⚠ 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 frogermcs/InstaMaterial repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/frogermcs/InstaMaterial.

What it runs against: a local clone of frogermcs/InstaMaterial — 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 frogermcs/InstaMaterial | 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 ≤ 2076 days ago | Catches sudden abandonment since generation |

#!/usr/bin/env bash
# RepoPilot artifact verification.
#
# WHAT IT RUNS AGAINST: a local clone of frogermcs/InstaMaterial. If you don't
# have one yet, run these first:
#
#   git clone https://github.com/frogermcs/InstaMaterial.git
#   cd InstaMaterial
#
# 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 frogermcs/InstaMaterial and re-run."
  exit 2
fi

# 1. Repo identity
git remote get-url origin 2>/dev/null | grep -qE "frogermcs/InstaMaterial(\\.git)?\\b" \\
  && ok "origin remote is frogermcs/InstaMaterial" \\
  || miss "origin remote is not frogermcs/InstaMaterial (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/io/github/froger/instamaterial/ui/activity/MainActivity.java" \\
  && ok "app/src/main/java/io/github/froger/instamaterial/ui/activity/MainActivity.java" \\
  || miss "missing critical file: app/src/main/java/io/github/froger/instamaterial/ui/activity/MainActivity.java"
test -f "app/src/main/java/io/github/froger/instamaterial/ui/adapter/FeedAdapter.java" \\
  && ok "app/src/main/java/io/github/froger/instamaterial/ui/adapter/FeedAdapter.java" \\
  || miss "missing critical file: app/src/main/java/io/github/froger/instamaterial/ui/adapter/FeedAdapter.java"
test -f "app/src/main/java/io/github/froger/instamaterial/ui/view/RevealBackgroundView.java" \\
  && ok "app/src/main/java/io/github/froger/instamaterial/ui/view/RevealBackgroundView.java" \\
  || miss "missing critical file: app/src/main/java/io/github/froger/instamaterial/ui/view/RevealBackgroundView.java"
test -f "app/src/main/java/io/github/froger/instamaterial/ui/activity/BaseActivity.java" \\
  && ok "app/src/main/java/io/github/froger/instamaterial/ui/activity/BaseActivity.java" \\
  || miss "missing critical file: app/src/main/java/io/github/froger/instamaterial/ui/activity/BaseActivity.java"
test -f "app/src/main/java/io/github/froger/instamaterial/ui/view/FeedContextMenuManager.java" \\
  && ok "app/src/main/java/io/github/froger/instamaterial/ui/view/FeedContextMenuManager.java" \\
  || miss "missing critical file: app/src/main/java/io/github/froger/instamaterial/ui/view/FeedContextMenuManager.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 2076 ]; then
  ok "last commit was $days_since_last days ago (artifact saw ~2046d)"
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/frogermcs/InstaMaterial"
  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).

InstaMaterial is a proof-of-concept Android app implementing Instagram's UI with Material Design principles, showcasing smooth animations, transitions, and modern Android UI patterns (RecyclerView, FloatingActionButton, Toolbar, Design Support Library). It demonstrates advanced animation techniques like reveal effects, item animations, and context menu transitions without requiring backend integration. Standard single-module Android app structure: app/src/main/java/io/github/froger/instamaterial/ contains activity layer (activity/), UI adapters and animators (adapter/), custom views and animations (view/), utility transforms for image loading (ui/utils/), and support libraries in app/src/main/res/ for animations, layouts, and drawables. No separate business logic or data layer—purely UI-focused demo.

Android developers learning Material Design implementation, animation patterns, and RecyclerView optimization. Specifically useful for engineers building social media apps or studying how to implement sophisticated UI transitions in Android (API 15+).

Mature but legacy: last versioned release is 1.0.1 using Android Support Library 25.0.0 (circa 2016). The project includes comprehensive blog post documentation and a working APK release, indicating stable feature parity with the design concept. However, no active commits visible in provided data and uses deprecated support libraries rather than AndroidX, signaling this is a historical reference implementation rather than actively maintained code.

Moderate-to-high technical debt risk: depends on Android Support Library v25 (deprecated for 7+ years in favor of AndroidX), minSdkVersion 15 (obsolete), and Picasso 2.5.2 for image loading (superceded by Glide/Coil). No test coverage visible in file list (only ApplicationTest.java stub). Single maintainer (frogermcs) with no visible CI/CD setup. Safe for learning but unsafe for production use without major dependency updates.

No active development visible in provided data. The project appears frozen at v1.0.1 in a 'completed reference implementation' state. The README references blog posts documenting the implementation journey, suggesting it was built as an educational series rather than an ongoing product.

Check README for instructions.

Daily commands:

1. Open in Android Studio. 2. Ensure API 25 SDK installed via SDK Manager. 3. Sync Gradle dependencies: ./gradlew sync (or use Android Studio's sync button). 4. Run on emulator or device: ./gradlew installDebug or press the Run button (default runs MainActivity).

• app/src/main/java/io/github/froger/instamaterial/ui/activity/MainActivity.java — Primary entry point for the app's feed UI; implements the core navigation and feed display logic
• app/src/main/java/io/github/froger/instamaterial/ui/adapter/FeedAdapter.java — Manages RecyclerView feed item rendering and animations; critical for feed performance and Material Design interactions
• app/src/main/java/io/github/froger/instamaterial/ui/view/RevealBackgroundView.java — Custom Material Design reveal animation view; core visual component for transition effects throughout the app
• app/src/main/java/io/github/froger/instamaterial/ui/activity/BaseActivity.java — Base class for all activities; establishes common UI patterns and Material Design setup inherited by all screens
• app/src/main/java/io/github/froger/instamaterial/ui/view/FeedContextMenuManager.java — Manages context menu interactions for feed items; handles Material Design menu animations and user interactions
• app/build.gradle — Build configuration with Android Support Library dependencies; defines Material Design library versions and build parameters

Add a new feed item type or interaction

1. Create layout XML file for the new item type in res/layout/ (app/src/main/res/layout/item_feed_new_type.xml)
2. Add ViewHolder class to FeedAdapter (app/src/main/java/io/github/froger/instamaterial/ui/adapter/FeedAdapter.java)
3. Extend FeedItemAnimator if custom animation is needed (app/src/main/java/io/github/froger/instamaterial/ui/adapter/FeedItemAnimator.java)
4. Update FeedContextMenu to handle new item actions (app/src/main/java/io/github/froger/instamaterial/ui/view/FeedContextMenuManager.java)

Add a new activity or screen

1. Extend BaseActivity and implement lifecycle methods (app/src/main/java/io/github/froger/instamaterial/ui/activity/BaseActivity.java)
2. Create layout XML with Material Design components (app/src/main/res/layout/activity_new_screen.xml)
3. Register activity in AndroidManifest (app/src/main/AndroidManifest.xml)
4. Add reveal animation view if transition needed (app/src/main/java/io/github/froger/instamaterial/ui/view/RevealBackgroundView.java)

Add a custom Material Design view with animation

1. Create custom View class in ui/view/ extending View (app/src/main/java/io/github/froger/instamaterial/ui/view/CustomView.java)
2. Define animation XML in res/anim/ for transitions (app/src/main/res/anim/custom_animation.xml)
3. Create drawable resource for Material Design styling (app/src/main/res/drawable-v21/btn_custom.xml)
4. Integrate into activity and add to FeedContextMenuManager if interactive (app/src/main/java/io/github/froger/instamaterial/ui/activity/MainActivity.java)

• Android Support Library (Material Design components) — Provides Material Design UI components (FAB, NavigationView, CardView, RecyclerView) with backward compatibility to API 15
• RecyclerView with custom FeedItemAnimator — Efficient scrollable feed with custom item insertion/removal animations to match Instagram's Material Design transitions
• Custom reveal animation (RevealBackgroundView) — Implements Material Design circular reveal transitions for navigation between screens, core to app's visual identity
• Image transformation utilities (CircleTransformation, RoundedTransformation) — Provides circular avatars and rounded corners on images without bloating with external image libraries initially

• Custom View implementations (RevealBackgroundView, FeedContextMenu) vs. standard Material Design library

  • Why: README indicates this is a reference implementation; showing custom Material Design implementation details
  • Consequence: More code to maintain, but serves educational purpose; newer versions use Design Support Library as noted in README

• Compile SDK 25 (API level 25) targeting Android 7.0+

  • Why: Balance between Material Design 2.0 features and device coverage at time of development
  • Consequence: Min API 15 support; older devices lack some Material animations and ripple effects

• Mock data for feed items in adapters

  • Why: Focus on UI/Material Design without backend integration complexity
  • Consequence: No real data persistence; purely demonstration of Material Design patterns

• Backend API integration or real data persistence
• User authentication or account management
• Real photo capture or filter processing (TakePhotoActivity is UI only)
• Offline caching or local database
• Push notifications or real-time messaging
• Support for Android versions below API 15

1. Support Library Deprecation: Project compiles against API 25 and Support Library v25—Android Studio will warn about deprecated dependencies; requires manual migration to AndroidX to update. 2. minSdkVersion 15 is obsolete: Android no longer supports API 15 in official toolchain; you'll need to increase minSdkVersion (recommend 21+) to build with modern Android tooling. 3. No Backend: App uses mock/placeholder data—no server integration; likes, comments, and posts don't persist. 4. Camera & Permissions: TakePhotoActivity depends on CWAC Camera and requires runtime permission handling not shown in file list; API 15 targets don't include runtime permissions, creating compatibility gaps on Android 6.0+.

• Circular Reveal Animation (Material Transition) — Core visual effect in Material Design (featured in RevealBackgroundView.java); transitions between screens via expanding/contracting circles to create continuity illusion.
• RecyclerView ItemAnimator — FeedItemAnimator.java customizes how list items appear/disappear/change; essential for smooth social feed UX and differentiates InstaMaterial from static lists.
• ObjectAnimator & AnimatorSet — Low-level APIs used throughout (like button, view, and icon animations); enables property-based tweening without frame-by-frame manual updates.
• Activity Transitions (Window Animations) — Application intro transitions and Comments activity transitions use enterTransition/exitTransition patterns; Material Design depends on smooth activity handoffs.
• ViewPager with Fragments (implied in photo filters) — PhotoFiltersAdapter suggests swipeable photo filter selection; common pattern for gallery/editing UX in social apps.
• Picasso Image Transformation Pipeline — CircleTransformation.java and RoundedTransformation.java show custom image transformations (circular avatars, rounded corners); Picasso's composable API enables clean image loading chains.
• ButterKnife View Binding — Eliminates findViewById() boilerplate across Activities/Adapters; InstaMaterial uses v8.4.0 before Kotlin synthetics/view binding superseded it.

• antoniolg/MaterializeYourApp — Similar Material Design reference implementation for Android circa 2014-2015; shows alternative approaches to toolbar, FAB, and transition animations.
• wasabeef/awesome-android-ui — Curated list of Android UI libraries and implementations; includes Material Design projects and advanced animation patterns relevant to learning from InstaMaterial.
• google/iosched — Google's official Google I/O app source; production-grade Material Design and RecyclerView patterns with actual data binding and architecture patterns.
• airbnb/lottie-android — Modern animation library used in production apps; InstaMaterial uses hand-coded animations that Lottie can simplify for new projects.

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.

Add unit tests for UI utility transformations (CircleTransformation, RoundedTransformation)

The repo contains custom image transformation classes (CircleTransformation.java and RoundedTransformation.java) in app/src/main/java/io/github/froger/instamaterial/ui/utils/ that are used with Picasso for image loading, but there are no corresponding tests in app/src/androidTest/. These transformations are critical for the Material Design visual appearance. Adding instrumented tests would ensure these transformations work correctly across different image sizes and densities, and prevent regressions.

• [ ] Create app/src/androidTest/java/io/github/froger/instamaterial/ui/utils/CircleTransformationTest.java with tests for bitmap transformation output
• [ ] Create app/src/androidTest/java/io/github/froger/instamaterial/ui/utils/RoundedTransformationTest.java to verify rounded corner application
• [ ] Add assertions for bitmap dimensions, color values at edges, and null handling
• [ ] Run tests with various image aspect ratios to ensure robustness

Migrate deprecated Picasso and Camera library dependencies with compatibility tests

The build.gradle shows dependency on Picasso 2.5.2 (from 2014) and commonsware.cwac:camera:0.7.0, both significantly outdated. More critically, the targetSdkVersion is 25 (Android 7.1, from 2016), which no longer meets Google Play requirements. Updating these dependencies with proper testing against TakePhotoActivity.java and image loading in FeedAdapter.java would modernize the codebase and ensure compatibility with current Android versions.

• [ ] Update com.squareup.picasso:picasso to latest version (2.8) in app/build.gradle
• [ ] Update commonsware.cwac:camera to cyanogenmod's or alternative maintained camera library, testing against app/src/main/java/io/github/froger/instamaterial/ui/activity/TakePhotoActivity.java
• [ ] Update targetSdkVersion to 34 in defaultConfig and test with storage permissions on modern APIs
• [ ] Verify image loading in FeedAdapter.java and UserProfileAdapter.java still works correctly
• [ ] Add integration tests in app/src/androidTest/ for photo capture and image display workflows

Add GitHub Actions CI workflow with automated testing and lint checks

The repo has no CI/CD configuration (.github/workflows/ is absent). Given the Material Design focus and complex animation code (FeedItemAnimator.java, RevealBackgroundView.java, custom animations in app/src/main/res/anim/), automated lint checks and test execution would catch regressions early. This is especially valuable for a reference implementation project that others learn from.

• [ ] Create .github/workflows/android-ci.yml with Android Gradle build setup
• [ ] Add lint checks for app/src/main/java/ to catch deprecated API usage and Material Design violations
• [ ] Configure workflow to run androidTest suite from app/src/androidTest/java/io/github/froger/instamaterial/
• [ ] Add build artifact upload for APK to allow reviewers to test PRs
• [ ] Set up workflow to run on pull_request and push to main/master branch

• Add AndroidX migration: Replace all android.support.* imports in ui/activity/, ui/adapter/, and ui/view/ files with androidx.* equivalents and update build.gradle dependencies to androidx:appcompat:1.x, androidx:recyclerview:1.x, etc.
• Write unit tests for FeedItemAnimator.java and RevealBackgroundView.java: Currently no test coverage in the adapter or view custom animation logic; add instrumentedTests in androidTest/ to verify animation state changes and view measurement.
• Document animation XML files: Add a comments guide in app/src/main/res/anim/ explaining what each animation (cycle_2.xml, slide_in_likes_counter.xml, etc.) does and where it's triggered in the code—currently undocumented.

Failed to generate security analysis.

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.