# BitChord: an Android client whose legal notice disclaims the access it needs > kushagrasinghx/BitChord is a Kotlin Android YouTube Music client distributed as a signed APK from its own releases page. The interesting file is the disclaimer, which names four companies the app is not affiliated with, refuses to guarantee access to any of them, and hands the legal burden to the person running it. **kushagrasinghx/BitChord** — BitChord - A modern YouTube music client with clean aesthetics inspired from Apple Music - Repository: https://github.com/kushagrasinghx/BitChord - Website: https://bitchord.kushagrasingh.in/ - Stars: 2,310 · Forks: 209 - Language: Kotlin - License: GPL-3.0 - Published: 2026-09-16 · Updated: 2026-09-16 · Language: en - Canonical page: https://hysenlabs.com/projects/kushagrasinghx-bitchord ## One channel, one file, one device toggle Distribution is described in a single paragraph. You download the latest signed APK from the releases page, and sideloading it requires enabling Install unknown apps for whichever app you open the file with. No app store is named anywhere in the file, so a Google Play listing, an F-Droid package or a marketplace copy is neither offered nor ruled out by this text. The signing is the maintainer's, not yours, and the repository ships `keystore.properties.example` rather than a keystore, which is the arrangement you would expect: the example file tells you the shape of the signing config, and the key itself stays with the person who publishes the release. Recent tags are v1.7 on 2026-09-25, v1.6 on 2026-09-15 and v1.5.2 on 2026-09-05, so the line moves by minor version, with the third of those carrying Hotfix in its release title rather than in the tag. The last push on the repository is dated 2026-10-03. ## An Android app with a backend module and a native module The primary language is Kotlin and the build is Gradle, with `gradlew` and `gradlew.bat` both committed, so the Windows wrapper exists for building rather than running, since the shipped artefact is an APK. The tree is wider than a single Android application module. `app/` is the client, `backend/` is a second module whose purpose the file never states, and `native/` holds a native component. Alongside them sit `build.gradle.kts`, `settings.gradle.kts`, `gradle.properties` and a `gradle/` directory, plus a `docs/` folder and three community documents the contributing section links: a contributing guide, a code of conduct, a maintainers list and an additional documents file. Two root images are worth noting for what they say about priorities: `Banner.png` and `Logo.png` for presentation, and `upi_support.jpg`, an image named for UPI, the instant payment system, which is the support section shipped as a picture alongside a Ko-fi link and a PayPal link. ## The disclaimer names four companies the feature list never mentions Two notices say the same thing at different lengths. The callout near the top states that BitChord is not affiliated with, endorsed by or connected to YouTube or Google in any way, and that you use it at your own discretion. The dedicated legal section widens the list to Google LLC, YouTube Music, Deezer, Telegram and any of their parent companies. Two of those four are instructive. Deezer appears nowhere in the feature descriptions, so the reference presumably anticipates the pluggable source system rather than any shipped integration, and it is the only sign that sources other than YouTube Music are expected to exist. Telegram appears in the feature list only as a visual reference, the interface being described as Telegram-style translucent bars, so the company is disclaimed in the same document that borrows its design language. The disclaimer also states that BitChord hosts no media at all, operating strictly as an interface to scan local device storage or stream from public, public-facing or user-authenticated APIs. ## The app promises a clean player and refuses to promise the access One bullet in the legal section is more informative than the rest. The no ad-blocking guarantee says the project focuses on providing a clean listening environment but does not guarantee permanent bypasses or modifications to commercial third-party platform conditions. That is the honest sentence, because a direct client for a commercial catalogue has no contract with the catalogue: it streams from an API that can change, be rate limited or be closed, and the only thing the project controls is its own request layer. The fair-use bullet completes the transfer of responsibility, saying the software is created solely for personal research, educational and fair-use purposes and that the user is entirely responsible for ensuring their usage aligns with local copyright laws and the YouTube terms of service. So the position is coherent and stated up front: this is an interface whose continued function is not something the author can promise, and using it well is the user's legal problem, not the maintainer's. ## Lossless audio is a module you supply, and the service is the fallback The audio quality story is the clearest illustration of that arrangement. Hi-res lossless audio in FLAC and ALAC is described as coming from a configured module source, with YouTube Music as fallback, which inverts the usual arrangement: the third-party path is the feature and the official service is the safety net. The pluggable source system is where the weight sits, and the controls described for it are unusually complete: you can add a source, edit one, test one, and health-check one from inside the app. So a broken module is something you can diagnose rather than something you file a report about. Two other quality settings exist in the same family. Per-network audio quality gives separate quality ceilings for Wi-Fi and mobile data, so a mobile plan and a home connection can be capped differently, and the now-playing screen carries stats for nerds, which the file lists as codec, bit depth, sample rate and more, so you can see what you actually received instead of trusting a label. ## Exactly one feature is labelled beta The feature table is dense and, with one exception, entirely unqualified. Automix is marked Beta and described as DJ-style transitions with beat-matching and tempo-stretching, which is the most novel thing in the list and the only thing the file hedges. The neighbouring playback claim is stated flatly: gapless playback with true crossfade, adjustable from 0 to 12 seconds. Everything else in the Playback group is flat as well, including search, browse and play of anything available on YouTube Music, offline downloads with embedded metadata, local library integration, and background playback through a proper foreground media session. That last one is worth separating out, because on Android a media session is the difference between music that keeps playing when you leave the app and music that does not, and the word proper in that line suggests it was once not. The Controls and Tweaks group is the most conventional: playback speed from 0.5 to 2.0 times, skip silence, a sleep timer with fixed presets or stop after this track, and system equalizer integration. ## Four visual features are other people's work The Experience column is where the credits are, and the file gives them precisely once. Apple-like lyrics animation is credited to a named repository, am-lyrics by binimum, which is the only external attribution anywhere in the feature list. Around it sit word-synced lyrics with word and syllable level highlighting gathered from multiple sources, an animated album canvas providing motion artwork on the now-playing screen, dynamic artwork-driven theming that extracts a Material palette from the album art, and a frosted-glass interface implemented with Haze under Material 3 theming. So of the four things that make the app look the way it does, one is credited in writing, one draws its palette from a third-party component library, one is a data pipeline from unnamed sources, and one is a motion canvas. None of that is a complaint about the quality of the work. It is a note about what you are installing when you sideload an APK from a single release channel with 220 open issues on the repository. ## Four account surfaces, one of which is Google The Connectivity and Accounts group names four separate external relationships, and only one of them is about content. Signing in with a Google account is what buys personalized content, which makes it the single point where your identity is exposed to a service BitChord explicitly disclaims any relationship with. Discord Rich Presence is a display integration with its own in-app login, publishing the current track, artist, album and progress. Scrobbling is offered to Last.fm and ListenBrainz, so listening history can be sent to one, the other, or both. The fourth is local rather than remote: offline downloads with embedded metadata and local library integration, which is the part of the app that keeps working without a network at all. The copyleft bullet closes the file: the project is free software under GPLv3, the license does not let anyone forbid others from selling or redistributing copies, and any distribution must come with the Corresponding Source under the same license. For a project whose only distribution vehicle is a signed APK, that sentence is the mechanism by which the source travels with the binary. ## Conclusion Read BitChord as a client whose durability depends on things it does not control. That is stated plainly in its own legal notice, which is more useful to a prospective user than a promise would be. It fits an Android user who wants lossless audio, word-synced lyrics, scrobbling and a themed interface, and who is willing to sideload and to supply their own module source for anything above the service's own ceiling. It does not fit anyone who needs a supportable install, since a signed APK with an unknown-apps toggle is the only channel the file names. Four things to check before you rely on it. Read the disclaimer end to end, because the fair-use bullet puts compliance with local copyright law and the YouTube terms on you personally, and the no-ad-blocking bullet promises nothing about the service continuing to work as it does today. Work out where your lossless audio comes from, since FLAC and ALAC are a configured module source and YouTube Music is only the fallback. Count the third-party pieces you are trusting, because the lyrics animation, the word-sync data, the frosted glass effect and the artwork theming all name other people's work. And expect the version numbers to tell you nothing about features, because the release titles are bare numbers with the occasional Hotfix suffix. ## FAQ ### How do I install BitChord on an Android phone? Download the latest signed APK from the Releases page. Sideloading it requires enabling Install unknown apps for whichever app you open the file with, and the file names no app store as an alternative channel. ### Does BitChord host or store any music files itself? No. The legal notice states that it does not host, upload or store copyrighted music, and operates strictly as an interface to scan local device storage or stream from public, public-facing or user-authenticated APIs. ### What does Automix do in BitChord, and is it ready? It performs DJ-style transitions with beat-matching and tempo-stretching, and it is the only feature in the list labelled Beta. Crossfade on the normal playback path is adjustable from 0 to 12 seconds. ### Which accounts does BitChord need me to connect? A Google account for personalized YouTube Music content, Discord for Rich Presence with its own in-app login showing track, artist, album and progress, and Last.fm or ListenBrainz if you want scrobbling. ### Where does BitChord's lossless audio come from? FLAC and ALAC come from a configured module source, with YouTube Music as the fallback. Module sources can be added, edited, tested and health-checked from inside the app, and per-network ceilings apply separately to Wi-Fi and mobile data. ### Under what license is BitChord released? GPLv3. The disclaimer notes that the license does not let anyone forbid others from selling or redistributing copies, and that any distribution must come with the Corresponding Source under the same license. ## Sources - [kushagrasinghx/BitChord on GitHub](https://github.com/kushagrasinghx/BitChord) - [License: GPL-3.0](https://github.com/kushagrasinghx/BitChord/blob/main/LICENSE) - [Project website](https://bitchord.kushagrasingh.in/) - [README](https://github.com/kushagrasinghx/BitChord/blob/main/README.md) - [Releases](https://github.com/kushagrasinghx/BitChord/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/kushagrasinghx-bitchord