Why We Built Kinder Browser

Every product we have made began with a problem inside our own home. Kinder Browser began with one of the simplest: our daughter wanted to use the web to learn, and we could not find a browser we felt comfortable handing her. So we built one. This post is about the thinking behind it.

The web is one of the greatest learning resources humanity has produced, and it was designed, overwhelmingly, by adults for adults. Pages assume the reader can judge what is worth clicking. Ads are engineered to pull attention away from the content. Links lead to links lead to links, and within a tap or two a young child can land somewhere no parent would have chosen for them. None of this means the web is bad. It means the web, as it stands, was not designed with a five-year-old as its audience. When we looked for a browser that acknowledged this, one made for a young child’s educational web surfing rather than a lightly padded version of an adult browser, we could not find one that satisfied us. That gap became Kinder Browser.

Most parental-control tools take the filtering approach: the entire web is open, and a blocklist tries to catch the bad parts. We chose the opposite. In Kinder Browser, nothing opens unless a parent has approved it. The reason is arithmetic as much as philosophy. A filter has to be right about a web of effectively unlimited size that changes every day, and every site it misjudges appears on your child’s screen. An allowlist only has to be right about the handful of sites you chose yourself. You can read your child’s entire web in one glance at the list.

There is an honest tradeoff here. With a default-deny allowlist, a young child sees far less of the web. For the age group Kinder Browser serves, I believe that is not a limitation but the point. A deep session with Scratch teaches more than an hour of wandering. And because external redirects are blocked as well, the boundary holds even inside approved sites. A stray link cannot lead anywhere the list does not.

We also did not want to build a children’s product that negotiates with advertising. Ads are, by design, machines for redirecting attention, which is precisely the thing a child learning to focus does not need. In Kinder Browser, intrusive site ads are blocked by default. This is not a premium option or a toggle buried in settings. It is simply how the browser works.

Kinder Browser does not track your child, and it does not collect data. It is a one-time purchase with no subscription. That choice is also about incentives: a product paid for once, with no data to monetize, has no reason to maximize your child’s time in the app or to know anything about them. We only need the browser to be worth its price. We find that alignment easier to trust, and we built the app we would want to be asked to trust.

Everything else followed from watching a child actually learn on the web. The screen stays on during use, so a half-built Scratch project is not interrupted by a darkening display. A doodling feature keeps a bit of play within reach. Settings live behind a parental gate, and the app works alongside Screen Time, so it slots into the rules a family already has.

What do we hope it feels like? Calm, mostly. A parent approves the sites they trust, hands over the iPad, and thinks about something else. A child explores freely inside boundaries drawn by someone who loves them. If that sounds like your household, Getting Started with Kinder Browser walks through the first setup, and Who Is Kinder Browser For? may help you decide whether it fits. More posts live under the kinderbrowser tag.

If this way of thinking resonates with you, we would be glad to have Kinder Browser in your family’s toolkit.