Parents don’t want controls. They want confidence.

The category is called “parental controls,” and I understand why. It is what parents search for, and what the market sells. But the longer I work on this, the less the word fits what I watch parents do.

They do want control sometimes — approve an app, set a limit, see a location, lock the device at night. Those needs are real. But when I listen closely, the job underneath is different. A parent wants to feel less alone in a decision they are already making, and mostly making badly, because the environment gives them no help. What they are reaching for is confidence.

Power comes from more switches. Confidence comes from fewer surprises.

That changes the bar. A control can be harsh or confusing and still technically work. Confidence cannot. It needs the parent to know what will happen and the child to feel the boundary as predictable. So the design question stops being “how many things can a parent configure” and becomes “how few decisions can we force on them to reach a setup that is safe and that they actually understand.”

I keep pushing back on configurability for that reason. Every family is different, so letting parents tune everything sounds respectful. But too many knobs is its own kind of abandonment. It tells a parent: you supply the philosophy, we will hand you the dials. For a product about kids, that is not neutral. It is a dodge.

So I think the product has to have a point of view — not a rigid one, not a theory of parenting, but enough that the safest, most understandable path is the easy one, and a parent does not have to become a policy designer to get through setup. That is the real weight of a default. More than the state that holds until someone customizes, a default is the company's first answer to what is reasonable for a child. We do not get to be neutral about that. We are answering whether we choose to or not.