vivizzz007/vivi-music
Kotlin No license Mobile Single maintainer risk License not recognized by GitHubVivi-Music is an expressive Material 3–based YouTube Music client for Android.
1.3k
Stars
70
Forks
79
Open issues
5
Contributors
AI Analysis
Vivi-Music is a Material 3-based YouTube Music client for Android that streams ad-free music with dynamic color-adaptive UI and privacy-focused local storage. It serves Android users who want a feature-rich alternative to the official YouTube Music app, particularly those valuing privacy, customization, and visual polish. This is not a general-purpose music player but a specialized third-party client for YouTube Music consumers.
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.
Material 3 YouTube Music client for Android with dynamic theming and offline support, 14 months old
Vivi-Music is a GPL-3.0 Android client for YouTube Music built in Kotlin, emphasizing Material 3 design with dynamic color adaptation, animated visualizers, synced lyrics, and offline download capability. It targets privacy-conscious listeners seeking an ad-free, aesthetically-driven music experience. The project gained 1,232 stars and 44 new stars in the past week as of June 2026, placing it in the mid-tier of the YouTube Music client ecosystem but significantly smaller than SimpMusic (9,713 stars) and InnerTune (5,967 stars).
Created April 2025, Vivi-Music emerged in the established category of third-party YouTube Music clients for Android. This category has been active since ~2020, with multiple projects offering ad-free streaming and customization. Vivi-Music positions itself as design-forward rather than feature-maximalist, focusing on Material 3 compliance and visual polish.
The project shows steady, recent activity: last push June 29, 2026 (1 day before evaluation date) and 44 stars gained in 7 days suggests consistent interest. However, 14 months of development with 1,232 stars indicates modest but stable adoption compared to established competitors. The growth curve appears linear rather than accelerating, with no evidence of viral adoption or major milestone triggers.
Adoption not verified through direct metrics. README mentions 'download' button and GitHub releases are available, but no download count data is provided in metadata. Ko-fi support link suggests some user base funding the developer, but scale is unknown. Comparable projects (InnerTune, SimpMusic) have documented user communities; Vivi-Music's community presence is not evident from available information.
Based on README, the project uses Kotlin and appears to follow modern Android patterns with Material 3 guidelines. README mentions dynamic color theming, animated canvas visualizers (Apple Music-style), an integrated equalizer, karaoke lyric syncing, and OTA update infrastructure. Likely built with Jetpack Compose or Material Design components given the emphasis on Material 3. Architecture appears service-based (background playback, offline caching). No details on API integration method, authentication handling, or data layer are disclosed in README.
Not documented in README. No mention of unit tests, integration tests, or CI/CD pipeline.
Active maintenance confirmed: push date 2026-06-29 is current (1 day before evaluation). README is well-structured and recently updated. Ko-fi donation link present suggests single-author or small-team development. No public issue tracker snapshot provided in metadata, so issue response time cannot be assessed. Commits appear recent, but frequency cannot be determined from repository metadata alone.
ADOPT IF: you prioritize Material 3 design aesthetics, dynamic color theming, and privacy-first architecture; you are comfortable with a 14-month-old project maintained by likely one developer; you can tolerate potential API breakage or feature gaps relative to larger competitors. AVOID IF: you require battle-tested stability, extensive community support, or certainty of long-term maintenance; you need features not yet implemented (verify against README before use); you cannot tolerate reliance on a single maintainer. MONITOR IF: the project continues active commits and star growth; you want to use it but wish to see 18–24 months of demonstrated stability first; you are evaluating it as part of platform selection and want to hedge against abandonment.
Independent dimensions
Mainstream potential
3/10
Technical importance
5/10
Adoption evidence
3/10
- Single maintainer or very small team: Ko-fi link and no visible contributor list suggest potential for abandonment if maintainer loses interest. No documented succession plan.
- YouTube API dependency: All YouTube Music clients risk breakage if YouTube alters its API, terms of service, or anti-scraping measures. Vivi-Music has no stated mitigation strategy.
- Early-stage maturity: 14 months of development means edge cases, bugs, and performance issues may not yet be surface-tested across diverse device types and Android versions.
- Competitive saturation: The YouTube Music client category already has 4+ established projects with 5–10× more stars. User acquisition may slow as the market stratifies.
- Unclear data persistence model: README does not detail how offline data is stored, encrypted, or synced. Privacy claims ('zero trackers') are stated but not independently verified.
Vivi-Music will likely remain a niche, design-focused alternative in the YouTube Music client ecosystem, with adoption constrained to users who specifically value Material 3 aesthetics and privacy-first positioning. Mainstream growth is improbable absent significant feature innovation or a major failure in a competitor. Most probable trajectory: modest steady state at 2,000–5,000 stars within 12 months, active maintenance if developer remains engaged, or dormancy if abandoned.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- Kotlin
- License
- NOASSERTION
- Last updated
- 1d ago
- Created
- 15mo 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
[Feat]: search bar for options menu
[Feat]: export playlist button
[Feat]:Add auto-mix feature
age restriction to all of the songs for me
[Feat]: Decrease the volume of lyrics only
Top contributors
Similar repos
z-huang/InnerTune
InnerTune is a Material 3-compliant YouTube Music client for Android that...
ArchiveTuneApp/ArchiveTune
ArchiveTune is a Material Design 3 music player for Android that supports local...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
vivizzz007/vivi-music
this
|
1.3k | +52 | Kotlin | 7/10 | 1d ago |
|
z-huang/InnerTune
|
6k | — | Kotlin | 8/10 | 8mo ago |
|
ArchiveTuneApp/ArchiveTune
|
3.4k | — | Kotlin | 7/10 | 15h ago |
 Arturo254/OpenTune
|
1.7k | — | Kotlin | 7/10 | 5d ago |
 maxrave-dev/SimpMusic
|
9.8k | — | Kotlin | 7/10 | 2d ago |
SimpMusic is 8× larger by stars and appears more established. Vivi-Music differentiates via Material 3 focus and animated visualizers; SimpMusic likely prioritizes breadth of features and platform stability. Vivi-Music is newer (14 months vs. multi-year projects).
InnerTune is 5× larger. Both are Kotlin-based YouTube Music clients. Vivi-Music emphasizes visual polish and theming; InnerTune likely has broader adoption and longer stability track record.
Mid-tier competitor with roughly 2.5× Vivi's stars. Exact differentiation unclear from available metadata, but Vivi-Music's Material 3 + animation focus may be its unique value proposition.
Closest peer by star count (1.3× Vivi's size). Both appear to be recent or mid-stage projects. Vivi-Music's Material 3 theming may differentiate it, but functional parity with OpenTune is likely.
Vivi-Music targets users who reject the official app due to ads, tracking, or feature constraints. All three parties (Google, Vivi, competitors) compete on user experience and privacy rather than core functionality.
