Every nap timer on earth starts counting when you lie down. Your body starts when you fall asleep. That gap — 5 minutes one day, 20 the next — is why the same "25-minute nap" feels great one day and useless the next.
Why fixed timers fail
Same three people, same intended nap. The fixed timer delivers 20, 10, or 0 minutes of sleep depending on luck. Onset-anchored timing delivers 20 minutes to everyone — the wake time flexes instead of the sleep. Lying awake never burns your nap.
Anatomy of a power nap
One tap, one deadline. If you never fall asleep, the app doesn't guess — by 30 minutes of lying awake it tells you, and the deadline alarm still fires. Rested-but-awake ends on time too.
The 30-minute trap
Minutes of actual sleep, not minutes on the clock. Short naps end before deep sleep takes hold; a full cycle rides through deep and comes back up. The zone between is where alarms hurt — Smart Wake's power nap is built to stay out of it.
Cycle naps
Want more than a power nap? Ask for one or two full cycles. The deadline still rules: Smart Wake fits as many complete cycles as your available time allows and aims the wake near a cycle boundary. If two don't fit before your 4pm meeting, you get the best one-cycle nap that does.
Design rule from the evidence: when timing is uncertain, wake early. A controlled trial of an automatic nap alarm showed that waking ~10 minutes late costs the nap's measurable benefit — waking a little early costs almost nothing. Every error in Smart Wake lands on the early side.