Aastha Shree. ← Back to portfolio

Case study · Sprout (personal project)

A reading app that
earns a parent’s trust.

A privacy-first reading app for young children — where making it good and keeping it trustworthy were never two separate problems.

Role  Product & build (solo) Stage  Live two-week pilot Platform  Mobile web · add to home screen
On-device
only
data never leaves the child's phone
0accounts, logins, or sign-ups
1external call — a single dictionary lookup
NoApp Store — added from the browser

Why I built it

Reading is the highest-leverage habit you can give a young child. Yet most apps built for young children pay for themselves with data collection and advertising — exactly what a parent does not want near a five-year-old. I wanted to find out whether a genuinely trustworthy one could exist: good enough that a child wants to read, clean enough that a parent never has to think about it.

The interesting part was realising the product decision and the privacy decision were not two decisions. They were one.

The bet

Most apps promise privacy in a policy document. I wanted Sprout to be trustworthy by architecture: safe because it cannot misuse data, not because it promises not to. No account and no server means nothing to leak, sell, or lose — and that one constraint shaped every screen that followed.

“Make it impossible to misuse the data, and you no longer have to ask a parent to trust a promise.”

The product decisions

01

On-device only

No account, no login, no server. Everything a child does — the books, the minutes, the words, the stickers — lives on that one phone and nowhere else. Delete the app and it is genuinely gone.

02

One exception, named out loud

Exactly one thing leaves the phone: when a child taps a word, that single word goes to a dictionary to fetch its meaning — with no name, no device ID, not even which book it came from. Saying so plainly is part of how the product earns trust.

03

Skip the App Store

Sprout is added straight from the browser to the home screen. That removes a gatekeeper and a download, lets fixes ship instantly, and sidesteps a whole layer of store-level data requirements — at the cost of an onboarding step I had to get right.

04

Make reading its own reward

A child picks an avatar and a reading name, fills a “word jar” as they collect new words, and earns stickers. The motivation is built into the reading itself — not into streaks, nudges, or notifications.

05

Hand control to the grown-up

A separate grown-ups area holds setup, a one-tap “erase all data,” and a “save a copy of the data” export so the parent — not me — owns whatever the child created.

06

Hard safety rails

No ads. No outbound links. No messaging, photos, or notifications. No comparing one child against another. The things a kids' app is usually pressured to add are the things Sprout deliberately refuses.

What shipped

The pilot, honestly

Sprout is in a live two-week pilot, so there are no outcome numbers yet — and I would rather earn them than invent them. What I am watching for:

What I am already learning

The hardest problem is not the reading experience — it is the very first minute. On an iPhone, a browser bookmark can masquerade as the installed app and quietly break the full-screen experience, so the onboarding has to be unusually clear about the difference. It is a good reminder that a privacy-first, no-App-Store choice buys trust and control, but spends some of that back at the front door. The next iteration focuses there.

My role

Solo. I owned the problem, the product decisions, the user experience, and the build itself, using AI-assisted development tools to go from idea to a live pilot. Sprout is where I get to practise the whole craft end to end — and to hold a product to a standard of data ethics I would want for any child.

Try it, or talk it through?

The pilot is open, and I am always happy to walk through the decisions behind it.

Open Sprout ↗ Back to portfolio