Repo brief: Tencent/QMUI_Android

Generated by RepoPilot · document generated 2026-09-15 · concise human review Evidence snapshot · analyzed 2026-09-15T16:31:34.030Z · commit 026e7d486677

Verdict

Concerns — Looks unmaintained — solo project with stale commits

• Tests present

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

QMUI Android is a comprehensive UI library that accelerates Android development by providing pre-built UI components (BottomSheet, Tab, rounded ImageView, pull-to-refresh), global style configuration system, and utility methods (device info, keyboard/statusbar management) that work across API 21+. It reduces boilerplate and enables design fidelity without writing foundation code. Modular monorepo: arch/ contains core Activity/Fragment architecture (QMUIActivity.java, QMUIFragment.java, QMUIFragmentPagerAdapter.java), arch-annotation/ defines compile-time annotations for routing (@ActivityScheme, @FragmentScheme, @LatestVisitRecord), and arch-compiler/ implements the annotation…

Start here

Open these first:

• arch/src/main/java/com/qmuiteam/qmui/arch/QMUIActivity.java — Base activity class that all QMUI activities inherit from; defines lifecycle and fragment container management
• arch/src/main/java/com/qmuiteam/qmui/arch/QMUIFragment.java — Base fragment class providing lifecycle hooks and effect/scheme handling; core foundation for fragment-based navigation
• arch/src/main/java/com/qmuiteam/qmui/arch/scheme/QMUISchemeHandler.kt — Central routing/deep-linking handler that processes schemes and delegates to activities/fragments
• arch/src/main/java/com/qmuiteam/qmui/arch/effect/QMUIFragmentEffectRegistry.java — Registry for side-effect handling in fragments; enables decoupled event processing and result passing
• arch/src/main/java/com/qmuiteam/qmui/arch/record/QMUILatestVisitStorage.java — Interface for persisting and restoring navigation history; critical for last-visited-fragment recovery

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone and explore: git clone https://github.com/Tencent/QMUI_Android.git && cd QMUI_Android. The project uses Gradle (build.gradle.kts files visible). Open in Android Studio. Start with qmuidemo/ (referenced in READ…

Daily commands:

Standard Android project: import into Android Studio, wait for Gradle sync. Run ./gradlew build to compile all modules. To run on device: ./gradlew installDebug (requires connected device/emulator). Annotation proce…

…shortened for this brief.

Key cautions & unknowns

• Stale — last commit 2y ago
• Solo or near-solo (1 contributor active in recent commits)
• Annotation processors are non-obvious: if you add new @ActivityScheme or @FragmentScheme annotations, you must rebuild the project (not just re-run) for SchemeProcessor to generate navigation code. Proguard rules…
• License evidence is incomplete or ambiguous.
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.