Standalone Music App Decision for YouTube: Strategy Call and Experience Design

You are a product manager at Google working on YouTube. The question in front of you is whether YouTube Music should be offered as its own app, separate from the main YouTube app. Make the call and explain it. If your answer is yes, design the experience of that separate app. ### Clarifying Questions - Should we treat this as a decision made before any standalone music app exists, or as a review of whether a separate app should keep existing? - What matters most to the business: paid subscriptions, total listening time, or holding ground against dedicated music services? - Is the scope worldwide and across phones, desktop, smart speakers and cars, or one launch market and platform first? - Which content can the separate app carry: only officially licensed tracks, or also YouTube's live performances, covers and remixes? ### Part 1 — Decide whether to launch a separate app Recommend whether YouTube should launch a dedicated music app. Lay out the case for and against, the criteria you use to decide, and the conditions that would change your mind. ```hint Listening is not watching Compare how people listen to music with how they watch videos: what the screen is doing, how long a session lasts and what happens when the phone is locked. Then weigh what a second app costs YouTube. ``` #### What This Part Should Cover - The behavioral differences between music listening and video watching that one app struggles to serve. - The business case: competition with dedicated music services, subscriptions and licensing. - The costs: splitting the audience, cannibalization, duplicated work and user confusion. - A clear recommendation with the evidence that would reverse it. ### Part 2 — Design the standalone experience If you recommended a separate app, design it: who it is for, their main listening jobs, the core screens and flows, how it connects to the main YouTube app, and how you would measure success. ```hint Design for eyes elsewhere Much music is played while the listener's eyes and hands are busy. Design for those moments, and ask what YouTube's catalog offers that no other music service has. ``` #### What This Part Should Cover - Target users chosen deliberately, with their listening jobs. - Core flows: playback, library, discovery, offline and background listening, and moving between audio and video. - Differentiation from established music apps, and the bridge to the main YouTube app. - Success metrics with guardrails. ### What a Strong Answer Covers - A decision that follows from user behavior and business goals, not an assumption that a dedicated app is always better. - Consistency between the parts: the reasons for separating show up as concrete design choices. - Use of YouTube's distinct assets while protecting the main app's music experience and revenue. - Risks such as cannibalization, cold start and licensing limits, with a launch and migration plan. ### Follow-up Questions - Six months after launch, most music listening still happens in the main YouTube app. What do you do? - Once the separate app exists, how should music behave inside the main YouTube app? - How would you decide whether podcasts belong in the music app or in the main app?