Product design: a kid-friendly way to create, store and recover passwords

Design a tool that helps children manage their passwords. Explain who it is for, the problems it solves and what you would build first. ```hint Let age set the design A six-year-old and a fifteen-year-old differ in reading, memory, independence and how involved a parent is. Decide which children you are designing for before deciding how signing in should work. ``` ### Clarifying Questions - Which ages should "children" cover: early readers, pre-teens, teenagers, or all of them? - Should this build on Google's existing accounts, Chrome, Android and family supervision tools, or be a standalone product? - When keeping accounts secure, teaching good habits and giving parents oversight pull in different directions, which comes first? - Does it need to work on shared family or school devices, or only on a child's own phone or tablet? ### What a Strong Answer Covers - A chosen age segment, and how that age's reading, memory and independence shape the design - The needs of the child and of the parent or guardian, and where they conflict - Features for creating, storing, filling in and recovering passwords, prioritized into a first release - Privacy, safety and legal limits that apply to minors, including how oversight changes as a child grows up - Success metrics with guardrails ### Follow-up Questions - A parent wants to see every password their 15-year-old saves. Would you allow it? Why? - How should the product hand control to a child who reaches the age at which they may manage their own account? - How would you tell whether the tool is teaching better security habits rather than just storing passwords?