System-level multi-finger gestures take priority over app gestures

What it is

Three- and four-finger swipes, pinches, and taps belong first to the system shell on current platforms: app switching, home, multitasking, sometimes global undo. If an app is also listening on the same contact, arbitration gives the system the win. An app cannot assume it will fully consume a three-finger swipe.

Why it happens

The system recognizer lives in the window server or gesture-navigation layer and sees contacts before the app’s touch callbacks. Once finger count hits a reserved value and a direction or pinch pattern matches, the system captures the pointer; the app gets a cancel, or never sees later moves. The point is that people can escape any app—including fullscreen, frozen, or back-button-less ones. Priority is an escape hatch, not spite. If the app already started its own animation on three-finger down, a system steal leaves that animation half-finished—the visible cost of priority.

Studying it

Register a three-finger swipe inside a fullscreen app and pit it against the system “switch app.” Log who captures first, whether the app got cancel, and which screen the user landed on. Independent variables include the system-gesture toggle, fullscreen versus a normal window, and different reserved sets on tablet versus phone. Turning system gestures off is the control that shows whether the app recognizer works at all. Field traces full of “I was halfway through a stroke and jumped apps” are priority firing when people did not expect it.

Where it stops holding

On a desktop trackpad, three fingers may have been remapped by the user to “move window” rather than switch apps; the reserved set is not a constant. Android skins each own three-finger screenshot and four-finger split; one vendor’s table is not the world. If a stylus does not count toward finger count, two fingers plus a pen may look like two. When accessibility occupies three-finger tap, priority moves to the assistive service and the app is even hungrier.

Applying it

• Do not put a core action on a three- or four-finger swipe; assume those contacts can be taken at any time.
• On touch cancel, tear down the in-app gesture cleanly; do not leave a half selection or a stuck tool.
• Under the target OS’s default gesture navigation, three-finger swipe across your fullscreen canvas. Landing in multitasking rather than your command is expected priority. Then, with a “disable system gestures” developer option, check that only then the app sees a full trace.

Related

• Same group: C3.12.2 Apps should not occupy system-reserved multi-finger gestures · C3.12.3 System gestures truncate same-shape gestures inside the app
• Adjacent: C3.11 Two-finger and multi-finger taps · C3.31 System versus app gesture priority
• Search: system gesture · touch cancel · three-finger swipe