Design a kid-safe music listening app for young children and their parents

Design a music service for children. Decide which children you are designing for and which adults around them matter, what problems they have with music today, what the product does in its first version, and how you would measure whether it succeeds. ```hint The listener is not the buyer A child listens, but a parent usually installs the app, pays and sets the rules, and each wants something different. Choose an age band and ask what children of that age can and cannot do on their own before you list features. ``` ### Clarifying Questions - Which age range are we designing for: preschoolers who cannot read yet, primary-school children, or children close to their teens? - Is this a new standalone product, or a children's experience inside a music or video service Google already runs? - What is the business goal: new paid subscriptions, more families joining an existing family plan, or engagement? - Which devices should it work on: a parent's phone, a shared family tablet, a smart speaker, or a child's own device? ### What a Strong Answer Covers - A product goal and a chosen age segment, with parents treated as a second user whose needs differ from the child's. - Pain points specific to children and music, such as unsafe content, discovery suited to the age, navigation for children who cannot read, and screen-time worries. - A prioritized first version, with the reasoning behind what is left for later. - Success metrics with guardrails on child safety, privacy and healthy usage. - Risks such as children's data-protection rules, filtering mistakes and content licensing. ### Follow-up Questions - How would you find out that inappropriate songs are slipping through, and what would you do when one does? - Would you let children share playlists or follow friends? Why or why not, and would your answer depend on age? - How should the product change as a child grows from about age 6 to age 12?