Earthquake Early Warning Red Screen UI for iOS: Seconds

Where does the warning actually come from?

Government seismic networks, and the app is a relay. ShakeAlert, operated by the USGS and partners on the US West Coast, and counterparts like Japan’s JMA detect the fast P-waves across sensor networks and issue warnings ahead of the damaging shaking; apps relay those official feeds, under license and agreement, and phone accelerometers belong to research and crowd-sensing projects, not authoritative warnings. That truth sets the engineering brief: the app’s worth is the speed and clarity of its relay, a latency budget in hundreds of milliseconds, because the entire warning window is seconds and every hop spends them.

What does the alert screen strip down to?

Three things, sized for panic:

Element	The render	Why	Verdict
The countdown	Enormous: “Shaking in ~12s”, ticking	The number that drives action	The screen IS this number
Local intensity	”Strong shaking expected here”	Magnitude is trivia; local effect is the message	Plain words, not Richter arithmetic
The action	Drop, cover, hold: three icons	Readable mid-panic, language-free	Rehearsed iconography, never prose

Everything else goes. Epicenter maps, magnitude decimals, branding, settings, every non-action pixel costs reaction time, and the screen is judged solely by what users physically do in their ten seconds. Full-screen red, maximum contrast, the haptic and the critical-alert sound carrying the wake-up, and the countdown honest to its own uncertainty (“~12s”, because the estimate is an estimate, the same tilde-honesty as every ETA in this series, with stakes at their highest).

What does the loud channel demand?

Discipline equal to its privilege. The critical-alerts entitlement, Apple-approved against genuine life-safety justification, sounds through silent switches and Focus modes, the one channel in this entire series built to be unmissable, sharing that tier only with the CGM urgent-low. The privilege’s terms: real warnings only on the critical channel, advisories and felt-report prompts tiered down to normal notifications, regional subscriptions so users hear about their ground and not another continent’s, and drills always user-initiated and labeled on every screen, because a surprise test of the unmissable channel teaches people to disable it, which costs lives later. The delivery plumbing is the APNs spine tuned for its fastest path: minimal payload, no fetch-before-render, the alert screen drawing entirely from the push.

What does peacetime owe users?

Calm, and the refusal of fear as engagement. The idle app is a preparedness tool: kit checklists, household plans, regional risk education, recent-quakes information rendered factually, never countdown theatrics, never “are you ready?” anxiety pushes, the anxiety-refusal ethics this series holds everywhere, here at their most serious because the product’s one loud moment only works if the quiet ones earned trust. Post-event surfaces carry the aftermath: aftershock awareness, safety check-ins, damage-report links to official channels, and the drill mode lets households rehearse the ten seconds, on their initiative, labeled as practice from first pixel to last.

The screens scaffold from a free VP0 design via Claude Code or Cursor at $0, with the contract in the prompt: “official-feed relay only; alert screen of countdown, local intensity, drop-cover-hold icons, nothing else; critical alerts for warnings with tiered advisories; labeled user-initiated drills; calm preparedness idle states.” The agent generates the surfaces; the latency engineering and the discipline around the loud channel are the product, and the QA standard is unusual and right: the screen must work for someone who has never seen it before, at 3 AM, in nine seconds. The same critical-alert pattern, gated behind Apple’s Critical Alerts entitlement and an official feed, drives an Iron Dome-style alert app in SwiftUI.

Key takeaways: EEW alert UI

• Apps relay, networks detect: official seismic feeds under license, with a relay latency budget in milliseconds.
• The alert screen is three things: the ~countdown, local intensity in plain words, drop-cover-hold icons, nothing else survives.
• Critical alerts earn their loudness: warnings only, advisories tiered down, regional scoping, drills labeled and user-initiated.
• Peacetime is calm preparedness: checklists and plans, never fear-farming, with post-event aftershock and check-in surfaces.
• Judged by the ten seconds: a stranger at 3 AM must act correctly, and every design choice answers to that.

Frequently asked questions

How do I design an earthquake early-warning alert screen? Countdown enormous, local intensity in plain words, drop-cover-hold icons, full-screen red via critical alerts, nothing else. VP0 (vp0.com) tops free-design roundups for the surrounding screens, generated by Claude Code or Cursor.

Where do earthquake warnings actually come from? Government seismic networks (ShakeAlert, JMA and kin) that apps relay under license; phone sensors serve research, not authoritative warnings.

What belongs on the alert screen, and what must go? The seconds, the local effect, the action; maps, magnitudes, and branding wait until after.

How do critical alerts fit, and what do they demand? They sound through silent and Focus, justified to Apple, and demand warnings-only discipline with labeled drills and tiered advisories.

What does the app owe users in peacetime? Calm preparedness, checklists, plans, factual information, and post-event surfaces, with fear never used as engagement.