Gestures

A food delivery app shipped a neat new feature: swipe an order left in your basket to remove it. Within a week, support tickets piled up. “My pizza disappeared.” “I didn’t remove anything!” People were scrolling the basket with their thumb, the thumb drifted a little sideways, and items vanished. No Undo, no confirmation. Some customers only noticed at the door, when the rider handed over half an order.

Nobody had tested scrolling the basket. The swipe worked perfectly when you swiped. It also “worked” when you didn’t mean to.

Why gestures matter

On a phone there is no mouse and no hover. Everything happens through a few gesturesGestureA touch action such as tap, long press, swipe, pinch or drag.Open in glossary →: tap, hold, swipe, pinch. They feel natural, which is exactly why users notice instantly when one misbehaves, and why bugs here feel like the app is “broken” even when the code technically does what it was told.

Gestures are tricky to test because:

• They are invisible. A button says “Delete”. A swipe-to-delete says nothing until you discover it.
• They compete. The same finger movement could be a scroll, a swipe, a drag or the system’s back gesture. The app has to guess.
• They depend on thresholds: how long is a long press? How far is a swipe? Change a number and the feel changes completely.
• Not everyone can perform them. People using a screen readerScreen readerSoftware that reads the screen aloud for blind and low-vision users, like VoiceOver or TalkBack.Open in glossary →, a switch device or voice control need another way to do the same thing.

The gesture vocabulary

These are the gestures you’ll meet in almost every app, and what they usually mean.

What separates a tap from a swipe

An app doesn’t “see” gestures. It sees a stream of touch points: finger down at (120, 340), moved to (124, 338), lifted after 180 ms. A gesture recognizer turns that stream into a decision using a few thresholds:

Try it: the gesture pad

Play with the pad below and watch how the numbers decide the gesture. Try a slow drag versus a quick flick over the same distance. Hold still until the ring fills. Turn off “Wait for double tap” and double tap: you’ll get a Tap first and then a Double tap, which is exactly how “the like button also opened the post” bugs happen.

Edge swipes belong to the system

Some edges of the screen are reserved. A swipe that starts there is handled by the operating system or by the navigation stack, not by your app’s content.

Things to know:

• iOS back swipe comes from the navigation controller. Apps with custom navigation sometimes break it, so swiping from the left edge does nothing or, worse, leaves the screen half-dismissed.
• Android back is a system gesture from both side edges. It must do the same as the back button: close the drawer, dialog or keyboard first, then go back a screen, and only then leave the app. With predictive back, apps that support it show a preview of where you’ll land (since Android 15; on by default for apps that target Android 16).
• Apps can ask the system to exclude small areas from the back gesture (for example a drawing canvas), but that’s limited and should be rare.
• In full-screen games and video, iOS may need two swipes from the edge (the first one just shows the indicator), so the game doesn’t get interrupted.

When gestures collide

The most interesting gesture bugs come from conflicts: two things want the same finger movement. Good apps decide early, usually within the first few pixels, which direction the finger is going and then lock to one gesture.

Discoverability: hidden gestures need a visible way

A gesture is a shortcut, never the only path. Users can’t see swipe actions or long-press menus, so many will never find them. Apple’s and Google’s guidelines both say the same thing: provide a visible control for important actions.

Destructive gestures deserve extra care: a higher threshold (a full swipe or a swipe plus tap on the revealed button), a clear color and icon while swiping, and an Undo afterwards.

Accessibility: every gesture needs an alternative

Lots of people can’t do a precise swipe, pinch or long press: people with tremors or limited dexterity, people using a stylus or a head pointer, and people who can’t see the screen. When VoiceOver (iOS) or TalkBack (Android) is on, gestures change meaning completely: a single tap only selects an item, a double tap activates it, and swiping left or right moves between elements. Your app’s custom swipe never reaches the app.

So for every gesture, check that there’s another way:

• Screen readers. Custom swipe actions should be exposed as accessibility actions: VoiceOver reads “Actions available” and the user swipes up or down to pick “Delete”. TalkBack lists them in its Actions menu. Standard iOS list swipe actions get this for free; custom-built ones often don’t.
• Switch Control (iOS) / Switch Access (Android) users scan through items and pick actions from a menu. Drag-only features (reordering, sliders without +/− buttons) are often impossible for them.
• Voice Control users say “Tap Delete”. That only works if a visible, labeled button exists.
• WCAGWCAGThe Web Content Accessibility Guidelines, the main international standard for accessibility.Open in glossary → 2.5.1 Pointer Gestures (Level A): anything that needs a multi-finger or path-based gesture (swipe, pinch, drawing a shape) must also work with a single pointer without a path, such as a simple tap on a button. Examples: zoom buttons next to pinch-to-zoom, arrows next to a swipeable carousel.
• WCAG 2.5.7 Dragging Movements (Level AA, WCAG 2.2): anything done by dragging must also be possible without dragging, such as “Move up / Move down” buttons for a reorderable list.
• WCAG 2.5.2 Pointer Cancellation (Level A): actions should fire when the finger lifts, not when it touches down, so users can slide off a button to cancel.

Haptic feedback

A light vibration (a “haptic”) confirms that something happened without looking: the long press fired, a swipe passed the point of no return, a toggle snapped. iOS Mail gives a tick when a full swipe crosses the delete threshold; Android gives one when a long press is recognized.

Test that haptics are present where expected, not overused (a buzz on every scroll item is annoying), and that the app respects the system setting (iOS Settings › Sounds & Haptics › System Haptics, Android Settings › Sound & vibration › Vibration & haptics). You can’t feel haptics in a simulatorSimulatorSoftware that imitates a device's behavior on your computer, like Apple's iOS Simulator.Open in glossary → or emulatorEmulatorSoftware that imitates a real device's hardware and OS on your computer, like the Android Emulator.Open in glossary →, so this needs a real deviceReal deviceA physical phone or tablet used for testing, as opposed to an emulator or simulator.Open in glossary →.

What to test

Basic recognition

• Every tappable item reacts to a single tap, and nothing happens twice on a fast double tap (see double submitDouble submitA bug where an action runs twice because the user tapped or clicked twice quickly.Open in glossary →).
• Long press opens its menu after about 0.5 s, with visual and haptic feedback, and the tap action does not also fire.
• Swipes trigger only past a clear threshold; short or slow swipes snap back.
• Pinch zoom has sensible minimum and maximum levels and keeps the point under your fingers in place.

Conflicts and edges

• Scroll lists diagonally over swipeable rows and carousels.
• Swipe back from the left edge (and the right edge on Android) on every screen, including screens with swipeable content.
• Pull to refresh once, twice quickly, and while a refresh is already running. Watch the network log.
• Start a gesture and cancel it: drag back to the start, slide off the button, or get interrupted by a call or notification.

Recovery and accessibility

• Destructive gestures have an Undo or confirmation.
• Every gesture action is also available through a visible button or menu.
• Everything works with VoiceOver, TalkBack, Switch Control and Voice Control.
• Long press respects the system touch-and-hold delay.

Common bugs

Find the bug

This mail app supports swiping, long press and pull to refresh, and it has six gesture bugs. Everything works with a mouse too: drag to swipe or scroll, press and hold for the menu. Explore it like a tester:

• Swipe a row a little, then a lot. Scroll the list by dragging, not perfectly straight.
• Try to delete an email without swiping.
• Press and hold an email, then let go.
• Pull to refresh and keep an eye on the spinner and the network log.

Tools and how-to

adb shell input tap 540 1200                    # tap
adb shell input swipe 540 1200 540 1200 800     # long press (800 ms in one spot)
adb shell input swipe 900 1200 300 1200 150     # fast swipe left
adb shell input swipe 900 1200 860 1200 300     # tiny 40 px swipe: is that enough to delete?

Example test cases

Checklist

Check your understanding

Next up: what happens to all of this when the user turns the phone sideways, in Orientation and Screen Sizes.