How reminders actually fire

The five steps

1. You save a page and a time. Both are written to storage on your own machine. Nothing is sent anywhere.
2. Latr asks the browser for an alarm at that exact moment. One alarm per reminder, named after it.
3. The browser wakes Latr when the time arrives, even if no Latr window is open — as long as the browser itself is running.
4. You get a notification with the title, and your note if you added one.
5. The exact page reopens in a background tab, at the spot you had scrolled to — you do not have to catch the notification for it to come back.

Restarts, sleep and crashes

Reminders live in storage; the alarm is only a wake-up call. That distinction is what makes the product survivable:

• You restart your computer. Nothing is lost. When Chrome starts, Latr rebuilds every alarm from storage.
• The laptop sleeps. Anything that came due during sleep is delivered on wake, marked late.
• Chrome updates or crashes. The same rebuild happens. This is also why an alarm cannot quietly go missing — every browser start repairs the set.

When a reminder is late

A reminder delivered more than a couple of minutes after its time says so in the notification, and is marked Missed in the popup's Recent activity section. An unexplained notification for something due three hours ago reads as a bug, so Latr explains it.

Delays you asked for are not counted as late. A reminder held by quiet hours, or one you snoozed, arrives when you said it should — so it is recorded as delivered, not missed.

How exact is the timing?

While the browser is open, a reminder arrives within a few seconds of its time. Chrome batches alarms slightly to save battery, so treat it as accurate to the minute rather than the second. For everything a page reminder is for — a ticket drop, a renewal, a reply you owe — that is well inside what matters.