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/hanks-zyh/HTextView 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 5y ago

• 14 active contributors
• Apache-2.0 licensed
• Tests present
• ⚠ Stale — last commit 5y ago
• ⚠ Concentrated ownership — top contributor handles 70% of recent commits
• ⚠ No CI workflows 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 hanks-zyh/HTextView repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/hanks-zyh/HTextView.

What it runs against: a local clone of hanks-zyh/HTextView — 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 hanks-zyh/HTextView | 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 ≤ 1857 days ago | Catches sudden abandonment since generation |

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

# 1. Repo identity
git remote get-url origin 2>/dev/null | grep -qE "hanks-zyh/HTextView(\\.git)?\\b" \\
  && ok "origin remote is hanks-zyh/HTextView" \\
  || miss "origin remote is not hanks-zyh/HTextView (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 "htextview-base/src/main/java/com/hanks/htextview/base/HTextView.java" \\
  && ok "htextview-base/src/main/java/com/hanks/htextview/base/HTextView.java" \\
  || miss "missing critical file: htextview-base/src/main/java/com/hanks/htextview/base/HTextView.java"
test -f "htextview-base/src/main/java/com/hanks/htextview/base/IHText.java" \\
  && ok "htextview-base/src/main/java/com/hanks/htextview/base/IHText.java" \\
  || miss "missing critical file: htextview-base/src/main/java/com/hanks/htextview/base/IHText.java"
test -f "htextview-base/src/main/java/com/hanks/htextview/base/CharacterUtils.java" \\
  && ok "htextview-base/src/main/java/com/hanks/htextview/base/CharacterUtils.java" \\
  || miss "missing critical file: htextview-base/src/main/java/com/hanks/htextview/base/CharacterUtils.java"
test -f "htextview-base/src/main/java/com/hanks/htextview/base/HText.java" \\
  && ok "htextview-base/src/main/java/com/hanks/htextview/base/HText.java" \\
  || miss "missing critical file: htextview-base/src/main/java/com/hanks/htextview/base/HText.java"
test -f "demoapp/src/main/java/com/example/demoapp/MainActivity.java" \\
  && ok "demoapp/src/main/java/com/example/demoapp/MainActivity.java" \\
  || miss "missing critical file: demoapp/src/main/java/com/example/demoapp/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 1857 ]; then
  ok "last commit was $days_since_last days ago (artifact saw ~1827d)"
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/hanks-zyh/HTextView"
  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).

HTextView is an Android library that applies morphing animation effects to text rendering, not to a traditional TextView widget. It provides 7 different animation styles (Scale, Evaporate, Fall, Line, Typer, Rainbow, Fade) that animate text transitions with custom font support, packaged as modular dependencies (htextview-base, htextview-fade, etc.) that can be mixed and matched in applications. Modular monorepo: root build.gradle defines shared versions (support_version, compile_version, library_version); demoapp/ is a standalone Android app under demoapp/src/main/java/com/example/demoapp/ with activities for each effect type (FadeTextViewActivity.java, ScaleTextViewActivity.java, etc.); individual animation libraries (htextview-fade, htextview-scale, etc.) are referenced as compile dependencies but not visible as source directories in this file list, suggesting they may be external Maven artifacts or in unlisted subdirectories.

Android developers building mobile UIs who need eye-catching text animations without building custom Canvas rendering from scratch. Used by app developers targeting Android 15+ (minSdkVersion) who want morphing label effects similar to iOS LTMorphingLabel.

Moderately mature but dormant: at v0.1.6 (library_version in build.gradle), the repo structure shows complete modularization with demo app and multiple animation types, but the gradle setup uses Android Gradle 3.1.2 (from 2017) and buildToolsVersion 27.0.3, suggesting no recent maintenance. No CI/testing infrastructure visible in the file list; only ExampleInstrumentedTest.java exists.

Low immediate risk for stable use, but aging dependencies: compileSdkVersion 27 (API 27, from 2017) is well below current Android 14+. Single-maintainer risk (hanks-zyh) with no visible recent commits. No tests beyond one example instrumented test, and the Bintray release config (enable_bintray) references obsolete Bintray infrastructure (sunset 2021). Breaking changes likely needed for modern Android Gradle Plugin compatibility.

No active development visible: file list shows static structure with no recent commit hashes or CI workflows beyond .github/FUNDING.yml. The demo.apk artifact is pre-built and checked in, suggesting this is a stable-but-unmaintained library.

Clone and build the demo app: git clone https://github.com/hanks-zyh/HTextView.git && cd HTextView && ./gradlew :demoapp:assembleDebug (or gradlew.bat on Windows). Requires JDK 8+ and Android SDK with build-tools 27.0.3 and API 27.

Daily commands: ./gradlew :demoapp:installDebug to deploy demo app to connected device/emulator. Then launch the app from the launcher or adb shell am start com.example.demoapp/.MainActivity.

• htextview-base/src/main/java/com/hanks/htextview/base/HTextView.java — Core abstract base class that all animated text views inherit from—defines the animation lifecycle, text measurement, and rendering pipeline
• htextview-base/src/main/java/com/hanks/htextview/base/IHText.java — Interface contract that all animation implementations must follow—defines the animation behavior and character-level updates
• htextview-base/src/main/java/com/hanks/htextview/base/CharacterUtils.java — Utility class for diffing old/new text and determining which characters changed—critical for selective character animation
• htextview-base/src/main/java/com/hanks/htextview/base/HText.java — Data model holding character-level animation state (color, offset, alpha)—passed to all paint operations
• demoapp/src/main/java/com/example/demoapp/MainActivity.java — Entry point showcasing all animation types available in the library—reference for API usage patterns
• htextview-base/build.gradle — Library publication and dependency configuration—defines Bintray release targets and support library versions

Add a New Animation Effect Type

1. Create new class implementing IHText in htextview-base module (e.g., MyCustomHText.java) (htextview-base/src/main/java/com/hanks/htextview/base/)
2. Implement onDraw(Canvas canvas, Paint paint, HText[] hTexts, int startIndex) to apply custom transformations to HText array (translate, scale, color, alpha) (htextview-base/src/main/java/com/hanks/htextview/base/IHText.java)
3. Create custom TextView subclass extending HTextView and override onCreateAnimator() to instantiate your IHText and configure ValueAnimator (htextview-base/src/main/java/com/hanks/htextview/base/HTextView.java)
4. Add demo Activity in demoapp/src/main/java/com/example/demoapp/MyEffectActivity.java following BaseActivity pattern (demoapp/src/main/java/com/example/demoapp/BaseActivity.java)
5. Register new activity in AndroidManifest.xml and add navigation entry in MainActivity.java (demoapp/src/main/AndroidManifest.xml)

Modify Text Animation Duration or Interpolator

1. Locate the animation effect's HTextView subclass in htextview-base or htextview-demo modules (htextview-base/src/main/java/com/hanks/htextview/base/HTextView.java)
2. Override setAnimationDuration(long duration) or modify the ValueAnimator.setDuration() call in onCreateAnimator() (htextview-base/src/main/java/com/hanks/htextview/base/HTextView.java)
3. Call animator.setInterpolator(new CustomInterpolator()) to change animation curve (e.g., LinearInterpolator, AccelerateDecelerateInterpolator) (htextview-base/src/main/java/com/hanks/htextview/base/HTextView.java)

Customize Text Diff Behavior for Animations

1. Review CharacterUtils.diff() method to understand current character diffing logic (added, removed, kept, modified) (htextview-base/src/main/java/com/hanks/htextview/base/CharacterUtils.java)
2. Modify CharacterUtils or override in your HTextView subclass to change which characters trigger animations on text update (htextview-base/src/main/java/com/hanks/htextview/base/CharacterUtils.java)
3. Call updateText(newText) in HTextView to trigger animation; internally uses CharacterDiffResult to animate only changed characters (htextview-base/src/main/java/com/hanks/htextview/base/HTextView.java)

• Canvas & Paint (Android Framework) — Direct pixel-level control for character-by-character animation transforms (translate, scale, color, alpha); minimal overhead vs. View layout inflation
• ValueAnimator — Drives frame-by-frame animation from 0–1.0 progress; integrates with Android choreographer for 60fps; enables custom interpolators
• AppCompatTextView base — Leverages system text measurement (TextPaint, Layout) for character positioning; maintains backward compatibility to API 15
• Bintray/JCenter publishing — Distributes library as AAR artifact (com.hanks:htextview-base) for simple Gradle dependency management

• Character-level animation via onDraw() custom rendering vs. per-character View inflation

  • Why: Custom Canvas rendering is vastly more efficient: single invalidate() loop vs. thousands of View objects
  • Consequence: Developers cannot use standard View touch handlers or layout constraints on individual characters; animations are visual-only

• Diff-based character animation (only changed chars animate) vs. animate all chars on every text update

  • Why: Reduces computational load and visual noise; users see only changes
  • Consequence: Requires CharacterUtils diffing logic; added/removed/modified indices must be computed each update

• Abstract HTextView base class + Interface IHText for effect plugins vs. monolithic single class

  • Why: Extensibility; new effects inherit standard text measurement and lifecycle; effects are isolated
  • Consequence: Slight boilerplate for each effect; requires understanding onDraw() contract and HText data structure

• Does not provide real-time text editing or SelectionCallback support (animations are applied after text is finalized)
• Does not support animated text selection or highlighting
• Not a rich-text library; no mixed font sizes, colors, or styles per effect (animations treat all chars identically within effect rules)
• Does not support hardware acceleration (Canvas animations may stutter on some low-end devices)
• Not for accessibility-critical apps; no TalkBack friendly event propagation

Bintray repository references in build.gradle (enable_bintray = true, classpath 'com.novoda:bintray-release:0.8.0') are outdated; Bintray was sunset in 2021, so these tasks will fail on modern Gradle. Android Gradle Plugin 3.1.2 is incompatible with JDK 9+; requires JDK 8 only. No gradle wrapper committed (.gradle/ not in file list), so running ./gradlew may fail on first clone without manual wrapper setup. Support library version 27 requires compileSdkVersion 27, which conflicts with modern Android (target 14+).

• Property Animation (ObjectAnimator / ValueAnimator) — HTextView text transitions likely use Android's Property Animation framework (ValueAnimator for frame updates, ObjectAnimator for property changes) to drive morphing; understanding animation lifecycle and interpolation is essential for modifying or adding effects.
• Canvas Rendering & Custom Drawing — Each animation effect (Fade, Scale, Evaporate) likely overrides onDraw() or uses Canvas.drawText() with custom paint/matrix transformations; you must understand Canvas coordinate systems and paint properties to modify rendering.
• Character-Level Text Segmentation — Effects like Typer, Rainbow, and Line animate individual characters or words separately; the library must partition text into character/glyph boundaries and track animation state per character, which is non-trivial in Unicode/RTL text.
• Interpolators & Easing Functions — Smooth animation transitions (ease-in, ease-out, linear, bounce) are controlled by TimeInterpolator implementations; HTextView effects use different interpolators to create natural-feeling morphing (e.g., AccelerateInterpolator for Fall effect).
• Matrix Transforms for 2D Graphics — Scale, Evaporate, and Line effects likely use Matrix transformations (rotation, scaling, translation) applied during Canvas drawing to achieve morphing without redrawing the entire text; understanding Matrix.setScale() and Canvas.concat() is critical.
• Android Modular Dependency Model — HTextView uses separate gradle modules (htextview-base, htextview-fade, htextview-scale) to allow consumers to import only needed effects; understanding build.gradle dependency declarations and AAR packaging is essential for maintaining or extending the library.
• Bézier Curves & Path Animation — Effects like Fall and Evaporate likely animate characters along curved paths (using Path and PathMeasure); Bézier interpolation ensures smooth, natural-looking trajectories for disappearing/falling text.

• lexrus/LTMorphingLabel — iOS equivalent library that inspired HTextView; implements the same morphing animation effects for UILabel on iOS.
• HitenDev/flutter_effects — Flutter port of animation effects; allows developers to use similar morphing text animations in Flutter apps, cross-platform companion to HTextView.
• android/architecture-samples — Official Android architecture reference; useful for modernizing HTextView's app structure and build system to current Android best practices.
• material-components/material-components-android — Modern Material Design library for Android; HTextView could adopt Material animation utilities and support libraries instead of legacy AppCompat 27.1.0.
• airbnb/lottie-android — Production-grade Android animation library using JSON specs; demonstrates modern animation lifecycle management and could inspire HTextView's modernization.

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 instrumented tests for animation effect implementations

The repo has multiple animation effect classes (EvaporateTextView, FallTextView, LineTextView, RainbowTextView, ScaleTextView, TyperTextView, FadeTextView) but only contains a placeholder ExampleInstrumentedTest.java. Each effect should have specific tests validating animation timing, frame rendering, and text transformation logic. This ensures animation effects behave consistently across Android versions and prevents regressions when refactoring core animation logic in htextview-base.

• [ ] Create demoapp/src/androidTest/java/com/example/demoapp/animations/ directory
• [ ] Add EvaporateTextViewAnimationTest.java to test particle evaporation effects and alpha transitions
• [ ] Add FallTextViewAnimationTest.java to test gravity-based falling animation and collision detection
• [ ] Add ScaleTextViewAnimationTest.java to test scale transformation and timing consistency
• [ ] Verify tests run on API 15+ (minVersion) using @RequiresApi annotations where needed

Add GitHub Actions CI workflow for automated builds and APK generation

The repo has a demo.apk in the root but no automated CI pipeline. With outdated build tools (Gradle 4.6, AGP 3.1.2), having automated builds ensures compatibility across Android SDK versions and catches build failures early. A workflow should build the demo app and library modules, run instrumented tests, and optionally publish APK artifacts for each release.

• [ ] Create .github/workflows/android-build.yml with gradle build steps
• [ ] Configure workflow to run on push to main/master and pull requests
• [ ] Add steps to build demoapp module and run ./gradlew build for htextview-base
• [ ] Include upload-artifact action to store generated APKs in workflow artifacts
• [ ] Add Android SDK setup using actions/setup-java@v3 and android-gradle-action

Create comprehensive documentation for htextview-base animation architecture

The htextview-base module is the core library (with proguard-rules.pro suggesting it's meant for distribution), but there's no htextview-base/README.md explaining the animation framework architecture. New contributors cannot understand how to extend the base animation class or create new text effects. This documentation should explain the rendering pipeline used by all effects in demoapp.

• [ ] Create htextview-base/README.md documenting the base animation architecture
• [ ] Explain the custom Canvas-based rendering approach used instead of standard TextView
• [ ] Document how each animation type (Scale, Evaporate, Fall, Line, Typer, Rainbow) extends the base class
• [ ] Add code example showing how to create a new custom animation effect
• [ ] Reference the demoapp activities (BaseActivity.java pattern) as implementation examples

• Migrate build.gradle to Android Gradle Plugin 7.x+ and remove Bintray references, updating library_version and compileSdkVersion to modern values (e.g., 34); this fixes the deprecated toolchain and enables CI/CD.
• Add unit tests for animation frame interpolation: create androidTest/java/com/example/demoapp/FadeAnimationTest.java to verify frame transitions in FadeTextView using Espresso or Robolectric; currently only ExampleInstrumentedTest.java exists.
• Document each animation effect with inline JavaDoc in the demo Activities (e.g., add class-level comments to FadeTextViewActivity.java explaining how animationDuration and other custom attributes affect the fade effect) and extract into a EFFECTS.md guide.

The HTextView project has significant security concerns primarily related to severely outdated dependencies and platform targets. The use of Gradle 4.6, Android API 27, and support library 27.1.0 (all from 2017-2018) exposes the codebase to numerous known vulnerabilities. The minimum API level of 15 is exceptionally low by modern standards. While the core library functionality (text animation) has low inherent security risk, the outdated build infrastructure and lack of modern Android security configurations present substantial risks. Immediate action required: update all build tools, target modern API levels (34+), migrate to AndroidX, and establish a baseline security configuration. The codebase would benefit from automated dependency scanning and regular security audits.

• High · Outdated Gradle Build Tools and Dependencies — build.gradle, gradle/wrapper/gradle-wrapper.properties. The project uses Gradle 4.6 and Android Gradle Plugin 3.1.2, both released in 2018. These versions contain known security vulnerabilities and lack modern security features. Support library version 27.1.0 is also outdated and no longer receives security updates. Fix: Update to latest stable versions: Android Gradle Plugin 8.x, Gradle 8.x, and migrate to AndroidX with latest support libraries (androidx.appcompat:appcompat:1.6.x or higher)
• High · Outdated Android Target and Compile API Levels — build.gradle (ext.compile_version = 27, ext.target_version = 27). The project targets API level 27 (Android 8.1), released in 2017. Google Play requires apps to target API 34 or higher as of 2024. This exposes the app to unpatched Android OS vulnerabilities and missing security features like scoped storage and modern permission handling. Fix: Update targetSdkVersion and compileSdkVersion to at least 34 (API level 34). Implement required runtime permissions and storage scopes.
• Medium · Minimum SDK Version Too Low — build.gradle (ext.min_version = 15). The project supports API level 15 (Android 4.0.3, released 2012). This ancient API level lacks critical security features including modern TLS support, ASLR improvements, and secure random number generation. Fix: Increase minSdkVersion to at least 21 (Android 5.0). Devices below this level represent a negligible market share and are security risks.
• Medium · Missing Security Headers and Configuration — demoapp/src/main/AndroidManifest.xml, demo.apk. No AndroidManifest.xml security hardening visible, such as usesCleartextTraffic attribute, network security configuration, or explicit intent handling. The demo APK being versioned in git is unusual and may contain outdated code. Fix: Add network_security_config.xml disabling cleartext traffic, review manifest for implicit intents, implement certificate pinning for sensitive network calls, and remove demo.apk from version control.
• Low · Deprecated Bintray Repository Configuration — build.gradle (jcenter(), com.novoda:bintray-release:0.8.0). The build script references JCenter and includes bintray-release plugin (v0.8.0). JCenter has been sunset as of May 2021, and the bintray-release plugin is no longer maintained. Fix: Replace JCenter with Maven Central. For publishing, migrate to Sonatype Central Repository or Maven Central using gradle-maven-publish-plugin.
• Low · Binary Artifact in Version Control — demo.apk. The demo.apk file is committed to the Git repository, which is inefficient and can introduce security risks if the APK contains sensitive information or unverified code. Fix: Remove demo.apk from git history using 'git filter-branch' or BFG Repo-Cleaner. Add .apk to .gitignore and build/distribute through proper CI/CD pipelines.

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.