Why sleep apps go quiet before two months
2026-08-23
Napper is used for close to half the newborns in Norway. It tracks sleep from birth — and it withholds its schedule until around two months. Most of its competitors do the same thing, at roughly the same line.
When an entire industry independently converges on the same silence, that is not caution. That is a wall everyone hit. I went looking for it, because whatever stopped them was going to stop me too.
It turned out to be four walls stacked on top of each other.
There is nothing for a schedule to anchor to
A schedule is clock-anchored structure, and before roughly 6–12 weeks there is no clock. There is no diurnal melatonin rhythm in the first week of life; a rhythm first becomes observable around 9–12 weeks and only steadies at 13–15 (Kennaway 1992/1996; Wulff). The 24-hour rest-activity pattern emerges around the sixth week and is "very definite" only after the twelfth (Parmelee 1961). Even sleep pressure itself — the homeostat that every wake-window rule on the internet quietly assumes — emerges during the second month.
A newborn runs on cycles of roughly an hour, driven by feeds, scattered around the clock. In Mindell's dataset of 156,989 logged sessions, the first three months show sleep bouts under 3.5 hours distributed across the entire 24 hours. There is no day and no night in there to schedule against.
There is nothing stable to learn
Every prediction method needs repeating structure to find. A newborn supplies none. Nap counts flicker between four and seven with no stable positions, which means "the third nap" is not yet a category you can condition on — it is not a thing.
My own data says the same. Month-one wake windows spread ±30 minutes around their median, and the worst era my model has, by a wide margin, is 0–4 months. Any app promising calibration from "3–7 days of logs" is chasing a target that moves faster than its own window converges.
The product mechanics collapse
Newborn wake windows run 35–60 minutes. The core promise of a schedule app is plan your day, get a 30-minute heads-up. There is no lead time to give when the whole window is 35 minutes long. The feature doesn't degrade at this age. It has nowhere to stand.
And then plain prudence
Under about eight weeks, sleep is subordinate to feeding: on-demand feeds, weight checks, normal day-night confusion, and roughly one colicky baby in five whose drowsy cues are effectively invisible. A schedule in that window would nudge a parent to stretch wake times or push a feed to hit a predicted slot — exactly the wrong instinct to install in someone with a three-week-old.
The commercial logic runs the same way. Predictions shown while error is ±45–60 minutes would burn trust at the precise moment a desperate parent is deciding whether this app is magic or noise. The two-month line is not where the algorithms start working. It is where they stop being embarrassing.
Where I part ways with them
All four walls are real, and I hit every one. Here is my disagreement: everyone stops at the wall and then says nothing about it.
Silence is not neutral. A parent opens a sleep app at three weeks, finds a tracker and no guidance, and fills the gap themselves — and what people fill that gap with, at 3 a.m., is my baby isn't doing the thing the app is waiting for. The app knows the answer. The answer is comforting. It just doesn't say it.
So NaniNani says the quiet part out loud. Under two months it proposes no adjustments to anything — there is no clock to steer by — and it tells you why, in those words: a 24-hour rhythm isn't late, it hasn't switched on yet. Between roughly two and four months, while the clock is coming online, it leans on sleep pressure and stays deliberately loose about clock times.
Scattered days in the first months are biology doing precisely what it is supposed to do. An app that implies otherwise is manufacturing guilt out of normal development — and an app that merely stays quiet is letting the parent manufacture it alone.