All tools
Music & audio

CAN I VIBECODE

YouTube Music Premium?

NOT REALLYA prototype of the interface is possible, but the durable product depends on difficult systems beyond the UI. Build a safer adjacent workflow instead.

BUILD FIRST

  1. A non-sensitive or read-only version of the core experience
  2. A manual review step wherever correctness or trust matters
  3. A narrow companion tool that removes a real piece of work

LEAVE FOR LATER

  1. Regulated decisions, payments, or irreversible actions
  2. Claims of correctness, compliance, or uptime that the MVP cannot support
  3. Sensitive integrations until security, support, and auditability are ready

RESEARCH NOTES

What this tool actually does.

Checked 2026-09-06

YouTube Music Premium (paid subscription, distinct from the free YouTube Music tier) adds ad-free playback of songs and music videos, background play on mobile when the screen is off or other apps are open, audio-only mode that streams sound without loading video, downloads for offline use valid up to 30 days, Smart Downloads that auto-fetch content from listening history, shuffle-all-downloads playback, and casting to speakers/TVs via the web app. It also includes podcasts (ads may still appear on podcasts), and supports 'traveling members' for up to 6 months outside the home country, with downloads working 30 days offline (podcast downloads US-only). Premium benefits apply in the YouTube Music app only, not in other apps or services. Subscription is available in many countries/regions.

RESEARCHED BUILD PROMPT

Give this to your coding agent.

Build a web-based replacement for the paid-tier features of YouTube Music Premium. Workflow: a user signs in, searches/browses a music catalog, plays songs or music videos, and toggles Premium capabilities: ad-free playback, background play (audio continues when tab/app is inactive), audio-only streaming mode, offline downloads valid for 30 days with a 'Smart Downloads' auto-fetch toggle based on listening history, shuffle-all-downloads playback, and casting to a simulated speaker/TV target. Requirements: user accounts with subscription state enforcement; a media player with persistent audio playback across route changes; an IndexedDB/OPFS-based download cache with expiry timestamps; a casting interface that transfers playback state to a separate client session; admin tools to seed catalog content. Suggested stack: React or Svelte front-end, HLS or Web Audio for streaming, Web Worker for background playback, service worker for offline caching, Node/Python API with SQLite for subscriptions and listening history. Do not copy Google's brand, logo, layout, color scheme, or YouTube Music UI. Out of scope: real payment processing, podcast content, physical Chromecast/hardware device discovery, mobile native apps, and country/region restrictions. Include a README explaining setup, architecture choices, and known limitations (e.g., background playback on mobile browsers is constrained by OS).
Visit the official product page