Ties should keep the user’s way out
Aliases: exit first · navigation preserved · escape hatch
What it is
When a system gesture and an app gesture fight on the same edge, the default should leave exit, back, and home to the system, and move or demote the app’s drawer, pager, or canvas stroke. Being trapped in an app that guessed the gesture wrong is worse than opening a drawer one extra tap. The default conserves escape, not immersion.
Why it happens
Failed escape costs control: a wrong purchase can be undone; a full-screen player or a wedged WebView that cannot be left cannot. The system puts back and Home in front of the app by that loss ordering. If the app “wins” the clash, it wins local smoothness and loses global control. Visible buttons can patch escape, but under assistive tech, dead touch, or an unresponsive app, only system gestures remain. The default therefore cannot be “whoever’s recognizer succeeds first.”
Studying it
On a contested edge, compare system-first versus app-first. Tasks include “leave this wrong screen” and “open the drawer.” Record time trapped, reaches for a hardware key, and “I thought it froze.” Time trapped is the measure that matters, not drawer-open speed. Include people who do not know the app’s private stroke.
Where it stops holding
Managed kiosks, exam clients, and drive-lock car modes may legally lock exit, but that is a device policy with an admin or parked-car way out. A game may grab an edge during a round; the pause menu must give escape back. Conserving navigation by default does not forbid a short, informed exemption.
Applying it
- On a clash, leave back/Home to the system; open app drawers from a non-system edge or a visible handle.
- Full-screen media gets an obvious close, not only the same upward swipe the system uses.
- Pretend the app is unresponsive: system back or Home should still leave. If not, priority is reversed.
Related
- Same group: C3.31.1 System gestures are decided before the app sees touch events · C3.31.2 Opting out of a system gesture is an explicit declaration users may not know about · C3.31.3 Priority rules move with OS versions and can break old apps
- Adjacent: C3.14 Back gestures · C3.16 Swipe up to close and home
- Search:
escape hatch·system back·navigation priority