A swipe leaves no trace and needs a visual hint that it exists

What it is

A swipe occupies no control and leaves no mark on the current page. The next person facing the same card cannot see that pulling sideways will reveal another. Swipes therefore live on hints: a neighbor peeking, page dots, a cut that looks slideable, content cropped by the edge. Without a hint, a swipe exists only for people who already learned it.

Why it happens

A button is recognized by shape and label. A swipe is inferred from spatial structure—“this is cut off, so there is more outside.” A peek leaves a strip of the next card in the viewport, drawing the command as space. Page dots are weaker symbolic recognition and do not teach how a direction feels. A first slight follow (a rubber band, or the neighbor moving with the finger) turns a probe into a visible consequence, closer to the motion than a caption. The hint has to sit on the surface where the swipe will happen. “Swipe left for more” in the top bar, detached from the sliding region, is no hint.

Studying it

First use, no briefing: one card that looks complete versus one that peeks a neighbor. Measure spontaneous swipe rate, first-attempt direction, and time until people give up and tap a button. Eye tracking shows whether the peek is dismissed as an object edge. A next-day retest should keep discovery if the hint remains; a tutorial layer that is gone often will not. Do not ask “do you think this can slide”—self-report counts people who just learned it as people who “already knew.”

Where it stops holding

Fullscreen video and game HUDs have no room for a peek; hints move to a brief edge glow or neighbor-follow on first touch, signals that vanish, so long-term discovery stays weak. In right-to-left reading layouts, which side peeks changes the inferred direction. System photos and home launchers are already trained as “of course it slides,” so hints can be quieter; a tool canvas has no such convention. Hints for revealing actions on a list row (in-row coaching, a one-time lesson) are a different set; do not mix them with whole-page peeks.

Applying it

• On the swipe axis, show the neighboring state: the next card’s edge, a photo cut by the frame, dots with the current one enlarged. On first contact let content move a little and rubber-band back, telling people the axis is live.
• Put copy next to the sliding region, not in an unrelated navigation bar.
• Sit someone new in front of the UI, say nothing, and watch 15 seconds: do they swipe toward the hint? If everyone taps the only visible button, add a peek before adding the sentence “try swiping.”

Related

• Same group: C3.05.1 A swipe is jointly classified by direction, distance, and velocity · C3.05.2 Angular tolerance on a swipe sets the misclassification rate · C3.05.3 A swipe-triggered action should be undoable by a reverse swipe
• Adjacent: C3.20 Gesture discoverability · C3.17 Swipe actions
• Search: gesture affordance · peek hint · carousel peek