Design a food delivery app for kids.
This is a design question with a hidden constraint. Kids are the users, but parents pay and carry the risk. A good answer designs for both and picks one to lead.
Step 1. Clarifying Questions
- What age? A 6 year old and a 14 year old are different products. Assume 8 to 12.
- Who orders: the kid alone, or the kid with the parent watching? Assume the kid orders, the parent approves.
- What occasion? Snacks after school, school lunch, weekend treats? Assume all, starting with after-school snacks.
- Standalone app or a mode inside Swiggy/Zomato? Assume a kids mode inside the main app, so we reuse restaurants and riders.
Step 2. Why it matters
Kids already influence a large share of family food orders. A kids mode builds habit early and gives parents a reason to trust the platform with their children.
Step 3. User segments
- Kids (8 to 12): want fun, choice, and to feel independent.
- Working parents: want their kid fed safely while they are at work.
- Restaurants: want a new occasion and repeat orders.
Prioritise working parents with kids at home after school. They have the clearest pain and they hold the wallet.
Step 4. Pain points
- As a working parent, I don't know what my child ate this afternoon, and I worry about junk and allergens.
- As a working parent, I can't hand my card to my child, and I don't want surprise bills.
- As a working parent, I'm nervous about a stranger delivering to my child alone at home.
- As a kid, menus are long and full of words, and I don't know what I'll like.
- As a kid, I want to choose for myself, not just eat what was ordered for me.
Step 5. Solutions
1. Parent-set wallet: a weekly budget, approved restaurants, and blocked items. One-tap approval on the parent's phone.
2. Kid-safe menu: allergen filters set once by the parent, portion sizes for kids, a healthy-choice badge.
3. Picture-first ordering: big food photos, few words, a "build your plate" game for combos.
4. Safe handover: deliveries only to the saved home address, an OTP the kid reads out to the rider, and live tracking for the parent.
5. After-school subscription: the parent sets 3 meals a week, and the kid picks from a short list each day.
Prioritise (impact vs effort): 1 and 4 first. Without spend control and safe delivery, no parent turns this on. Then 2. Then 3 and 5.
Step 6. Metrics
- North Star: weekly approved kid orders per active parent
- Adoption: % of parents who set up kids mode, time to first approved order
- Trust: parent rejection rate, safety complaints per 1,000 orders
- Guardrail: % of orders from the healthy-choice range (we should not become a junk food channel)
Interview tip: name the tension early. The user (kid) and the customer (parent) want different things. The design is how you resolve it.
Community Answers (0)
No answers yet. Be the first to share your approach!