This is the question that decides whether an alarm app is worth installing at all, and it is the one most listicles skip. An alarm that a Focus mode can silence is not an alarm. It is a notification with ambitions.
The problem, before iOS 26
For years there was a hard asymmetry on iPhone. Apple’s own Clock app could ring through the silent switch, through Do Not Disturb, through any Focus mode, at full volume, with a full-screen interface. Third-party alarm apps could not. They were built on notifications: time-sensitive ones, or critical alerts if the developer had been granted that entitlement, and notifications live under a different set of rules.
The practical consequences were the ones people actually complained about: alarms that a Focus mode suppressed, no Lock Screen takeover, limits on how many alarms could be scheduled, and alarms that could fail to fire after a restart or an app update. Every developer in the category had workarounds. None of them were reliable in the way a real alarm needs to be.
What AlarmKit changed
In iOS 26, Apple introduced AlarmKit, a framework that gives third-party apps access to the same alarm behaviour the Clock app has. Apps using it can schedule alerts that fire even when Silent mode or a Focus is on, present full-screen stop and snooze interfaces, and appear on the Lock Screen, in the Dynamic Island and on Apple Watch.
There is a permission attached, as there should be. The first time an app schedules an alarm, iOS asks you to allow it, and you can revoke that permission later in Settings. That prompt is a good sign, not a nuisance. It is what a real system alarm looks like.
If a third-party alarm never asked your permission to schedule alarms, it is probably not using the system alarm path.
How to tell whether an app really rings on silent
The App Store listing usually will not tell you outright. Here is what does:
- Check the minimum iOS version. AlarmKit only exists in iOS 26 and later. An app supporting iOS 15, 16 or 17 necessarily has a different, older mechanism for those users. It may well use AlarmKit on iOS 26 as well (many apps do) but the listing rarely says, so do not assume.
- Look for the alarm permission prompt. An app using AlarmKit will ask for permission to schedule alarms the first time you set one.
- Test it, properly. Set an alarm two minutes out. Turn on Silent mode, enable a Focus, lock the phone, put it down and do not touch it. This takes three minutes and settles the question for good.
- Then test it again after a restart. The historical failure mode was alarms not surviving a reboot or an app update. Restart your iPhone, set an alarm, wait.
The apps
| Apple Clock | Mornio | Third-party apps supporting older iOS | |
|---|---|---|---|
| Rings in Silent mode | Yes, always | Yes, system alarm via AlarmKit | On iOS 26, depends on whether the app adopted AlarmKit |
| Rings through a Focus mode | Yes | Yes | Historically the weak point, so test it |
| Works when locked / app closed | Yes | Yes | Test it, including after a restart |
| Asks permission to schedule alarms | N/A, it is the system | Yes | Only if it uses AlarmKit |
| Minimum iOS | Built in | 26.1 | Varies: Alarmy 16.0, Erly 17.6, Nuj 15.0 |
We deliberately do not state whether individual competitors use AlarmKit on iOS 26, because their listings do not say, and we will not guess about another developer’s implementation. Test any alarm app yourself before relying on it.
Apple Clock
The most reliable alarm on your iPhone is the one Apple ships, and it is worth saying plainly. It rings through Silent mode and Focus, survives restarts, and costs nothing. In iOS 26 it also gained a custom snooze duration, anywhere from 1 to 15 minutes per alarm, replacing the fixed nine.
What it does not do is verify anything. There is no mission, so a swipe ends it, and nothing checks on you afterwards. That is the entire reason this category exists.
Mornio
Best for: people who want system-alarm reliability plus a mission and a follow-up check, and who are on iOS 26.1.
Mornio requires iOS 26.1 for one reason: it only ever uses the system alarm path. There is no notification-based fallback, because we did not want to ship a version of Mornio that a Focus mode could silence. That is a deliberate trade. It costs us every user on an older iPhone, and we think it is the right call for an app whose only job is to ring.
On top of that reliability sits the Wake Check (scan a registered QR code or barcode to dismiss), the stay-awake check a few minutes later, and a backup alarm.
Strengths
- System alarm through Silent mode, Focus and a locked screen
- No notification fallback that could be suppressed
- Backup alarm for extra reliability
- Built-in reliability check so you can confirm your setup before a critical morning
Limitations
- iOS 26.1 or later, iPhone only, no fallback for older devices
- Uses the system alarm tone; no custom tones
- Newer app with a smaller review base than the established options
Alarmy and other apps supporting earlier iOS
Alarmy (iOS 16+), Erly (iOS 17.6+) and Nuj (iOS 15+) all reach devices Mornio cannot, and Alarmy in particular has roughly 240,000 US ratings at 4.8 stars, so it is a mature, well-tested app. Because they support iOS versions that predate AlarmKit, they necessarily have another mechanism for those users. Whether they also use AlarmKit on iOS 26 is not stated on their listings, and we are not going to speculate about another team’s implementation.
What we would say to anyone using any alarm app, ours included: run the silent-mode-and-Focus test above before you trust it with something that matters.
Things that will silence any alarm
No app can save you from these, so check them tonight if you have an important morning:
- A dead battery. The single most common cause of a missed alarm. Charge overnight.
- The phone powered off. Apple’s Clock will still ring if the phone is off and has charge in some cases, but do not rely on subtleties, leave it on.
- Volume turned all the way down on some setups, depending on your alarm volume settings.
- Revoked permission. If you denied the alarm permission prompt, an AlarmKit app cannot schedule anything. Check Settings.
- The phone in another room, under a pillow, or in a bag. Obvious, and it still happens.
For a genuinely critical morning (a flight, an exam, an interview) use a second, independent alarm. Not a second alarm in the same app. A different device, or an old-fashioned alarm clock. This is what people whose jobs depend on it actually do.