Levyra: A Music Player That Treats Downloads as Ownership, Not Cache

What Levyra Actually Solves

The documentation also positions Levyra for Windows users who want the same experience on a desktop. The Windows build uses a separate libvlc engine with global keyboard shortcuts and system tray controls. That is a different audience from the Android-first crowd. The README does not go deep into the Windows feature set beyond those controls, so treat that part as thinner. The core problem Levyra solves is the gap between streaming convenience and offline file ownership. It is not a novel idea, but the execution details matter, and those are where Levyra makes specific choices.

The Dual Engine Architecture

The dual engine approach has a cost. You are maintaining two playback stacks, which means two sets of edge cases. Android Auto support is listed, but only for Android. The Windows engine does not get that. The README does not explain how the two engines stay in sync on features like SponsorBlock skipping. SponsorBlock is listed as a native feature, but the documentation does not say whether it works on both platforms. That is a gap you should verify before assuming parity. The design is sound for its goals, but the split means you are not getting one unified codebase. You are getting two specialized integrations.

Offline Storage and File Format Choices

The HTTP Range resume is important for large files. If a download drops, you do not start from zero. Atomic verification suggests that files are checked for integrity before being marked as complete. The JSON backups are a way to export your playlists and listening data. The README does not specify the exact backup format or how to restore it. That is a limitation. You cannot confirm the restore process from the material. The choice of M4A over FLAC or Ogg is a trade-off. M4A is efficient and widely supported, but it is lossy. The README says "high-bitrate M4A," but it does not give a specific bitrate. If you are an audiophile who demands lossless, this is not the tool for you.

The Stream Extraction and Discovery Engine

The critical thing to note is that the README does not name the actual source of these streams. It says "stream extraction" and "dual resolver," but it never identifies the underlying service. That is a red flag for stability. If the source changes its API or blocks the app, the extraction breaks. The README even mentions "real-time 73% comment energy resonance," which is a vague metric that does not mean anything concrete. The discovery engine is a differentiator, but it is also a dependency. You are relying on external services for the entire discovery and extraction layer. The offline vault works without those services, but the player's main appeal is the combination of streaming and offline storage. If the extraction layer fails, you are left with a local player that only plays files you already have.

Getting It Running: Commands and Config

For a user, the simplest path is to install the APK from F-Droid or the GitHub releases page. For a developer, the repository layout is standard for a Compose Multiplatform project. You would open the project in Android Studio, sync Gradle, and run the Android target. The Windows target likely requires a desktop run configuration, but the README does not detail that. The home page might have more, but it is not in the material. One concrete config key is the storage path, Music/Levyra. That is where your files go. The README also mentions a "Song/Video toggle" in the player, which suggests you can choose between audio and video sources. That is a user-facing setting, not a config file. The lack of explicit build instructions is a minor gap for developers, but the release artifacts are available.

Privacy and Analytics: What the README Claims

However, the README does not mention how the stream extraction service handles your requests. When you search for a song or stream a track, your IP address and query are sent to that external service. The README does not disclose what that service does with your data. The "Zero Tracking" claim applies to the app itself, not to the third-party resolver. That is a distinction you should keep in mind. The SponsorBlock integration also sends video IDs to a public database. That is a known privacy trade-off. The README does not address it. So the privacy story is strong on the local side, but it is incomplete on the network side.

Maintenance, License, and Upgrade Cost

The upgrade cost is low for end users because F-Droid handles updates automatically. For developers, the dual engine and the Compose Multiplatform setup mean that upgrading to a new version of Media3 or libvlc could require changes in both platforms. The README does not provide a migration guide or a changelog. You would have to read the release notes on GitHub. The maintenance burden is on the project maintainer, not the user. But if you are considering contributing, the GPL-3.0 license and the active release schedule are factors. The project seems to be moving fast, which is good for feature velocity but risky for stability. The lack of a documented API for the stream resolver means that any change in the external service could break the app without a code change on your side.

A Real Alternative: Local Players vs. Stream Extractors

The real difference is the offline file format. Phonograph and Vinyl play whatever you give them, including FLAC and Ogg. Levyra saves to M4A, which is a specific choice. If you want lossless, Levyra is the wrong tool. NewPipe lets you choose the format and quality, but it does not embed lyrics or artwork in the file. Levyra does that. So the comparison is about trade-offs: lossless flexibility versus tagged M4A convenience. The README does not mention FLAC support at all. That is a gap. If you are a lossless user, you should look elsewhere. If you are fine with high-bitrate M4A and want the embedded metadata, Levyra is a better fit than a bare extractor.

Editorial conclusion

Adopt Levyra if you want a local-first Android music player that stores playable M4A files with embedded tags and lyrics, and if you accept that its stream extraction depends on external services that may break without notice. Do not adopt it if you need a stable, guaranteed source of music content or if you require a mature Windows desktop experience beyond the documented libvlc tray controls. Before committing, verify the current state of the dual resolver on your network, test the HTTP Range resume with a large download, and confirm that the F-Droid build matches the latest release. The project is under active development, so check the repository for recent issues and the last push date before relying on it for daily listening.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes