Touch and fullscreen system gestures occupy the value of edges
Aliases: edge-gesture conflict · bezel gesture · back gesture
What it is
The desktop dividend of “fling to the top edge and you’re there” is collected first by the system on a fullscreen phone: left edge is Back, bottom edge is Home, top edge is notifications and Control Centre. An app that then parks a carousel, a drawer, or a sidebar toggle on those edges loses the swipe to the system. System-gesture occupation means the edge’s qualification as a cheap target has already been requisitioned on touch; an app cannot spend the edge the way desktop Fitts suggests.
What is taken is not the pixels. It is the gesture meaning of that edge. A button drawn there can still be tapped. A slide along the edge no longer belongs to the app.
Why it happens
Once physical keys disappear, the system still needs a channel for Back, Home and notifications that does not occupy the content area. The edge is the only continuous strip not already filled with content. Platforms therefore write “swipe inward from the edge” as a system gesture, outranking the app. A carousel, a pager or a drawer on the same edge becomes second in line: the system judges first, and if it matches, it eats the touch.
The fight is nastiest in the outer millimetres. A pager flush with the left edge sends a user who wanted the next card back to the previous screen. A tab bar that also opens a sheet from an upward swipe contends with the home indicator for the same arc. An app that “goes immersive” and hides system gestures to win the edge leaves the user with no system way out.
Where it stops holding
Older devices with a physical Home key or an on-screen Back button occupy the edge much less, and a drawer can still sit there. A desktop touchscreen with no system edge gestures can still spend Fitts’s edge. Games and drawing tools can temporarily reclaim the edge in a system-provided immersive mode, but the exit must be built some other way — users must not be locked in a fullscreen they can leave only with an app gesture. A foldable’s cover screen is so narrow that once both long edges are reserved, the remaining swipeable band may be too thin for the app’s own gesture.
Applying it
- Do not make “swipe in from the physical edge” the only navigation. Open sidebars with an explicit button, and start carousels on a band inset from the system gesture.
- Inset the start of app gestures — swipe-up sheets, pull-to-refresh — beyond the home indicator or the status bar; do not begin on the physical edge.
- Fullscreen scenes (playback, reading) need a way out that is not an edge gesture: an on-screen button, or a second tap.
- How to check: on a device with system gestures on, swipe each of the four edges ten times and count how many the system ate and how many the app ate. If the app wins all ten on an edge, check that the user can still leave with the system gesture. If the system wins all ten, the app must not bind critical navigation to that edge.
Related
- Same group: F1.05.1 Edges are unbounded in the direction of motion, so pointing cost is lowest · F1.05.2 Corners are cheapest but hold almost no targets
- Nearby: F1.12 Fixed chrome and safe areas · F2.12 Safe areas and irregular screens
- Search terms:
system-gesture occupation·edge swipe·bezel gesture·back gesture