If you have used alarm apps on iPhone, you have read instructions like these:
- "Keep the app open in the background."
- "Disable Low Power Mode before bed."
- "Set your ringtone volume to maximum."
- "Add us to Emergency Bypass in your contacts."
- "Do not force-quit the app."
None of those are things a real alarm should need. They exist because, for most of the iPhone's life, third-party apps could not schedule a real alarm — and every one of those instructions is a patch over that hole.
What an app could actually do
An iOS app that is not running does not get to execute code at an arbitrary future moment. That is a deliberate and largely good design decision: it is why iPhones have battery life and why a badly written app cannot wake your phone up at 3am.
What an app could do was ask the system to deliver a local notification at a given time. The system stores it, the app does not need to be running, and at the appointed moment a banner appears with a sound.
That sounds close enough to an alarm. It is not, for three reasons.
The sound is short. A notification sound is a chime, capped at a few seconds. An alarm's defining property — it keeps going until you deal with it — is not available. Apps worked around this by scheduling many notifications in a row, seconds apart, which produces a stutter of chimes rather than a continuous alarm and burns through the per-app notification limit.
The silent switch applies. Notification sounds are exactly what the ring/silent switch is for. The person setting a morning alarm is very often the same person whose phone is on silent, so this failure landed on precisely the wrong users.
Focus applies. Sleep Focus exists to suppress notifications overnight. An alarm built on notifications is, from the system's point of view, indistinguishable from the thing Sleep Focus was invented to silence.
The workarounds, and what each was really doing
"Keep the app open." If the app is in the foreground, it can play audio itself for as long as it likes, bypassing the notification-sound limit. This works and costs you a phone that cannot be used for anything else overnight, plus battery.
Silent background audio. Some apps played an inaudible track continuously so iOS would keep them alive in the background, then played the alarm through that same audio session. Clever, fragile, hard on the battery, and liable to be reclaimed by the system under memory pressure — which is precisely the "it worked for three months and then failed once" pattern people report.
"Disable Low Power Mode." Low Power Mode makes iOS more aggressive about suspending background activity. Any app relying on staying alive overnight is more likely to be killed. A real alarm does not care about Low Power Mode at all.
"Add us to Emergency Bypass." Emergency Bypass is a contacts feature that lets a specific person's calls through Do Not Disturb. Apps that rang you via a VoIP call used this to get around Focus. It works, and it requires you to manually configure a contact entry for an app, which is not a thing a normal product should ask.
Twenty chained notifications. Get a longer noise by scheduling many short ones. Still silenced by the switch, still suppressed by Focus, and it consumes your app's notification budget so a genuine reminder gets dropped.
Why this matters when you are choosing an app
The important question about any iPhone alarm app is not what its screenshots look like. It is what it is built on, because that determines whether it can ring at all when your phone is muted.
A reliable signal: during setup, does it show you a system permission dialog specifically about alarms? On iOS 26 and later, an app using real alarms has to ask, and you will see it. An app that only ever asks for notification permission is using notifications, whatever its marketing says — and it will inherit every limitation above.
The other signal is the support page. If it tells you to keep the app open, disable Low Power Mode, or whitelist a contact, it is telling you what it is built on.
What replaced all of this
iOS 26 shipped AlarmKit, which gives third-party apps the real thing — see what AlarmKit changed in iOS 26. If you want the shorter version of what the silent switch and Focus actually govern, that is here.
Sources
- Apple. AlarmKit — framework documentation. Alarms "break through silent mode", present on the Lock Screen and Dynamic Island, and require
NSAlarmKitUsageDescriptionplus explicit user authorization. - Apple. Scheduling an alarm with AlarmKit —
Alarm,AlarmManager, one-shot and repeating schedules. - Apple. Wake up to the AlarmKit API — WWDC25 session 230.
- Building Fifi's own AlarmKit integration checked part of this directly: it compiles against the iOS 26.2 SDK, and a repeating alarm set through the app has fired on real hardware and stayed armed. Ringing through silent mode is Apple's documented behaviour and has not been independently observed here — firing through Focus has. What is and is not verified says the same thing, and the two pages are meant to agree.