Work / Charades / Wiki / Surfaces
alerts
Surfacecanonicalverified 2026-10-02
SURFACE.MOBILE.PATTERNS.ALERTSSummary
The two native dialogs the app raises, with the copy it actually ships.
Raw wireframe
- .context/designs/mobile/patterns/alerts.html
Why it is drawn this way
Because they were the only user-visible copy no wireframe held. Both are
Alert.alert calls, so the OS draws them and no screen file had a reason to.
One of them confirms an irreversible delete.
The design check could not see them either. Both calls pass their words
through t("…"), and the check read only string literals, so it reported "0
dialog and toast strings checked" for as long as it existed. It now resolves a
key through src/i18n/en.ts and checks the sentence.
A pattern page, not two screens. A native alert has no route and no layout
of ours to get wrong; what needs reviewing is the wording. Its route is
null because no one screen renders it.
The English strings, exactly. They are the values of
home.alert.noMoviesTitle, home.alert.noMoviesBody, history.clearTitle,
history.clearBody, history.clearCancel and history.clearConfirm. Hindi and
Telugu fall back to these when a key is missing.
"No Movies" has the default single button. The call passes no buttons, so the OS supplies OK.
Related
- home — where "No Movies" is raised, when Play is tapped with no playable pack
- history — where the clear confirmation is raised, from either Clear all
Sources
- src/app/index.tsx
- src/app/history.tsx
- src/i18n/en.ts
Every project of mine is written down like this.
Read the résumé