SmartTube: A YouTube Client for Android TV That Skips Google Services

The Problem SmartTube Targets: YouTube on a TV Without the Official App's Terms

The README describes SmartTube as "a free and open-source media client for Android TVs and TV boxes" that lets you "browse and play content from various public sources in a TV-optimized interface." That sentence is doing a lot of work. The project is not a general media player in the VLC sense. It is a client built around a TV remote, a ten-foot interface, and playback of online video sources, with the feature list naming SponsorBlock integration, adjustable playback speed, 8K resolution support, 60fps playback, HDR compatibility, live chat viewing, and customizable buttons. One line in the feature list is the real positioning statement: "Does not require Google Services." On a Fire TV Stick or a cheap Android TV box, the official YouTube app pulls in Play Services and a Google account. SmartTube's audience is the person who wants the content without that dependency, and who is willing to trade the app store for a sideloaded APK. The device support section is explicit about who that is: "all Android TVs and TV boxes (incl. All FireTV devices released before Oct. 2025, NVIDIA Shield & Chromecast with Google TV), even older ones with Android 4.3 (Kitkat)." The Android 4.3 floor matters. It means hardware from roughly 2013 onward is in scope, which is unusual for a client still receiving beta builds in 2026.

How the Sideload-Only Distribution Model Works

There is no Play Store listing, and the README is blunt about why that matters: "Do not download SmartTube from any app store, APK websites or blogs; these were uploaded by other people and may contain malware or ads. SmartTube is not officially published on any app store." Distribution runs through two channels. The first is F-Droid, via the badge linking to f-droid.org/packages/app.smarttube.fdroid. The second is GitHub releases, with direct URLs for the beta and stable APKs. The README also points to short links, kutt.to/stn_beta and kutt.to/stn_stable, which are entered into the Downloader by AFTVnews app on the TV itself. That is the easiest path the documentation offers: install Downloader, type the short link, confirm the security prompts. Alternatives listed are transferring an APK from a phone or computer with an app such as Send Files to TV, or copying it to a USB stick and using a file manager like FX File Explorer or X-plore. The README warns that Android's preinstalled file manager does not work for this. For advanced users, ADB sideloading is documented with two external guides. The app ships a built-in updater with a changelog, so once installed, version bumps do not require repeating the sideload dance.

Beta and Stable Tracks, and What the Release Cadence Implies

SmartTube maintains two release channels, and the README recommends the beta: "Beta gets new features and bugfixes faster than the stable release." The supplied release list shows what that looks like in practice. Version 32.45 was tagged as a beta on 2026-09-07, 32.38s as a stable on 2026-09-01, and 32.38 as a beta on 2026-08-31. So the stable build trails the beta line by roughly a week in this snapshot, and the beta line advances in small increments. The naming convention is worth noting: the stable release carries an s suffix (32.38s) while the beta of the same number does not. Anyone scripting an update check against the GitHub releases page needs to parse that suffix rather than assume the highest number is stable. The changelog lives on the Telegram channel @SmartTubeNewsEN, which the README notes is readable without a Telegram account, and on the GitHub releases page. For a project whose installation instructions warn about tampered APKs, having two independent places to read release notes is a reasonable check.

Documented Limitations: Phones, Comments, Voice, and Casting

The README keeps its limitations list short and unusually direct. "Not supported on phones and tablets" is the first entry. That is not a soft recommendation; the app is built for a remote-driven TV interface, and the device support section repeats it under Not supported, alongside non-Android platforms like Samsung Tizen, LG webOS, and Apple TV. The second limitation is "Comment functionality is unstable." The documentation does not say which parts of commenting break or how often, so treat that as an unresolved area rather than a known-bad feature with a workaround. Third, "Voice search and casting performance may be inferior to official apps, depending on your device." That phrasing puts the variance on hardware, which is plausible for a client that does not use Google Services, but it also means the project is not making a performance claim it can stand behind across devices. The Fire TV situation is a separate, harder boundary. The README states that starting in October 2025, new Amazon FireTV devices no longer run Android under the hood, and SmartTube "will not be compatible with the Fire Stick 4k Select and newer devices which run Amazon's own VegaOS." Anyone buying a Fire TV device today should check the OS before assuming SmartTube will install.

The Supply-Chain Disclosure in the README

The most unusual part of this repository is the announcement at the top. The maintainer states that the development environment "was infected by unknown malicious software, as a result of which a few builds may have been affected." The stated response was a full disk wipe, a clean setup, and VirusTotal scanning of all builds, with the F-Droid version also verified before release. The README adds that "public keys may have been compromised" and that new versions and a new public key are being shared, with instructions for restoring backups. This is not a routine security note, and it is the single most important thing to read before installing. The mitigating detail the project offers is that the app uses one-time connection codes with limited permissions, which "cannot change your password." The README provides a revocation path: open myaccount.google.com/security, find "Your connections to third-party apps & services," tap "See all connection," locate YouTube TV or Google Drive, and select "Remove access." Whether that is sufficient depends on your threat model, but the project has at least documented the incident and the recovery steps rather than burying them.

Building From Source and What the Java Codebase Implies

The repository is primarily Java, with Kotlin and the retrofit2 and rxjava-android topics indicating the networking and reactive layers. The README includes a Build section in its navigation, though the README does not include its contents, so the exact Gradle commands and SDK requirements cannot be confirmed here. What can be said from the layout is that the app ships as APKs named smarttube_beta.apk and smarttube_stable.apk, and the source tree includes a smarttubetv module with per-flavor resource directories (the commented-out logo path in the README references smarttubetv/src/ststable/res/mipmap-nodpi/app_icon.png, where ststable appears to be the stable flavor). Building it yourself is the only way to avoid trusting the released binaries, and given the compromise disclosure, that option has more weight here than it would for a typical Android app. The trade-off is that a self-built APK will not receive the built-in updater's changelog or automatic version checks unless you wire that up yourself. The README also links a community translation tool for android-strings.xml, which suggests localization is handled through string resource files rather than a hosted translation platform.

Licence and Maintenance Cost Under MIT

The project is MIT-licensed, which is permissive: you can fork it, modify it, and redistribute it, including in closed products, provided the copyright notice and permission notice are retained. That matters for anyone considering a rebranded build for a fleet of TVs. It does not, however, transfer any responsibility for the content the client plays, and the README's Liability section exists for that reason; its exact text cannot be quoted here. On maintenance cost, the practical burden falls on the user, not a vendor. There is no managed update service. The built-in updater handles version bumps, but the initial install, the choice between beta and stable, and the response to a security disclosure are all manual. The release cadence in the repository (a beta on 2026-09-07, a stable on 2026-09-01) suggests the project is active, but activity is not the same as support. There is no stated SLA, and the README points questions to a community chat rather than a ticketing system.

Where SmartTube Is the Wrong Tool, and What to Use Instead

If your device is a phone or tablet, SmartTube is not an option, and the README says so plainly. The obvious alternative there is the official YouTube app, which is available on the Play Store and handles account features, comments, and casting without sideloading. The difference in approach is not just distribution. The official app requires Google Services and a signed-in Google account; SmartTube's feature list explicitly advertises that it "Does not require Google Services." That is the whole trade. You give up app store updates, comment reliability, and possibly voice search and casting quality, and you get a TV interface that runs on Android 4.3 hardware without Play Services. For a TV box owner who wants SponsorBlock and adjustable playback speed on a device the official app has abandoned, that trade is the point. For a household that relies on casting from phones and expects comments to load, it is the wrong choice. A second alternative worth naming is simply buying a device that still runs Android, since the README's VegaOS note means the newest Fire TV hardware is a dead end for this project regardless of software.

Editorial conclusion

SmartTube is for people who already own an Android TV or TV box released before October 2025 and are willing to sideload an APK and accept an unstable comment section. It is not for phones, tablets, Samsung Tizen, LG webOS, Apple TV, or the Fire Stick 4K Select and newer VegaOS devices. Before installing, verify three things: that the APK came from the GitHub releases or F-Droid page and not an app store or APK blog, that the device runs Android 4.3 or later, and that you are comfortable with the project's own disclosure that its development environment was infected and that public keys may have been compromised. The README's revocation steps at myaccount.google.com/security are the concrete fallback if a one-time connection code was issued.

Official sources

1. License: MIT
2. Project website
3. README
4. Releases
5. yuliskov/SmartTube on GitHub