“Design a kids’ educational app” is a regulated-industry mobile system design — Khan Academy Kids, Duolingo ABC, ABCmouse, Lingokids, Yousician for Kids. The interview tests whether you understand COPPA, the profile-and-parental-controls model, and the unique product-engineering of an ad-free, child-safe experience.
Clarify scope
- Age range? (3–6 vs 6–10 vs 10–13 are very different)
- Subjects: literacy, math, language, music, broad?
- Single-child or family with multiple kids?
- Free, freemium, subscription?
- Parent dashboard for progress?
COPPA and global child-data law
- US COPPA: under-13 users require verifiable parental consent for data collection
- EU GDPR-K: similar; specific age varies by member state (13–16)
- UK Age Appropriate Design Code: more prescriptive on data minimization
- India DPDP, Brazil LGPD: increasingly aligned
Implementation: the parent creates the account; the kid uses a profile under that account; data minimization is the default.
Profile model
- Parent account (verified adult; email, payment, parental-consent record)
- Child profiles (name, age, avatar; minimal data)
- Each child has independent progress
- Switching profiles: PIN gate or quick-tap on small screens
Parental gate
- Required for all account-management actions
- “Tap and hold the green circle for 3 seconds” — easy for parent, hard for child
- Or: math problem (“What is 7 + 6?”) — common in kids’ apps
- Used before purchases, settings, account changes
Time limits
- Per-child daily time cap, set by parent
- “Time’s up” friendly screen at end
- Visible countdown for older kids
- Parent override (15 more minutes) requires gate
- Integration with iOS Screen Time / Android Family Link is helpful but not sufficient
Content engine
- Lesson tree per subject and age
- Adaptive difficulty: success rate adjusts next lesson
- Replayable activities (kids enjoy repetition)
- Streak / star reward systems (carefully designed; avoid manipulative dark patterns)
Audio and voice
- Most lessons are voice-led — pre-recorded narrator audio
- Speech recognition for reading practice (on-device for privacy)
- Subtitles for accessibility / quiet-mode
- Multiple language support
Offline-first
- Lessons downloadable; works without network
- Sync progress on reconnect
- Critical for car / plane / waiting-room use
- Storage management with parent-visible usage
Ads and monetization
- Ad-free is the standard expectation; ads in kids’ apps are heavily restricted
- Subscription is the dominant model
- Trial period with parental gate at conversion
- Purchases require parental gate every time
Privacy and analytics
- No third-party advertising trackers
- Analytics minimal: completion events, no PII
- No social features that could enable contact with strangers
- If chat is in scope (uncommon), pre-approved messages only
Parent dashboard
- Per-child progress: lessons completed, skills learned, time spent
- Recommendations: “Try music next” with reasoning
- Email weekly summary
- Manageable from parent’s device or web
Accessibility
- Big touch targets (kids’ fingers)
- Strong contrast and readable typography
- VoiceOver / TalkBack work
- Reduced-motion mode for kids with sensory needs
- Multiple language support
Family sharing
- iOS Family Sharing for the subscription
- Per-child profile across siblings’ devices
- iCloud / Google sync of profile data within the family
Performance
- Audio prefetch for upcoming lessons
- Optimize for low-end iPad and Android tablet
- Battery-aware: avoid running heavy ML continuously
- Memory: kids stay on the app for long stretches; do not leak
Edge cases interviewers love
- Two siblings using the same iPad — fast profile switch
- Birthday triggers an age-bracket promotion (different content unlocks)
- Parent revokes consent mid-trial — graceful exit, data deletion
- Network drops mid-lesson — finish locally, sync later
- Foreground / background transitions — pause music, do not lose progress
What separates senior from staff
Senior candidates handle the profile model and offline lessons. Staff candidates address the COPPA / global compliance posture, the parental-gate UX, and the time-limit / adaptive-difficulty engine. Principal candidates raise the global-region content adaptation, the subscription pipeline with family-sharing, and the analytics-minimization story.
Frequently Asked Questions
How do I verify parental consent?
Credit-card swipe (the “small charge” trick) is acceptable under COPPA. Email verification + later confirmation works for some flows. Government ID is overkill for most use cases.
Can I use third-party SDKs?
Be very careful. Many SDKs collect data not allowed under COPPA. Evaluate each; prefer self-built or COPPA-compliant alternatives. Review SDK Privacy Manifests on iOS.
What about teen-specific apps (10–13)?
Caught between kids and adult product surfaces. Most companies treat the 10–13 segment with similar controls but slightly more independence (longer time limits, broader content).