原生、纯净、可扩展 —— 重新定义你的 B 站体验
3.7k
Stars
348
Forks
419
Open issues
9
Contributors
AI Analysis
BiliPai is a native third-party Bilibili (Chinese video platform) Android client built with Kotlin and Jetpack Compose, providing video, anime, live streaming, feeds, messaging, and offline download functionality. It is designed for daily Bilibili users seeking an alternative native experience with emphasis on playback optimization, Material You design, plugin extensibility, and tablet/foldable screen support. This tool is specialized for Bilibili users in Chinese-speaking regions; it is not ...
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Kotlin-native Bilibili third-party client prioritizing lightweight UX and plugin extensibility
BiliPai is a Kotlin/Jetpack Compose Android client for Bilibili (Chinese video platform), targeting users who prefer streamlined, customizable, privacy-conscious viewing over the official app. It covers core flows—video, anime, live, feed, downloads, messaging—with emphasis on playback quality (DASH, 4K, HDR), Material You theming, and a plugin system (JSON rules, external packages, native integration). Created November 2025, it has accumulated ~3,500 stars and ~87 stars in the past week as of July 2026. Adoption appears concentrated in Chinese Android user communities; real production metrics (download counts, active user base) are not independently verifiable.
BiliPai launched November 2025 as part of a growing ecosystem of third-party Bilibili clients (PiliPlus, bilimiao2, bilibilias also shown). The project explicitly positions itself as non-competitive cloning—focused on 'lightweight, quiet, customizable' experience rather than feature parity. Positioned after several established alternatives in the category.
Project gained 3,529 stars over ~7.5 months (Nov 2025 to Jul 2026), averaging ~470 stars/month. Recent weekly gain (87 stars) suggests sustained but modest momentum. Growth likely driven by: (1) Material 3 + Jetpack Compose native design, (2) built-in plugin system with no-recompile JSON rules, (3) explicit privacy stance (local login, minimal telemetry), (4) active maintenance (last push 2026-07-06, v9.6.0 released recently). Comparable projects (PiliPlus at 15K+ stars) indicate market awareness, though BiliPai remains smaller.
Adoption not verified through independent metrics. README cites GitHub download counts (badge present but numbers not inspected in this excerpt) and references 'total downloads' and 'latest version downloads'—data exists but quantity not independently confirmed. Active Telegram community channels suggest user base, but scale unknown. No corporate/institutional deployments mentioned. No third-party impact reports or case studies available in README. Adoption appears limited to enthusiast/power-user segments of Chinese Android ecosystem.
Based on README, appears to follow MVVM with Jetpack Compose UI layer. Network via Retrofit/OkHttp, storage via Room/DataStore. Media3/ExoPlayer for playback, custom danmaku rendering (DanmakuFlameMaster). Plugin system uses internal manifest-based dispatch and external Dex execution (described as 'preview stage'). Modular structure (app, settings-core, network-core, plugins, baselineprofile) suggests intentional separation. Actual implementation quality cannot be assessed from README alone.
Not documented in README. Presence of baselineprofile/ directory and macrobenchmark mention suggests performance testing infrastructure, but unit/integration coverage not specified.
Very active as of analysis date (2026-07-06). Last push occurred same day. Version 9.6.0 deployed with detailed CHANGELOG. Changelog references multiple subsystems (player, danmaku, plugins, UI), indicating continuous iteration. ~7 months of regular updates with no months skipped (inferred from version numbering and README timestamps). Social channels (Telegram, X) listed and referenced as ongoing, supporting active maintainer presence. No abandonment signals detected.
ADOPT IF: you are an Android enthusiast in the Chinese Bilibili ecosystem seeking a lightweight, customizable native client with strong Material 3 theming, extensible plugin architecture, and privacy-respecting defaults; you are comfortable with a younger project (7 months old) and willing to report issues. AVOID IF: you require enterprise-grade stability guarantees, production-critical SLAs, or broad non-Chinese market support; you depend on 100% feature parity with official app; your organization requires audit trails and vendor support contracts. MONITOR IF: you are evaluating long-term viability in a competitive niche; the project's ability to sustain active maintainance beyond year two; API changes from Bilibili that might break third-party clients; regulatory pressure on unofficial clients in China.
Independent dimensions
Mainstream potential
3/10
Technical importance
6/10
Adoption evidence
4/10
- Regulatory/legal: Third-party Bilibili clients face inherent risk of API changes, account bans, or takedown requests. BiliPai is not shielded from this.
- Maintenance concentration: Active maintainer evident, but no visible team/succession indicators. Bus factor potentially high; long-term sustainability unclear.
- Plugin sandbox: README notes external Dex execution in 'preview stage'—security and stability implications not yet proven at scale.
- API surface stability: Bilibili frequently modifies endpoints; project must track changes continuously or risk degradation.
- Adoption plateau risk: At 7 months with ~470 stars/month growth, project may not escape niche positioning; mainstream market share unlikely given entrenched alternatives.
BiliPai will likely stabilize as a sustainable niche tool within the enthusiast/power-user segment of the Chinese Bilibili community over the next 12-18 months. Growth may plateau around 5-8K stars if no significant feature differentiation or external catalyst emerges. Maintenance will probably continue at current cadence if maintainer remains engaged; risk of diminished updates if regulatory pressure increases or alternative projects gain momentum. Unlikely to challenge market-leading alternatives but may become preferred choice among users prioritizing Material 3 design and plugin extensibility.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://t.me/BiliPai
- Language
- Kotlin
- License
- NOASSERTION
- Last updated
- 8h ago
- Created
- 7mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Top contributors
Recent releases
Similar repos
bggRGjQaUbCoE/PiliPlus
PiliPlus is a third-party Flutter-based client for the BiliBili video platform,...
10miaomiao/bilimiao2
bilimiao is a third-party Android client for Bilibili (a major Chinese video...
1250422131/bilibilias
BILIBILIAS is a Bilibili (Chinese video platform) video parsing and caching...
yichengchen/ATV-Bilibili-demo
A tvOS client for BiliBili (a major Chinese video platform) that demonstrates...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
jay3-yy/BiliPai
this
|
3.7k | +198 | Kotlin | 7/10 | 8h ago |
|
bggRGjQaUbCoE/PiliPlus
|
15.9k | — | Dart | 7/10 | 3d ago |
|
10miaomiao/bilimiao2
|
2.9k | — | Kotlin | 7/10 | 1w ago |
|
1250422131/bilibilias
|
1.8k | — | Kotlin | 5/10 | 1mo ago |
|
yichengchen/ATV-Bilibili-demo
|
3.1k | — | Swift | 6/10 | 5d ago |
 tiajinsha/JKVideo
|
5k | — | TypeScript | 6/10 | 2mo ago |
Significantly larger community (4.4× stars). Different language/framework (Dart vs Kotlin). Both support plugins and offer third-party experience. BiliPai emphasizes Material 3 native feel; PiliPlus broader user base may indicate different positioning or earlier market entry.
Similar language, smaller community. Fewer feature details in comparable metadata. BiliPai's explicit plugin system, Material You focus, and actively maintained appearance may differentiate, though direct capability comparison not possible from README alone.
Smaller footprint. Limited metadata available. BiliPai's emphasis on extensibility and modern Android APIs (Material 3, Media3) may offer technical advantages, but adoption evidence insufficient to claim superiority.
BiliPai explicitly does not aim to replicate official client comprehensively. Targets users seeking lightweight, privacy-respecting, customizable alternative. Not positioned as replacement, but as adjacent experience for specific user preferences.
Different platform/language (web/cross-platform vs Android-native). Both support plugin architectures. Limited basis for direct comparison; different audience.
