Why gestures
With full-screen phones, iOS and Android replaced hardware buttons with system gestures such as swiping up for home and edge-swiping for back. Gestures save space and become fast once learned. Bragdon et al. (2011) found edge-based gestures were less disrupted than small buttons when users walked or did not look. Gestures starting within the thumb zone suit one-handed use.
The trap of invisible commands
Norman and Nielsen (2010) argued gestures are invisible, hard to discover and inconsistent across apps; in Norman's (2013) terms they lack signifiers. Wobbrock et al. (2009) proposed eliciting gestures from users and choosing high-agreement ones, which were easier to learn. Horizontal app swipes can also clash with the system's edge-back gesture.
Using gestures well
Never make gestures the only path: offer a visible button or menu too, and hint with subtle animation or grab handles. WCAG 2.2 criterion 2.5.1 requires single-pointer alternatives to multipoint or path-based gestures, a web accessibility basic that helps everyone. Back primary movement with visible structures such as bottom navigation.
FAQ
- Can a feature be gesture-only?
- Not recommended; discoverability is low and accessibility rules require a single-pointer alternative.
- What if an app swipe clashes with system back?
- Keep horizontal swipe areas away from screen edges or use the platform's gesture-exclusion settings.
Sources reviewed: 2026-10-27
References
- Wobbrock, J. O., Morris, M. R., & Wilson, A. D. (2009). User-defined gestures for surface computing. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 1083–1092). ACM. Elicits gestures from users and measures agreement, guiding natural gesture choice.
- Bragdon, A., Nelson, E., Li, Y., & Hinckley, K. (2011). Experimental analysis of touch-screen gesture designs in mobile environments. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 403–412). ACM. Compares gestures and soft buttons while walking or not looking.
- Norman, D. A., & Nielsen, J. (2010). Gestural interfaces: A step backward in usability. Interactions, 17(5), 46–49. A critique of gestures' poor visibility and consistency.
- Norman, D. A. (2013). The design of everyday things (Revised and expanded ed.). Basic Books. The classic on affordances and signifiers, useful for hinting gestures.
- Bergstrom-Lehtovirta, J., & Oulasvirta, A. (2014). Modeling the functional area of the thumb on mobile touchscreen surfaces. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 1991–2000). ACM. Thumb-reach model useful for placing edge-swipe start zones.
- Google. (n.d.). Gestures. Material Design 3. Official Android definitions of tap, swipe and drag gestures.
- World Wide Web Consortium. (2023). Understanding Success Criterion 2.5.1: Pointer gestures. In Understanding WCAG 2.2. Requires single-pointer alternatives to path-based and multi-finger gestures.