Edge-to-edge screens widened the system-owned band
Aliases: gesture navigation · home indicator · system occupancy band · full-screen bezel
What it is
After the physical Home key and side bezels went away, content painted to the glass edge—but the system still needed Leave, Back, and Control Center. Those entries moved from keys and frames outside the pixels into strips inside them. The system-owned band thickened. The home indicator along the bottom, the back strips at the sides, the pull-down at the top are products of that form-factor shift, sharing glass with content. Apps used to assume the whole rectangle; after edge-to-edge, the rectangle is shared at the rim. This entry is only about occupancy thickening with form. It is not about who wins arbitration, and not about how one edge band clips the head of an app gesture.
Why it happens
A hardware key is a dedicated target that spends no content pixels. A bezel is empty space that can be a start feature without drawing UI. Edge-to-edge took both away. To keep the same system abilities, new hit bands had to be drawn inside the content rectangle. The bottom changed from “height of a key” into a full-width gesture strip; the sides changed from “frame” into swipe-in back bands; a notch or island occupies display and gesture at once. If an app still parks a virtual stick, a tab bar, or a drawer handle on the outer rim using the old body, it overlaps the new occupancy—not because the app forgot how to gesture, but because exclusively owned pixels shrank by a ring. That ring thickened across generations: from button navigation to full gesture navigation, failures cluster on old layouts, especially sustained touches in the bottom corners.
Studying it
Compare forms: the same app, the same tasks, on a button-navigation body and a gesture-navigation body; code operations eaten by the occupied band. Use consecutive-generation hardware, not only a simulator’s safe-area numbers.
Independent variables: navigation mode (buttons / gestures), millimetre width of bottom and side bands, whether controls sit on the rim. Dependent variables: accidental Home or Back, failure rate of rim-hugging controls, whether people switch hands or change grip.
Turning system gestures off on an edge-to-edge phone recovers the old occupancy and does not represent the device people bought. “Content is drawn to the edge” is not “occupancy did not change”—drawing to the edge is background pixels, not hit ownership. Hold app version fixed in a generation comparison or layout change confounds form change.
Where it stops holding
Rugged and some slab phones that kept a chin or a hardware key did not thicken occupancy; old rim layouts still hold. Tablets are wider, so a bottom gesture strip is a smaller share of width and side Back behaves differently. Desktop never had this shift. A foldable cover display is extremely narrow, so the band can be a larger share than on a large slab; do not substitute the inner screen’s edge-to-edge result.
Applying it
- Pull sustained-hold controls (sticks, record, drawer handles) in from the bottom corners and the outer side rims; do not reuse coordinates from bodies that had a hardware key.
- Re-walk old rim interactions on a gesture-navigation phone; a regression pass on button navigation is not enough.
- Backgrounds may paint to the edge; tappable targets and continuous-gesture hit regions inset by the occupied band. Those are not the same decision.
- Verify by installing one build on a button-navigation phone and a gesture-navigation phone and completing tasks that depend on sustained rim touches. Counts that become “went Home” or “triggered Back” only on the edge-to-edge body are conflicts added by thicker occupancy, not a miswritten app gesture.