Designing a First Phone for Children Under Five: Users, Safety and Metrics

Design a phone for children younger than five. Explain whom you are building for, which problems the phone solves for them, what the first version would include and leave out, and how you would judge whether it succeeds. ```hint Who uses it, who buys it Think about what a child of this age can and cannot do alone, and separate the person holding the device from the people who buy it, set it up and are on the other end of a call. ``` ### Clarifying Questions - Is the phone meant for the child to hold and operate, or for the adults who look after young children? - Must it be a handheld cellular phone the child carries, or could a wearable or a device that stays at home count? - What is the business goal: hardware sales, a recurring service, or something else? - Which country launches first, given that child-privacy and product-safety rules differ by market? ### What a Strong Answer Covers - The distinct users (the child, the parents who buy and control the device, and the family on the other end) and a justified age range within under-five - Needs grounded in what young children can do: not reading yet, small hands, rough handling, short attention and rarely being alone - A scoped first version with deliberate omissions and the trade-offs behind them, including the form factor - Safety, privacy, contact control and durability treated as requirements, plus a stance on screen-time concerns - Success metrics that do not simply reward more time on the device, with guardrails ### Follow-up Questions - Many parents and pediatric experts worry about young children and screens. Should this product exist, and how would you defend or change it? - How should the device handle emergency calls while avoiding accidental dials? - What happens to the product and the customer when the child turns six?