How Android allows loud alarms
Android exposes a dedicated alarm audio stream with a high priority alarm notification channel. Apps with alarm permission can play through that stream on silent, locked, and Do Not Disturb, with user consent on first open. The server monitors your venue over websocket at zero data cost, then sends a free push on trigger. The app receives it even when closed and fires the local alarm with custom tone and volume. That is the same path as the Clock app, which is why it is reliable.
Why iPhone cannot match it yet
Apple gates loud bypass behind the Critical Alerts entitlement, granted case by case with review and strict justification. Standard push on iOS respects silent and Focus modes. Web push on iOS is further limited. That is why Wakever is Android first globally in English, with iPhone as waitlist only until traction and revenue justify the Apple build, review cycle, and call fallback for offline coverage.
Why web push cannot replace native
Browser push has no alarm stream, no full screen intent, and no survival under battery saver. Service workers get suspended. The result is quiet delivery that you see in the morning. Native Android with exact alarm permission plus battery exemption solves exactly that. Full product context is in how alarms sound on silent.
What to do by device
On Android, join the waitlist and select Android plus your exchange. At launch, allow alarms and disable battery limits, then set one venue exact alarm. On iPhone, join the same waitlist and select iPhone. That vote directly controls iOS priority. When iPhone demand passes 30 percent or Android revenue covers Apple costs, the iOS build with call fallback unlocks. Until then, no false promises.