Baby Bloom

Where baby records actually live

Ask new parents how they track their baby's development and the answer is almost always a collage: a few notes in a phone app, a spreadsheet somebody started with good intentions, some photos with dates attached, and a great deal held in memory.

None of it was built for the job. The notes app has no structure, so a milestone and a shopping list sit side by side. The spreadsheet demands a level of diligence that does not survive a bad week. Memory is doing a lot of quiet work, and memory during the first year is not at its best.

The result is not that parents fail to track things — they clearly do. It is that the record is fragmented, so looking back is harder than it should be, and the moments that were not written down in the first ten minutes tend not to get written down at all.

Designing for the state the user is in

Most software is designed for an attentive person at a desk, and most software gets to make that assumption safely. This one does not.

Baby Bloom is opened one-handed, mid-task, frequently in the middle of the night, by someone who has been interrupted and is about to be interrupted again. A session can end at any moment without warning, not because the user lost interest but because they were needed elsewhere.

That reframes the design problem. The question stops being "how do we present all the capability?" and becomes "how little can stand between opening this and having recorded the thing?" Every extra decision, screen or step is not just friction — it is a chance for the session to end before the record exists. A tracker that is slightly harder to use does not get used slightly less; it stops getting used.

So the interface is deliberately quiet. Nothing competes for attention, nothing is gamified, nothing prompts or nudges. Calm reads as a stylistic choice and is really a functional one: clarity, for a tired user, comes from what has been left out.

One home for the history

The other half of the problem is not capture but retrieval. Records scattered across three apps are effectively unsearchable — the information exists, but nobody is going to reassemble it a year later.

Milestones, growth and routines living in one purpose-built place means the history is somewhere it can actually be looked back on. That is the real return on the discipline of logging: not the entry itself, but being able to see the shape of a year afterwards.

Building it for the web serves the same end. There is no install step and no device that holds the only copy — sign in from whatever is nearest, which given the circumstances is not always the same phone.

Where it landed

A dedicated tracking portal built with Vue, Nuxt and PostgreSQL, with milestones, growth and routines in one calm, purpose-built place. The engineering here is unremarkable by design. The work that mattered was restraint: deciding what not to put on the screen so the app stays usable by someone with one hand free and very little attention to spare.