Product Sense: Designing the Mobile Experience Around a Toy Remote-Control Car

Design a mobile app for a toy remote-control car. Explain who the app is for, what it should do, and how you would judge whether it succeeded. ```hint Find the app's reason to exist Ask what a phone can add that the car's own remote cannot, and for whom. Keep in mind that the person who buys a toy is often not the person who plays with it. ``` ### Clarifying Questions - Should the app replace the car's physical remote, work alongside it, or offer both? - Are we the toy maker building an app for our own cars, or a software company building one app for cars from many makers? - Who is the main driver: a young child, an older child or teenager, or an adult hobbyist? - What can the car do today: connect to a phone, carry a camera, or report its speed and battery level? ### What a Strong Answer Covers - A goal tied to the business, and a chosen segment that separates the buyer from the player - The pain points that segment has with toy remote-control cars today - A focused, prioritized first release that respects what the car's hardware can do - Safety, children's privacy and parental controls built into the design - Success metrics, guardrails and the main risks ### Follow-up Questions - After launch, most children stop opening the app within a couple of weeks of getting the car. What do you change? - How would the design change if the car had a front-facing camera? - Would you charge for the app or for anything inside it, and how would that affect parents' trust?