Critical Alerts vs AlarmKit Alarms on iOS Explained

What's the difference between critical alerts and AlarmKit alarms?

Critical alerts are a notification type gated behind an Apple-approved entitlement that only health, safety, and security apps can request. AlarmKit alarms are a newer, open framework any app can use to schedule real alarms, no special approval required.

Both mechanisms share one trait: they ring through Silent mode, Do Not Disturb, and Focus. Past that, they're built for different jobs. Notifications scheduled with UserNotifications stay quiet in silent mode or during a Focus unless the app holds the rarely granted Critical Alerts entitlement, while AlarmKit alerts cut through silent mode and focus with a permanent banner and sound. Apple itself is explicit that the new framework doesn't replace the old one — Apple's WWDC25 session notes AlarmKit alarms "are not a replacement for other prominent notifications, like critical alerts or time-sensitive notifications."

If you've landed here after searching what AlarmKit actually is, this is the companion question: why does one mechanism need Apple's sign-off and the other doesn't.

How do you get the critical alert entitlement?

You apply directly to Apple, describe a specific life-safety, health, or security scenario, and wait for manual review — there's no self-service toggle. Developers must apply for a special entitlement from Apple to use Critical Alerts, and the application process involves demonstrating a legitimate need and adhering to strict guidelines.

Apple's own developer forums back this up with blunt language. One Apple staff response to a demo-app request put it plainly: the entitlement won't be granted purely for demo purposes, because the audience for it is significantly restricted given how disruptive critical alerts are. Real developers report review taking "typically over days to a few weeks, and it is common to be asked to resubmit with a clearer case." Apple's guidance narrows eligible categories to roughly four buckets:

These are apps monitoring medical conditions or dispensing medication reminders, apps detecting emergencies like fire or break-ins, home security and fraud detection apps, and government-issued disaster alerts. A calendar or productivity app almost never clears that bar, which is exactly why AlarmKit matters — it gives everyday apps a legitimate way to ring through Silent mode without pretending to be a safety product.

Why did Apple build AlarmKit if critical alerts already bypass Silent mode?

Because critical alerts were never meant for cooking timers, workout intervals, or wake-up calls, and Apple needed a way to let ordinary apps schedule real alarms without opening up the abuse risk critical alerts were designed to prevent. AlarmKit fills that gap by giving any app the same underlying alarm permissions as the built-in Clock app.

AlarmKit, introduced at WWDC 2025 and shipped in iOS 26 in late 2025, gives third-party developers the same alarm permissions as the Clock app: full-screen alerts, sound through Silent and Focus, Lock Screen UI, and Dynamic Island integration. No entitlement request, no waiting on Apple review — just a runtime authorization prompt the user approves once, similar to how notification permissions work.

Adoption so far tracks exactly the use cases Apple called out on stage. Apple specifically called out recipe and cooking apps embedding countdown timers that fire as real alarms instead of notifications you might miss, and several major recipe apps have shipped or announced AlarmKit integration. Interval and workout apps followed for the same reason: HIIT apps have switched timer rounds to AlarmKit so the round-end alarm fires reliably through Workout Focus. Notably, major task managers like Things, Todoist, TickTick, and Microsoft To Do were still using Time Sensitive notifications, not alarms, as of early 2026 — a sign that adoption outside timers and wake-ups is still catching up. For more on where this fits against Focus rules generally, see whether Focus blocks calendar alerts.

How do critical alerts and AlarmKit compare side by side?

The two mechanisms differ on approval process, intended use, and how deeply they integrate with system UI. The table below lines up the practical differences a developer or a curious user would actually care about.

For calendar apps specifically, this distinction explains why an app like Pealo relies on AlarmKit rather than critical alerts — a meeting reminder isn't a medical emergency, but it still deserves to ring through Silent mode reliably.

What does this mean if you're just trying to not miss meetings?

It means the app category that used to have no good options now does. Before AlarmKit shipped in iOS 26, a calendar app had no legitimate path to bypass Silent mode — critical alerts were off-limits since a missed meeting isn't a safety emergency, leaving apps stuck with regular notifications that go dark the moment Focus or Silent mode is on.

That's the exact failure mode covered in notification blindness and missed meetings and in why calendar reminders don't wake you up. AlarmKit closes that gap without requiring a health-and-safety pretext. If you're comparing calendar alarm tools that have actually adopted the framework, the calendar alarm apps compared for 2026 roundup breaks down which ones ring through Silent mode today versus which still rely on regular push notifications.