Priority rules move with OS versions and can break old apps
Aliases: gesture regression · new system gesture · version clash
What it is
Edge-to-edge chrome, a home indicator, left-edge back, Control Center from the upper right—each arrived in some OS version. Older apps had laid drawers, canvases, and pagers against the priority table of their day. The new system inserts a gesture in front of the app, and an edge that used to work goes dead. That is not a skipped regression test; it is the platform rewriting the priority table.
Why it happens
The system gesture set evolves. New hotspots occupy pixels that used to be “nobody’s” (the home indicator band, curved side walls, the ears of a notch). If an app parked a critical gesture in a region later levied, events are stolen before the app after an OS upgrade. Exemption APIs may also be renamed or tightened. Users see “after the system update this app will not swipe”; blame looks like the app’s, the cause is a platform insert.
Studying it
On adjacent major versions, run the same app binary through an edge matrix: left/right/top/bottom, one finger and several. Record ownership changes. Keep “binary unchanged” as the control. The measure is how many new system-gesture cells invade. Do not test only the current build on the newest OS—that hides the historical break.
Where it stops holding
Apps that adopt new APIs and pull drawers inside the safe area can patch the break. Web apps also eat the browser’s own versioned gestures (swipe-back). Custom ROMs and tablet desktop modes add another layer. Version shift explains interruption along a timeline, not why the system classifies first inside one version.
Applying it
- Tabulate system gestures per target OS version, and run the edge matrix on both the oldest and newest supported builds before release.
- Do not let a critical action live only on an edge the next OS might levy; keep a visible button.
- After a major OS upgrade, hit the edges with an unmodified old binary, hunting cells that used to work and are now eaten.
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.4 Ties should keep the user’s way out
- Adjacent: C3.13 Edge swipe gestures · C3.12 Three- and four-finger system gestures
- Search:
OS version·gesture regression·safe area