Storkie

Product, 2026

Storkie started as an app for my wife and me. We had a newborn and were barely sleeping, and every baby tracker we tried was noisy, full of ads, and a little too interested in our son’s data. So I built our own, where we can both log sleep, feeds, diapers, growth, and photos and see each other’s entries right away.

I used it every day while I built it, and that shaped every feature. Voice logging is for when you have one free thumb at 3am. The “Up Next” forecast looks at today’s naps and wake-ups and suggests when the next nap should be. Ask Storkie is for the “is this normal?” questions you’d otherwise google at midnight.

It runs on the web and installs from the browser, so a tired parent can start logging without going through an app store. Grandparents get their own account as an editor or a viewer, so they can follow along too. Native apps built with Expo are in progress.

The rule behind all of it is that your kid’s data belongs to you. You can export it or delete it, and I don’t mine it or sell it. I’m user number one, and that’s the standard I want for my own son’s data.

Built with

TypeScript, Next.js, Supabase, React Native

storkie.app

What I decided

I went with hosted Postgres and hosted auth: Back when this was just an app for my wife and me, I picked Supabase because I wanted a hosted Postgres I could get running with almost no setup, and Clerk because its React components were the fastest way to get auth working. I’d weigh both differently if I started today, but migrating either one is expensive when you’re the only developer, even when something newer looks better. Billing is the exception. I was going to use Clerk for it, and I’m going with Stripe instead.

I built for the web first, and it cost me notifications: A progressive web app was the fastest path for me, since I know React better than React Native and I’d already built PWAs at work. It also meant a tired parent could start logging without going through an app store. The cost was reminders. I wanted feed and nap reminders, and the web couldn’t do them the way a native app can. I’m building native apps with Expo now, mostly so people can find Storkie in both app stores.

Ask Storkie only sees your kid’s data if you turn it on: Personalized answers are off by default, so you get general information, the same as you would from any chatbot. When you turn them on, Ask Storkie answers through tools that read your own logged activities, stats, and growth entries, so the answer is about your kid, and you can turn it back off whenever you want. Either way, it won’t give medical interpretations and points you to your pediatrician for those, and it only says it checked your logs when it actually did. When it doesn’t know something about your kid, it says so.

I made CI enforce the privacy rule: Every table that holds family data sits behind row-level security, and CI fails the build if one of them is missing a policy, so a new table can’t go out without one. You can export your whole account as JSON and CSV in a zip. When you delete something, Storkie keeps it for 30 days in case you tapped by mistake, and then a daily job deletes the rows and the photos for good.

I put off encrypting your data from myself: I wanted your kid’s data encrypted so that I couldn’t read it either, even with the database in front of me. It’s more work than the app needs right now, so I’ve set it aside for later. I’m saying so here because I don’t offer that guarantee yet.