Adapting Google Maps navigation for young children and their parents

Design a version of Google's Maps product made for children. ```hint Age decides everything A five-year-old and a twelve-year-old would use a map for very different reasons, and in both cases a parent decides whether the child gets it. Settle the age and the job before any features. ``` ### Clarifying Questions - What age range should I design for, and does it include children old enough to walk to school or to a friend's house on their own? - Is this a separate app, or a mode inside the existing Maps app that switches on for a child's supervised account? - Is the main purpose getting from place to place safely, learning about places and geography, or both? - Will the child use their own phone, a shared family device or a smartwatch? ### What a Strong Answer Covers - A chosen age band and core job, with parents treated as co-users who approve and set limits - Why current maps fail that child (abstract map views, distance-based directions, typing) and what the parent worries about - Prioritized features that make navigation workable for a child and give parents control without constant surveillance - Metrics that reward safe, completed trips rather than time spent in the app, with safety and privacy guardrails - Children's privacy and safety risks, including parental consent rules and features deliberately left out ### Follow-up Questions - How would you choose a route that is safe for a child to walk or cycle, and what data would you need that a fastest-route algorithm ignores? - A parent wants to see the child's location at all times, and the child finds that intrusive. How do you design for both? - Would you let children share favorite places with friends? Why or why not?