Skip to main content

A Baby Tracker Built for 3am

Client

Little Logbook (our own product)

Industry

Health / Family

Tech Stack

React NativeExpoTypeScriptPostgreSQLDrizzle ORMRailwayPWAPostHogRevenueCat

Timeline

In private beta with six families, 2026

1,859feeds logged by six families, most of them one-handed in the darkLittle Logbook, counted across every family schema, 26 August 2026
3,433entries in total: feeds, nappies, pumping and sleep, on a product that has not launched yetLittle Logbook, 1,859 feeds, 1,259 nappies, 264 pump entries and 51 sleeps, 26 August 2026
01

The problem

It started with a baby in neonatal care and a parent trying to keep track of feeds on a phone, at night, in a room where you do not want a bright screen.

Every tracker on the market gets one of two things wrong. The clinical ones open on dense tables and charts. The pastel ones open on a cartoon mascot and a streak counter. Both assume two hands, good light and a working signal, and most of them rent a family their own data back.

And nothing handled the start we actually had. A baby who spent weeks in neonatal care is not the same age as the calendar says, so every milestone, every centile and every “is this normal yet” question is measured against the wrong clock.

02

What we built

A calm, private record of feeds, nappies and sleep, designed for one hand in a dark room and a phone with no signal.

Dark by default, one-handed, repeat the last entry
The 3am feed is the whole design brief. No login to fail, a shared PIN, and each device stamps who logged it so two parents never argue about whether it was done.
Neonatal care is asked once, gently, and never again
One optional question at signup, per baby rather than per family because twins can have different starts. Answer it and corrected age quietly becomes the clock every milestone runs on. Never inferred from gestation: term babies go to neonatal care and some preterm babies never do.
It works with no signal
Writes are idempotent against a client-generated ID and queue in an outbox. Hospital corridors and 3am nurseries are exactly where the bars disappear.
Every family gets its own database schema
Not a tenant column that one missing WHERE clause defeats. Backups run continuously and a single-family restore has been rehearsed and written down, because this is a record of somebody’s child.
The AI answers from this baby’s own records
Not generic advice with a chat box on it. And the delete is a real ceremony: object storage is purged before the database row, so leaving takes the photos too.
03

What it did

  • Six families using it daily through pregnancy, neonatal care and the first year
  • Growth plotted against RCPCH UK-WHO centiles, descriptive only and never diagnostic
  • Self-serve export, so a family can take the whole record and leave
  • Continuous point-in-time backups with a drilled single-family restore runbook
  • iOS app plus a PWA, so a partner without the app can still log a feed
  • Not yet on the App Store: self-serve signup is the launch blocker, not features

Ready to build something like this?

Whether it's a SaaS platform, a custom dashboard, or a brand website - we build bespoke tools that fit your business.