Letting Children Aged 10 to 16 Order Food on Swiggy: Product Design

Swiggy, the Indian food delivery app, wants an experience designed for young users aged 10 to 16. Design it. ```hint Who orders, who pays, who receives Think about who places, pays for and receives an order when the user is a child, and whether a 10-year-old and a 16-year-old need the same things. ``` ### Clarifying Questions - What does Swiggy want most from this: more orders, more trust from families, or future adult customers? - Does the experience cover only restaurant delivery, or also Swiggy's grocery and quick-commerce orders? - Must a parent or guardian be involved in every order, or may older teens order on their own within limits? ### What a Strong Answer Covers - A clear goal for Swiggy, and a segmentation that separates younger children, older teens and the parents who pay - Concrete situations in which a 10-to-16-year-old would order, with the pain points in each - Safety, payment, nutrition and children's privacy treated as core design requirements, including India's rules on processing children's data - A prioritized first release, with what is deliberately left out - Success metrics with guardrails for safety and parents' trust ### Follow-up Questions - A parent complains that their 12-year-old ordered fried food every day for a week, all within the approved budget. How should the product respond? - How would you confirm that the adult approving a youth account is really that child's parent or guardian? - Would you show restaurant promotions and offers to these users? Why or why not?