Why your phone's alarm rings on Silent, but a maps notification does not
iOS has three separate volume channels. Which one a sound plays through decides whether it can wake you. Here is how that works, and why it matters at your stop.
Your iPhone has three separate volume levels, not one. The silent switch and Focus only govern the ringer and notification level. Music, video and any audio an app plays while it is running go through the media level, which the silent switch does not touch. That single distinction decides whether a sound can wake you.
The three channels, and which one the silent switch controls
Think of iOS as having three taps rather than one dial.
The ringer and alert level. Calls, texts, notification sounds, and the little chimes apps send when something happens. This is the level the volume buttons change when nothing is playing, and it is the one the silent switch mutes outright. Focus modes filter this level further, by deciding which apps are allowed to interrupt you at all.
The media level. Music, podcasts, video, games, and any audio an app plays deliberately while it is open. This is the level the volume buttons change while something is playing. The silent switch has no effect on it. If you have ever muted your phone and then been startled by a video autoplaying at full volume, you have already met this distinction.
System sounds. Keyboard clicks, the camera shutter in some regions, and a small set of alerts Apple exempts from the switch. The Clock app's alarm lives here, which is why it rings on a phone that is otherwise silent.
Most people carry a phone whose ringer is low or off and whose media volume is wherever they last left it while listening to something. Those two numbers are frequently very far apart.
Why the Clock app can wake you
The Clock alarm is a system alarm. iOS treats it as a special case and deliberately routes it past the silent switch and past Focus, because an operating system that let you accidentally sleep through your own alarm would be a bad operating system. It is not that Clock is louder. It is that Clock is allowed.
For a long time, third-party apps had no way to ask for the same treatment. An app could schedule a notification, and a notification obeys all the rules above.
Why a maps arrival alert cannot
When a navigation app tells you that you are approaching your stop, it is almost always sending a local notification. That means it inherits every restriction of the ringer channel:
- On Silent, it makes no sound.
- Under a Focus mode that does not allow that app, it may not even appear.
- With the phone in a coat pocket and you genuinely asleep, a single short chime at notification volume is not an event your brain is likely to act on.
None of that is a flaw in the app. A notification is designed to be interruptible and polite. It is the correct tool for "your train is in three minutes" and the wrong tool for "wake up".
What an app can actually do about it
There are two honest routes, and Stopzone uses both.
Play real audio while the app is running. An app that is awake for the duration of your trip can configure its audio session for playback and play a tone on the media channel. That channel ignores the silent switch and Focus for exactly the same reason a video does. This is not a loophole or a workaround, it is the documented behaviour of the playback category, and it is why a running app can wake someone a notification cannot.
Schedule a system alarm as a backup. On iOS 26 and later, AlarmKit lets an app schedule a real
system alarm, with the same exemptions the Clock app gets. That covers the case where the app is
not running at all, because you force-quit it or the system reclaimed its memory.
The two are complementary. The first handles the normal case and can escalate, change volume, and speak to you. The second is the floor underneath it.
The claim nobody can make
No app can play louder than your phone's hardware and OS ceiling. Any product that tells you it overrides the maximum volume, or that it is louder than every other alarm in absolute terms, is describing something that cannot be built.
What is true, and worth knowing, is narrower and more useful: because the media channel is separate from the ringer channel, and because most people's media volume is higher than their ringer volume, audio on the media channel is in practice usually louder than a notification sound on the same phone. And it rings on Silent either way.
What to check on your own phone
If you rely on any alarm, three settings decide whether it reaches you:
- Your media volume, not your ringer volume. Play something, turn it up, then stop it. That is the level an in-app alarm will use.
- Attention Aware Features, under Face ID and Attention. When it is on, your phone quietly lowers alert volume when it can see you looking at it. That is helpful all day and unhelpful at the moment you have fallen asleep holding it.
- Whether the app is allowed to keep running. An alarm that depends on an app being awake needs the app left alone in the background, not swiped away.
Where Stopzone fits
Stopzone is a proximity alarm. You pin the stop you are travelling to, it measures the distance
on the device with no network involved, and when you enter the zone you drew it plays a real alarm
on the media channel: a calm voice in your earphones first, then a harsh tone on the speaker if you
do not respond. On iOS 26 and later it also arms an AlarmKit alarm at the start of the trip, so a
force-quit still ends in a sound.
If you want the shorter version of the comparison, it is on the maps arrival alerts page. If you want to know what the alarm sounds like, the home page plays it.
Stopzone is the alarm this article is about.
Download on theApp Store