Long press

Problem Context

• A touch-first surface has objects, cards, rows, messages, files, canvas items, map markers, or media that support secondary actions.
• The same target may also support tap-to-open, double tap, swipe action, drag pickup, text selection, scroll, context menu, hover tooltip, or popover.
• Users may need selection mode, item actions, preview, inspect details, reorder pickup, copied text actions, or temporary reveal.
• The product must support users who cannot sustain contact, cannot keep a pointer still, use keyboard or switch control, use a screen reader, or interact with a mouse and trackpad.

Selection Rules

• Choose long press when the design problem is a sustained-contact gesture and its threshold, feedback, cancellation, and equivalent action path.
• Use touch gesture when the question is the broader vocabulary and fallback contract across tap, swipe, pinch, drag, and other gestures.
• Use context menu when the main question is the menu surface, command grouping, focus movement, and target-specific command scope after invocation.
• Use tooltip when the surface only supplies short supplemental text and no interactive controls.
• Use popover when the target opens nonmodal contextual content with richer text or controls.
• Use action menu when commands should be opened from a visible trigger instead of relying on sustained contact.
• Use swipe action when a horizontal row gesture reveals or commits an item action.
• Use drag and drop when sustained contact is only the pickup phase for moving an object to a destination.
• Provide a visible More actions button, menu, checkbox, shortcut, or custom action for every long-press-only outcome.
• Do not use long press for primary, urgent, destructive, payment, consent, account, security, or required instructions.

Required States

• Idle target state with visible identity and alternate action path.
• Gesture hint state that teaches touch and hold without relying on hover.
• Press down state that identifies the target before threshold.
• Hold progress state showing duration or affordance before action fires.
• Threshold reached state with haptic, visual, or status feedback.
• Release-before-threshold cancellation state that leaves data unchanged.
• Movement-tolerance cancellation state when the user scrolls, swipes, drags too far, or leaves the target.
• Context menu, preview, selection mode, or drag-pickup destination state after threshold.
• Disabled or unavailable long-press state with explanation.
• Equivalent action-menu, visible control, keyboard, screen reader, switch, and pointer path.
• Destructive or high-impact action handoff to undo, confirmation, or review.
• Mobile compact, large-text, one-handed, landscape, and assistive-touch states.

Interaction Contract

• Long press starts only from a target that intentionally supports sustained contact.
• The interface gives press-down feedback immediately and progress or dwell feedback before threshold when the delay is noticeable.
• The gesture cancels cleanly if the user releases before threshold, moves beyond tolerance, begins vertical scroll, starts an incompatible swipe, or presses Escape on an equivalent path.
• Crossing threshold opens a named destination such as context menu, selection mode, preview, inspect panel, or drag pickup rather than performing an unexplained action.
• Tap, double tap, swipe action, pull-to-refresh, drag, and system gestures have explicit priority rules against long press.
• Every outcome is available through a non-gesture equivalent with matching disabled, pending, success, and recovery states.
• Destructive outcomes after long press require explicit tap, confirmation, or undo according to reversibility.
• Status messaging names the target and action when long press changes selection, opens actions, or completes work.

Implementation Checklist

• Inventory each long-press target, purpose, duration threshold, movement tolerance, destination, action scope, and equivalent control.
• Decide whether long press opens a context menu, enters selection mode, shows preview, starts drag pickup, reveals hidden controls, or performs another specific outcome.
• Add visible teaching such as More actions, selection checkbox, handle, hint text, or onboarding only where users need to discover the shortcut.
• Implement press-down feedback, progress feedback, haptic feedback where platform appropriate, threshold reached state, cancellation, and release behavior.
• Resolve conflicts with tap, double tap, scroll, swipe action, pull-to-refresh, drag pickup, text selection, hover tooltip, popover, and system gestures.
• Expose the same actions through buttons, menus, keyboard, screen reader custom actions, context menu key, switch control, or other assistive paths.
• Route destructive or high-impact outcomes through confirmation, undo, delayed commit, or review rather than committing on threshold.
• Test slow tap, tremor, accidental movement, long text selection, nested scrollers, one-handed use, large text, screen reader touch exploration, keyboard, switch, mouse, trackpad, stylus, and mobile landscape.

Common Generated-UI Mistakes

• Hiding required or primary actions behind undiscoverable long press.
• Using long press as a tooltip that contains required or interactive content.
• Committing destructive work as soon as the hold threshold is reached.
• Failing to cancel when users release early or start scrolling.
• Conflicting with swipe action, drag pickup, text selection, or pull-to-refresh on the same target.
• Providing no keyboard, screen reader, switch, mouse, or visible menu equivalent.
• Using hover hints to teach a touch gesture.
• Making the required hold duration too long, too short, or inconsistent across similar targets.

Critique Questions

• What exact outcome happens after the hold threshold: menu, selection, preview, drag pickup, or action?
• How do users discover that touch and hold is available before needing it?
• What hold duration, movement tolerance, and cancellation rules prevent accidental activation?
• What visible or accessible control performs the same outcome without sustained contact?
• How do tap, scroll, swipe action, pull-to-refresh, drag, text selection, context menu, and system gestures avoid conflict?
• What happens if the target becomes disabled, moves, or changes state during the hold?
• Does any destructive outcome require confirmation, undo, or explicit activation after reveal?