Appointment Reminders on Android: Exact Alarms, Inexact Ones and Server Push
Short answer: For an appointment reminder, you almost never need an exact alarm on the phone. A reminder that fires within a few minutes of the target is fine for a haircut or a dental check-up, and the most dependable way to send it is from your server through Firebase Cloud Messaging, not from a timer inside the app. Exact alarms are meant for alarm-clock and calendar-style apps, they need a special permission, and recent Android versions restrict them. Choose the weakest tool that meets the real need.
Three ways to deliver a reminder
| Method | Timing | Needs special permission | Works if the app was closed | Best for |
|---|---|---|---|---|
| Server push (FCM) | Usually within seconds of sending | Notification permission on newer Android | Yes, when the phone is online | Most appointment and booking reminders |
| Scheduled work on the device (WorkManager) | Approximate, the system may delay it | No | Yes | Reminders that must exist offline, with a tolerance of several minutes |
| Exact alarm | Precise to the moment | Yes, on current Android versions | Yes | Alarm clocks, calendar events with a hard start |
The temptation is to think "reminder at 09:00 means exact alarm at 09:00". In practice, people do not mind a 9:03 message, and the cost of an exact alarm is complexity, battery use and a risk of store policy trouble.
Why exact alarms became awkward
Android has become stricter about apps waking the phone at precise moments, because many apps abused it. In general terms, Android 12 introduced a special permission for exact alarms, and later versions made it harder: on newer releases, an app targeting a recent Android version may have that permission off by default, and the person has to grant it in settings. A separate permission exists for apps whose core purpose is an alarm clock or calendar, and Google Play restricts who may declare it.
Because this changes between releases, do not rely on memory. As of November 2026, read the current Android developer page on alarms and the Play policy before you commit, and tell your developer to target the latest recommended API level.
For a small business app, the practical consequence is simple: unless your app genuinely is a clock or calendar, plan your reminders so they do not depend on an exact alarm.
Numbered steps to a reliable reminder system
- Decide how late is too late. Write it down per reminder type. "Appointment tomorrow" can be 15 minutes off. "Your driver is outside" cannot.
- Schedule on the server. Your system already knows the booking time. Let it send a push message at the right moment instead of asking each phone to remember.
- Include the details in the message. Date, time and place should appear in the notification itself, so it is useful even if the app cannot open.
- Add a device-side backup. Where a booking exists offline, schedule a local reminder with WorkManager when the booking is saved. If the push arrives too, make the two use the same notification ID so the person sees one, not two.
- Handle the permission. On recent Android versions, the app must ask before it can show notifications. Use a sensible moment, such as right after the first booking.
- Respect battery settings. Some manufacturers aggressively stop background apps. Push messages sent with high priority are more likely to get through. Do not build around workarounds that tell people to disable battery optimisation unless there is no alternative.
- Cancel and reschedule correctly. When a booking changes, the old reminder must disappear. This is where many apps fail: the customer moves their appointment, and still receives the old reminder.
- Test with real devices from more than one manufacturer.
When an exact alarm is justified
Be honest about whether your case qualifies. Examples that may:
- A medication reminder app where a missed minute matters
- A fitness class timer that must ring at the start of a session
- A calendar-style app where events have hard start times
If you are in this category, your developer needs to handle the permission flow: check whether the app can schedule exact alarms, send the person to the right settings page if not, and provide a fallback to inexact timing when they decline. For Google Play, they also need to review the policy on exact alarm permissions and the declaration in Play Console.
Illustrative example: a fictional physio clinic app sends "Your appointment is tomorrow at 14:30, Room 2" from the server at 17:00 the evening before, plus a second message two hours ahead. Both are push messages. No exact alarm is needed, and nothing depends on the app having been opened that day.
Symptoms and what they usually mean
- Reminders arrive in a clump after the phone wakes. Doze mode delayed inexact work. Move delivery to server push.
- No reminder at all on one brand of phone. Aggressive battery management. Check high-priority push and test that device.
- Duplicate reminders. Local and push notifications both fire without a shared ID.
- Reminders for cancelled bookings. The cancellation did not cancel the scheduled work or the server job.
- Silent failure after an update. The notification channel was changed or the permission was reset. Test upgrades, not just fresh installs.
What to put in your brief
- [ ] Maximum acceptable delay for each reminder type
- [ ] Server-sent push as the primary route
- [ ] Optional local backup, with matching notification IDs
- [ ] Notification permission request timing
- [ ] Behaviour on booking change and cancellation
- [ ] A test list of at least three phone brands and two Android versions
- [ ] A written statement of whether exact alarms are used, and why
FAQ
Does a reminder need the app to be open?
No. Push messages and scheduled work both run when the app is closed, within the limits Android sets.
Can we send reminders by text message instead?
Yes, and it avoids the whole permission question, but it costs per message and does not suit every audience. Many businesses use text as a fallback.
Will iPhone behave the same way?
Not exactly. iOS has its own scheduling and permission model, so brief it separately.
Why did reminders stop after we targeted a newer Android version?
Newer target levels apply stricter rules. Your developer should check what changed for alarms and notifications in the release notes for that level.
If late reminders are costing you appointments, tell us how your bookings work and we will choose the right delivery route with you.