This post is for our Paid Subscribers. If you haven’t subscribed yet,
Clarifying Questions
Before diving in, I would want to align on scope. There are several dimensions here that would dramatically change both the feature set and the regulatory framework, so let me surface the most important ones.
What age range are we targeting? This is the single most consequential scoping decision. Children under 13 fall under the Children’s Online Privacy Protection Act (COPPA) in the U.S., which imposes strict requirements on data collection, parental consent, and advertising. Teenagers aged 13 to 17 fall under a different, generally less restrictive regime but still require serious safety design. These two populations warrant fundamentally different products, and conflating them would be a serious design error.
Standalone product or a mode within existing WhatsApp? Meta already has directly relevant precedent here. Messenger Kids, launched in 2017, was built as a fully separate, parent-controlled product precisely because Meta concluded that adding a restricted mode to core Messenger or WhatsApp was architecturally insufficient for child safety. I would want to know whether we are repeating that same judgment or deliberately departing from it, and why.
What specific parental problem are we solving? Parents’ motivations vary considerably: keeping in touch with a child who does not yet have independent phone access, enabling communication with a small approved circle like grandparents and family friends, or displacing an unsafe alternative the child is already using. Each motivation implies a different prioritisation of features and onboarding design.
What is the primary geography for launch? COPPA governs U.S. users under 13, but the EU’s GDPR and the UK’s Age Appropriate Design Code (often called the Children’s Code) impose additional or sometimes stricter requirements. A global product needs a compliance architecture that satisfies the strictest applicable standard, which significantly affects engineering scope and timeline.
Is child safety a first-class, non-negotiable requirement from day one, or is it a post-launch addition? I want to name this explicitly because the industry track record of bolting safety onto products designed for growth is, frankly, poor. For this answer I am assuming safety is foundational, not retrofitted.
For this answer I will assume we are designing for children aged 6 to 12, following the same age range Messenger Kids uses, and that we are building a fully separate, parent-controlled product rather than a restricted mode within core WhatsApp. Core WhatsApp’s open contact-discovery, unmoderated group messaging, and end-to-end-encrypted architecture with no parental visibility are fundamentally incompatible with responsible design for this age group. Meta’s own decision to build Messenger Kids as an entirely separate product rather than a simplified WhatsApp mode reflects this same safety reasoning, and I would proceed under the same logic.
Product Description
WhatsApp is owned by Meta, which acquired it in 2014 for approximately $19 billion, making it one of the largest technology acquisitions in history at that time. As of 2024, WhatsApp has over 2 billion monthly active users across more than 180 countries, making it the world’s most widely used messaging application outside China. The product is free to end users and generates revenue primarily through the WhatsApp Business API, which charges businesses for customer messaging at rates ranging from roughly $0.005 to $0.09 per conversation depending on message category and region. WhatsApp’s core differentiation is end-to-end encryption by default, cross-platform availability, and near-ubiquitous penetration in markets including India, Brazil, Germany, and across most of Southeast Asia, Latin America, and Sub-Saharan Africa.
The children’s messaging space is a smaller but strategically meaningful category. Messenger Kids, the closest direct comparable, launched in December 2017 and had reached approximately 7 million users as of 2019, though Meta has not disclosed more recent figures. The broader children’s digital safety technology market is projected to reach $3.2 billion globally by 2026, growing at roughly 13 percent annually, driven by increasing parental concern about children’s unsupervised internet access. The U.S. Federal Trade Commission has issued COPPA enforcement actions totalling over $300 million in fines against companies including Google ($170 million in 2019) and YouTube, creating serious financial and reputational incentives for any company to treat child-safety compliance as a genuine priority rather than a checkbox.
The core design tension in this space is that the features that make adult messaging products successful (open contact discovery, frictionless network growth, broad reach) are precisely the features that make them unsafe for children. A genuinely safe children’s messaging product must invert the typical growth-oriented product philosophy, treating any connection outside a parent-approved circle as a safety failure rather than a missed growth opportunity. This is not a minor product adjustment. It is a fundamentally different design premise.
Define Goal
The core problem is that children in the 6 to 12 age range have genuine, legitimate social communication needs, including staying in touch with grandparents, family friends, and peers, but no existing messaging product designed for mass adoption safely serves them. General-purpose messaging apps built for adults create real child-safety risks when used by young children, and informal workarounds (giving a child a parent’s phone or an unrestricted account) provide inadequate, unreliable oversight.
The goal I want to focus on is building a messaging product that gives children in the 6 to 12 age range a safe, genuinely fun way to communicate with a small, parent-approved circle, while giving parents complete, reliable oversight and control, and maintaining full compliance with COPPA and equivalent global child-privacy regulations.
The north star metric I would use is weekly active child users who complete at least one parent-approved communication (message or video call) within a 7-day window, with zero unauthorized contact incidents in the same period. I prefer this compound metric over simple weekly active users because engagement without safety is meaningless for this product, and safety compliance without engagement means we have not actually served the child’s communication needs. Both dimensions must be true simultaneously for the product to be genuinely successful. A simple DAU or WAU figure, the typical metric for an adult messaging product, would be actively misleading here because it would mask safety failures.
User Segmentation
Parents
Primary parent administrators (ages 28 to 45, single-household): These are the core decision-makers. They research, download, configure, and monitor the product. Their trust in the safety architecture is the single determining factor in whether their child ever uses it. They skew toward higher digital literacy (they are evaluating a technology product for their child) but are deeply skeptical of tech-industry child-safety claims given years of well-documented failures. Retention risk is high if any safety incident occurs or if parental controls feel superficial.
Co-parents in separate households (ages 30 to 48): A segment with a specific, sensitive need: reliable, safe communication between a child and each parent across two households. This segment requires coordinated administrative access rather than assuming a single parental administrator, a nuance most competitor products handle poorly. Churn risk is high if coordination between co-parents is cumbersome or creates conflict over who controls settings.
Extended family contacts (ages 55 to 75, grandparents): Not administrators, but a critical adoption enabler. A grandparent who cannot easily connect with their grandchild after being approved undermines the entire value proposition. This segment needs the lowest possible technical barrier on the approved-contact side. Low churn risk once onboarded, but high drop-off risk at initial setup if the process is confusing.
Children
Early elementary children (ages 6 to 8): Limited reading ability, need heavy reliance on visual design, large touch targets, voice-first or sticker-first communication, and zero expectation of navigating settings independently. Primary use case is video calling grandparents and close family. No peer-to-peer messaging expectation at this age in most families.
Late elementary children (ages 9 to 12): More independent, beginning to have peer messaging needs, more likely to notice and care about whether the product feels “cool” compared to what peers use. This segment is where the tension between safety and social desirability is highest. Churn risk is elevated if the product feels babyish or lacks the sticker and reaction features children in this age band associate with messaging.
I will focus this answer primarily on the primary parent administrator and late elementary child (9 to 12) pairing, because this is where the product design tension is most acute (safety versus social desirability) and where getting the design right has the highest impact on adoption. A 9-to-12-year-old who genuinely wants to use the product because it is fun and feels age-appropriate, not just because a parent installed it, is the proof point that this product works.
