Migraine apps end where the headache does, and that's the wrong place.

The day the app has nothing to log

It's the morning after. The headache broke sometime in the night, and by every clinical definition the attack is over. But you can't hold a full sentence, the light through the blinds still feels like too much, and your neck is stiff in a way that has nothing to do with how you slept. You open your tracking app out of habit. Yesterday sits there, neatly logged: onset, peak, a triptan at 9 a.m. Today's row is blank. There's nothing to record, because the thing the app measures already ended. So you close it, and the part of the migraine that's about to eat your Tuesday goes undocumented.

The attack-shaped app

Most trackers share a hidden assumption: a migraine is an event with a start and a stop. Call it the attack-shaped app. It's built around the spike, the window when pain arrives, escalates, and resolves, because that window is the easy thing to model. It has an onset you can timestamp, a severity you can slide from one to ten, a medication you can attach, and an end. Every question the app asks assumes the migraine is the pain, and the pain is the migraine. When the pain leaves, the record stops. The catch is that for a large share of people, the migraine isn't finished when the headache is.

Why the after-phase disappeared

This isn't an accident of lazy design. The attack is the unit the whole surrounding system is organized around. Acute medications are dosed to it. Clinical trials measure their endpoints against it: pain freedom at two hours, relief of the most bothersome symptom. Prior-authorization forms count it. When you build a tracker, the attack is what every downstream reader already speaks in, the prescriber, the trial, the insurer. So the app inherits their vocabulary. It logs what a neurologist's intake form logs, and it stops where that form stops. The fatigue, the word-finding trouble, the residual sensitivity to light don't have a billing code, so they don't get a field. The apps weren't built for the person on day two. They were built for the paperwork the attack generates.

The after-phase is the rule, not the exception

Postdrome is not a fringe complaint from a sensitive minority. In an electronic-diary study of migraine patients, Giffin and colleagues found that around 81% of attacks were followed by at least one non-headache symptom in the hours after the pain resolved (Giffin et al., Neurology, 2016). The most common ones weren't exotic: tiredness, trouble concentrating, a stiff neck. In r/migraine and r/VestibularMigraines the same pattern shows up in plain language. People describe a hangover that costs them the day after an attack, and a recurring frustration that the tools they use have nowhere to put it. One of the loudest recurring notes in those communities is some version of the same line: the apps feel like they were made by people who've never had the after-phase themselves.

What day two actually looks like

Picture a Wednesday attack. The triptan works, the pain's gone by evening, and the app closes the book: one migraine, logged. Thursday you're slow, reading the same email three times, canceling the thing you'd promised, snapping at someone and not sure why. Friday, still not right. By the next week you feel human again, and when your neurologist asks how the month went, you say 'a few migraines, not too bad,' because the app told you it was a few discrete days. What the record can't show is that a single Wednesday attack actually took three days out of your life. Multiply that across a chronic pattern and the data you carry into your appointment quietly understates how much migraine is taking from you.

A single Wednesday attack took three days out of your life. The tracker counted the spike.

Track the arc, not the spike

If the after-phase is where a real share of the disability lives, then a tracker that ends at the headache is quietly miscounting the disease. Change the unit from the attack to the arc and a lot follows. You'd log a continuous timeline instead of a row per headache. You'd capture severity that keeps moving after the pain stops, because postdrome fatigue and brain fog have their own curve. You'd give the day-two symptoms a field, so 'a few migraines' becomes 'nine days affected,' the number that actually argues your case to a doctor or a disability reviewer. And you'd design for someone tracking while they still can't focus, not someone at full capacity tapping through a form.

Building for day two

We built Postdrome around that gap, because the people we care about kept losing the day after and had nowhere to put it. The timeline doesn't close when the headache does. It follows the whole arc, including the residual photophobia, the fog, and the neck stiffness that outlast the pain. Aura Mode exists for the obvious reason that you can't tap through a fiddly form when you can't see straight or hold a thought. Your data stays on your device and exports cleanly, so the record you build is yours to hand to a neurologist. And it's one lifetime price, stated up front, because a condition you live with for years shouldn't bill you monthly to see your own symptoms.

What we're watching

The open question we keep returning to: how much of the postdrome is one thing versus several. Fatigue, cognitive fog, and residual light sensitivity may not share a single mechanism, and they almost certainly don't clear on the same clock. The more people log the full arc, the clearer it gets which after-phase symptoms cluster together and which move on their own. That's exactly the pattern a tracker built for the attack can never surface, because it stopped looking the moment the pain did.