rukamori/archivetune

🌸 The Cutest Music Player With Support Local File and Youtube Music for Android!

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 47 minutes ago
Added to GitGenius on September 11th, 2026
Created on September 1st, 2025
Open Issues & Pull Requests: 110 (+0)
GitHub issues: Enabled
Number of forks: 248
Total Stargazers: 5,971 (+2)
Total Subscribers: 76 (+1)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 98
New in 7 days: 36
Closed in 7 days: 20
Avg open age: 40 days
Stale 30+ days: 37
Stale 90+ days: 3

Recent activity

Opened in 7 days: 32
Closed in 7 days: 20
Comments in 7 days: 13
Events in 7 days: 31

Top labels

  • BUG (361)
  • ENHANCEMENT (328)
  • CONFIRMED (51)
  • documentation (1)
  • good first issue (1)
  • question (1)
  • wontfix (1)

Detailed Description

ArchiveTune is a music player application for Android that combines local file playback with YouTube Music streaming in a single interface.

The tool addresses the fragmentation of music listening across multiple apps by integrating both offline library management and online streaming capabilities. It achieves this through a privacy-focused architecture built on Kotlin and Jetpack Compose, using Material Design 3 for the interface and MVVM patterns for maintainability. The application prioritizes performance and user experience for people who want comprehensive music access without relying on the official YouTube Music client.

ArchiveTune suits Android users who want a unified music experience spanning local files and YouTube Music without sacrificing privacy or performance. It works well for those comfortable with community-maintained applications and who value open-source alternatives to proprietary streaming apps. The project is built with modern Android development practices, making it relevant for developers interested in Jetpack Compose and contemporary Material Design implementation.

Almost all open issues are raised by outside users rather than the core team, demonstrating a substantial base of real-world adopters. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker is dominated by bug reports, enhancement requests, and confirmed issues.