Back-gesture direction is bound to platform convention
Aliases: edge back · Android back · iOS swipe back
What it is
“Go back” has no universal direction on a touchscreen. iOS long made back an inward slide from the left edge; Android gesture navigation later allowed back from both edges; some launchers or car UIs use up or right. Direction is a platform convention, not a spatial necessity. A cross-platform product that only honors the left edge on Android, or that enables both edges on iOS, fights muscle memory people already trained.
Why it happens
Once back is a gesture it becomes a high-frequency escape; people do not read a label each time, they repeat one entrance arc. The shell trains the convention: every day, out of any app, the arc is reinforced as “that is back.” An app that invents another direction asks people to overwrite system-level memory inside one title. When that fails they swipe the wrong edge or think back is broken. RTL scripts unhook visual “back” from the left edge; the system may mirror the band, and an app that hard-codes left-edge slides into empty space in Arabic UI. Conventions also version: from a virtual back key to full gestures, the same person changed direction in two years. Products follow the system rather than insisting on a “more logical” direction of their own.
Studying it
Cross-device transfer: use only the back gesture on system A for a week, then a homologous app on system B, and code the edge and direction of the first back attempt. Independent variables include a visible back arrow and RTL layout. Dependent measures include first-swipe correctness, wrong-edge counts, and time until people switch to a button. Do not declare “left-swipe is more natural” from a single-platform lab.
Where it stops holding
Fullscreen games and cameras often disable the system back gesture to avoid misfires; the convention is paused and a visible exit is required. When a WebView’s internal history fights system back, the issue becomes stack semantics, not direction choice. Desktop browsers go back with a top-left button and a shortcut; touchscreen direction convention does not move there.
Applying it
- Follow the host system for the back gesture: which edges, which direction, whether both sides are live. Read the system; do not invent a third edge in the app.
- In RTL, use the system’s mirrored band; do not write
leftas physical left. - Find someone who just switched systems, give no hint, and ask them to leave a detail page. Watch which edge the first swipe lands on. If you made the unmatched side the only back, transfer will fail.