Long Press

Long press is a touch gesture triggering secondary actions or context menus after a sustained touch (300-500ms).

stellae.design

Design Principles

Long press triggers secondary actions after holding a finger on an element for 300-500ms. Common uses: context menus, edit/rearrange mode, content preview (peek), alternate actions. Like swipe, it has discoverability problems — nothing suggests holding longer does something different. Always treat as a shortcut, never the sole path.

Why It Matters

Long press is a foundational touch gesture that unlocks secondary actions, contextual menus, and progressive disclosure without cluttering the primary interface. When calibrated correctly — typically between 300ms and 500ms — it feels intentional and natural, giving power users fast access to advanced functionality while keeping surfaces clean for casual users. Poorly implemented long press creates discoverability gaps, because users who never stumble upon the gesture miss entire layers of functionality hidden behind it.

Real-World Examples

iOS home screen app rearrangement

Long-pressing an app icon on iOS triggers a contextual quick-action menu, and continuing to hold enters jiggle mode for rearranging or deleting apps. The two-stage response gives users a clear escalation path — a brief press reveals shortcuts, a sustained press enters edit mode. Haptic feedback at each threshold confirms the state transition without requiring the user to look for on-screen cues.

WhatsApp message reactions

WhatsApp uses long press on a message bubble to surface a row of emoji reactions and a contextual menu with reply, forward, and delete options. The gesture keeps the conversation view uncluttered while making power actions immediately accessible to experienced users. The slight scale-up animation on the message bubble provides instant visual confirmation that the system registered the sustained touch.

Counter-example

Long press as the only way to delete items

A task management app hides the delete action exclusively behind a long press with no swipe-to-delete, menu option, or edit mode alternative. New users search the interface for minutes without discovering how to remove completed tasks, eventually assuming the feature does not exist. Relying on a single hidden gesture for a critical action creates a severe discoverability failure.

Role-Specific Guidance

Common Mistakes

• The most frequent mistake is making long press the sole entry point for important actions without any visible affordance or onboarding hint, leaving the majority of users unaware the action exists. Another error is setting the hold duration too short, causing accidental triggers during normal scrolling, or too long, making the interaction feel sluggish and unresponsive. Teams also forget to provide cancel-on-drag behavior, so users who begin scrolling accidentally fire long-press actions and land in unexpected states.