Ad-free and offline: how HushBrush is built

HushBrush is a colouring and early-learning app for young children. Two decisions shaped everything else about it: no ads, and no internet required. Both cost us things, and both were the point.

Why no ads, in an app that could carry them

Children's apps monetise with ads because it works. We took the other route because of who the actual customer is.

The buyer is not the child, it is a tired parent handing over a phone for fifteen minutes. What they are buying is the confidence to stop watching. An ad breaks that instantly: it is a link out of the app, into something nobody vetted, at the exact moment supervision has been relaxed.

So there is nothing that can interrupt or redirect. No third-party ads, no pop-ups, no links out, no chat, no social feed. Once the app is open, the only thing in it is the app. That is the entire product promise, and a single ad unit would void it.

Offline is a feature, not a fallback

Most apps treat offline as a degraded state to apologise for. For this one it is the primary case.

Think about when a parent actually reaches for this: a car journey, a flight, a restaurant, a waiting room. Those are precisely the places with no usable connection. An app that needs a network to draw a letter is useless exactly when it is needed most.

So everything ships in the app and runs on the device. No loading spinner, no retry, no blank screen because a request failed in a car park.

Privacy by making data optional

The strongest privacy guarantee is not a policy, it is not holding the data.

Guest mode needs no account at all. Progress stays on the device. A parent can install it, hand the phone over, and never create anything — because for a children's app the safest default is to collect nothing and let the family opt in if they want more.

Signing in is optional and buys one thing: progress that survives a new device. That is a real benefit, so it is offered. It is not required, because requiring it would mean holding data on children who did not need us to.

This is also what makes compliance tractable. Designing for COPPA, GDPR-K and Play's Families requirements is a much shorter conversation when the honest answer to most questions is that the data never left the device.

The parent dashboard

The feature parents respond to most is not in the colouring at all. Behind a parental gate, a dashboard shows what actually happened: letters and numbers traced, colours learned, minutes of practice this week, pages completed, daily streaks.

We added it because of a specific guilt. Handing a child a screen feels like a small failure even when the app is good, because the time is invisible — you cannot tell whether anything happened. The dashboard makes it legible. Fifteen quiet minutes turns out to have been letter tracing and counting, and you can see it.

That is the difference between screen time you tolerate and screen time you feel fine about. Same fifteen minutes either way. The reporting is what changes how it feels.

What it costs

No ad revenue. No engagement loops, because the goal is a child who finishes calmly rather than one who cannot stop. No analytics-driven iteration on children's behaviour, because we do not collect it.

Every one of those makes the app harder to grow and easier to trust. For software aimed at four-year-olds, that is the right side of the trade.