YTubic YouTube Music Desktop Client Skips Webview for Direct API
A new open-source Windows app called YTubic launched today with a genuinely different technical approach to a problem Google has ignored for years: there is no official YouTube Music desktop client for Windows. Developer NUber-dev built the free, GPL-3.0-licensed app to bypass the sluggish webview wrappers that define most third-party alternatives, communicating directly with YouTube's internal API instead of loading the full website inside a desktop shell. Whether that architectural bet pays off in practice is still unproven, but the approach is distinct enough from what came before to be worth understanding.
Desktop frustration with YouTube Music has grown real enough that many users rely on browser extensions just to access basic playback controls, according to Android Authority. The space YTubic enters is not empty: YTMDesktop, Veltune, Tunecat, and Pear Desktop all exist. The interesting question is not whether another unofficial client launched, but whether its architecture changes what desktop YouTube Music can actually feel like for Windows users.
Why this YouTube Music desktop client for Windows takes a different approach
Most unofficial clients share the same foundational decision: render the YouTube Music website inside a desktop application frame. That is fast to build. It also inherits everything slow about the web app.
YTubic skips the web interface entirely. The app claims to communicate directly with YouTube's internal InnerTube API, pairs that with local caching and aggressive prefetching, and routes anonymous audio playback through yt-dlp, the widely used open-source media extraction tool, rather than through the YouTube Music web player, according to Android Authority. The developer says this eliminates the loading spinners and mid-session reloads that characterize the wrapper experience.
The contrast with existing clients is concrete. Pear Desktop loads the standard YouTube Music web interface inside a desktop window and layers integrations on top of it, as Audio File reported about six weeks ago. Veltune is a community-maintained fork of Pear that carries the same underlying wrapper design, per its GitHub repository. YTMDesktop's own FAQ acknowledges the app uses more than 300MB of RAM because Electron bundles a full Chromium engine, as cited by BrightCoding about four months ago.
No independent benchmarks existed at publication time to validate YTubic's speed claims. The architectural approach is real; whether it produces a meaningfully better daily experience remains to be seen.
What YTubic ships with and what it asks of your Google account
The feature set targets the gap between a browser tab left open and an actual desktop application. YTubic offers multiple layout modes: a dockable bottom bar, a right-side panel, and a floating always-on-top mini-player. It pulls line-by-line synced lyrics from LRCLIB, Musixmatch, and Genius, and automatically upgrades album artwork to high-resolution studio art where available, Android Authority reported.
Google account login is entirely optional. Anonymous users can browse and stream freely; signing in unlocks saved libraries, liked tracks, and personal playlists. The developer states the app collects no telemetry, per Android Authority.
Worth naming plainly: signing in with a Google account through any unofficial client involves different trust considerations than using the official website. These are not Google-sanctioned integrations. Guest mode limits that exposure. Tunecat, a cross-platform Tauri+Rust client published about three weeks ago, takes the same optional-login stance and explicitly routes audio directly from the user's machine to YouTube without proxying through developer servers; its account sign-in is capped at 100 users total because it is a small personal project, per its GitHub repository. YTubic does not publish a comparable routing disclosure, which is worth noting for users who care about that distinction.
How YTubic compares to the existing field
Performance. YTubic claims its direct API approach and local caching cut the sluggishness of webview wrappers. YTMDesktop and Veltune are Electron wrappers that bundle a full Chromium engine; YTMDesktop's own FAQ puts the resulting RAM footprint above 300MB, as cited by BrightCoding about four months ago. Tunecat uses Tauri+Rust, a lighter alternative to Electron, but still loads the YouTube Music web interface inside its shell, per the project's GitHub page.
Login requirements. YTubic and Tunecat both offer functional guest modes. Pear Desktop requires a Google account for normal use, as Audio File noted about six weeks ago. YTMDesktop's setup flow prompts for Google sign-in, though the available sources do not establish whether that is a hard requirement for all functionality.
Maturity. YTMDesktop has the deepest track record in the category. BrightCoding reported about four months ago that the project has attracted over 30 contributors submitting features including Last.fm scrobbling, Discord Rich Presence, custom CSS theming, and global hotkeys, and that its v2 codebase was a complete rewrite of the earlier version, per BrightCoding. That source reads as promotional, so those contributor figures are best treated as claims rather than verified data. Veltune's GitHub repository lists 2 contributors and last received a commit in mid-June, per the repository. YTubic's contributor history is too new to assess.
Platform support. YTMDesktop, Veltune, Tunecat, and Pear Desktop all run on Windows, macOS, and Linux. YTubic is Windows 10 and 11 only, per Android Authority.
Install friction. Veltune warns that Windows Defender SmartScreen may flag its installer as coming from an unknown publisher until code-signing is in place, per its GitHub repository. Whether YTubic's installer triggers the same warning is unconfirmed from available sources.
Users on Windows 10 or 11 who find wrapper-based clients frustrating and are comfortable with an early-stage project are the natural fit for YTubic. Users who want a longer track record, cross-platform support, or integrations like Last.fm scrobbling and Discord presence that YTubic does not currently advertise are better served by YTMDesktop or Veltune.
What would change the picture
YTubic's InnerTube API approach is a genuine structural departure from the Electron-and-webview pattern that every major competitor uses. That distinction matters, if the performance difference holds up under real-world conditions. Right now there is no independent data to confirm it does.
Two things would shift this conversation: public benchmark tests comparing YTubic's responsiveness against wrapper-based alternatives, or sustained GitHub activity that signals the project will keep pace with YouTube API changes over time. Until one of those materializes, the gap in the Windows YouTube Music ecosystem stays real, and projects like YTubic will keep making the case that wrapping a slow website was never the right answer.
Comments
Be the first, drop a comment!