iOS alarm limitations, honestly explained

Most alarm apps bury this in a support FAQ. We think it belongs on the blog, in plain language: on iOS, no third-party app can do everything the built-in Clock app does. Here's exactly what that means for RiseProof on iPhone.

What Apple reserves for itself

The built-in Clock app uses private alarm infrastructure: it can fire a true alarm that rings at full volume regardless of ringer switch position, Focus modes, or whether the app is running. Third-party apps get local notifications instead, and notifications come with hard constraints:

• A notification sound plays for at most about 30 seconds, at the ringer volume — an app cannot override the ringer or force volume up.
• An app can schedule at most 64 pending local notifications; iOS silently discards the rest.
• If the user force-quits the app, or silences notifications via Focus, delivery is degraded or gone.

How RiseProof works within the rules

To turn 30-second notifications into a persistent alarm, RiseProof schedules a chain of back-to-back notifications for each alarm — that's the standard technique every serious iOS alarm app uses, and the 64-slot budget is why we're careful about how many alarms and how much chain depth you can stack. Critical Alerts (an Apple entitlement that lets sound through Focus and the mute switch) help where granted, and we request the permissions that make the chain robust.

But the genuinely reliable configuration on iOS is simpler and less glamorous: keep RiseProof open (or foregrounded) overnight, with the phone charging. A foreground app can play continuous audio on ring, run the full-screen mission UI, ramp volume within what the system allows, and never worry about the notification budget. That's why RiseProof's iOS setup guide says, in actual sentences, "for the mornings that matter, leave the app open." We'd rather give you one slightly inconvenient instruction than a false promise.

What we won't pretend

Some apps imply their iOS alarms are unstoppable and unmissable. On this platform, that's not a thing any third party can honestly promise: force-quit kills any app's alarm, the 64-notification limit is real, and ringer-volume coupling is Apple's rule, not ours. If Apple ever opens a real alarm API (the AlarmKit-style capabilities appearing in recent iOS versions are a promising direction), RiseProof will adopt it immediately.

Android, for contrast

On Android, RiseProof schedules through setAlarmClock() — a first-class system primitive that survives Doze and reboots and can force the alarm stream to full volume. The full technical story is in How Android alarms actually work. Same app, same missions, same one-time $19.99 — but we'll always tell you which platform is doing the heavy lifting natively.