Long Press — What It Is, the Long Touch Gesture in Apps

What Is Long Press?

Long Press is a multi-touch interface gesture where the user touches the screen and holds the finger still for a specified duration. The system does not react instantly: it waits for a timeout (usually 500 ms), and only after it expires does it recognize the gesture as Long Press. If the finger is released sooner — the gesture is interpreted as a regular Tap.

The gesture is a fundamental building block of modern mobile interfaces. Apple uses it to invoke context menus in apps (Messages, Safari, Files). Google integrated Long Press into text selection, icon rearrangement on the home screen, and context menu invocation in Android. In web interfaces, long press often emulates a right mouse click on mobile devices, where there is no physical right button.

Historically, Long Press emerged as an alternative to the context menu (right click) for touch screens. Early implementations appeared on devices with resistive screens (Palm, Windows Mobile in the early 2000s), but the gesture became standardized only with the advent of iPhone and Android. Both platforms' Human Interface Guidelines describe Long Press as a secondary action — not a replacement for Tap, but an extension of functionality.

How Long Press Differs from Tap

Long Press and Tap are two different gestures with different semantics. Tap is an instant press: the finger touches the screen and is released within 100–300 ms. Tap is always a primary action: open an app, press a button, follow a link. Long Press is a secondary action: open a context menu, start editing, show additional information.

Key rule: never use Long Press as the only way to perform an action. Users expect Tap to perform the primary action, and Long Press to open additional options. Violating this principle (for example, requiring a long press to open a link) leads to a negative user experience and reduced accessibility.

Long Press in iOS: UILongPressGestureRecognizer

UILongPressGestureRecognizer is the standard gesture recognizer in the iOS SDK for handling long press. It inherits from UIGestureRecognizer and supports configuration of minimum duration, allowable finger movement, and number of touches. The recognizer transitions to UIGestureRecognizerStateBegan after the timer expires, then to UIGestureRecognizerStateChanged when the finger moves, and UIGestureRecognizerStateEnded upon release.

// UILongPressGestureRecognizer with minimum duration configuration
class ContextMenuViewController: UIViewController {

    override func viewDidLoad() {
        super.viewDidLoad()

        let longPressRecognizer = UILongPressGestureRecognizer(
            target: self,
            action: #selector(handleLongPress(_:))
        )

        // Minimum hold time: 0.5 seconds
        longPressRecognizer.minimumPressDuration = 0.5

        // Allowable finger movement: 10 points
        longPressRecognizer.allowableMovement = 10

        customView.addGestureRecognizer(longPressRecognizer)
    }

    @objc func handleLongPress(_ recognizer: UILongPressGestureRecognizer) {
        guard recognizer.state == .began else { return }

        // Creating a context menu
        let location = recognizer.location(in: self.view)
        ContextMenuPresenter.show(at: location)
    }
}

Configuration parameters: minimumPressDuration — time in seconds before activation (default 0.5, for accessibility 0.65+ is recommended); allowableMovement — maximum finger movement in points (default 10, increasing helps with unsteady hands). iOS supports numberOfTouchesRequired for multi-touch gestures (e.g., long press with two fingers). The recognizer also integrates with UIContextMenuInteraction — when a context menu is added to a UIView via UIContextMenuConfiguration, Long Press automatically invokes the context menu without manual gesture implementation.

Long Press in Android: setOnLongClickListener

setOnLongClickListener is a View method in the Android SDK that sets a long press listener. When a user holds a View for more than 500 ms, the system calls onLongClick(). The method returns a boolean — true means the event was handled and should not propagate further, false means the event can be handled by other listeners. For more complex handling (finger movement after Long Press starts), GestureDetector with OnGestureListener is used.

// Example of setOnLongClickListener with haptic feedback
val itemView: View = findViewById(R.id.itemView)

itemView.setOnLongClickListener {
    // Haptic feedback to confirm gesture start
    it.performHapticFeedback(
        HapticFeedbackConstants.LONG_PRESS
    )

    // Showing context menu at element position
    val popup = PopupMenu(this, it)
    popup.menuInflater.inflate(R.menu.context_menu, popup.menu)
    popup.show()

    true // Event handled
}

GestureDetector provides finer control over the gesture. Unlike setOnLongClickListener, GestureDetector notifies about the start (onLongPress), movement (onScroll), and release. This enables complex scenarios — for example, starting a drag after a long press (Drag-and-Drop). OnGestureListener requires implementing six methods: onDown, onShowPress, onSingleTapUp, onScroll, onLongPress, onFling.

Where Long Press Is Used

Long Press is used in dozens of mobile interface scenarios. The most common application is the context menu: long press on a contact shows communication options (call, message, email), on a file — options (copy, move, delete), on text — selection and clipboard. The Android Launcher uses long press on an icon to move apps and add widgets.

Text selection is a classic example of Long Press on both platforms. In iOS, long pressing on text activates a magnifying glass for cursor positioning; on a word — selects it with handles. In Android, long press selects the entire word and shows an action bar (copy, cut, paste). Both platforms use subsequent handle dragging to expand the selection.

Preview — in iOS, long pressing a link in Safari or a message in Mail opens a content preview (peek). In Android, similar behavior is implemented via Long Press on a notification (expands the notification with action buttons). Photo apps use long press on a thumbnail for quick image preview.

Drag-and-Drop is often initiated by Long Press. The user holds the element, the system switches to drag mode, and finger movement moves the element across the screen. Android supports this scenario via View.startDragAndDrop() after Long Press. iOS uses UIDragInteraction, where drag interaction requires a long press to start dragging.

Best Practices for Using Long Press

Human Interface Guidelines of both platforms provide clear recommendations: Long Press should always be a secondary action. Never make long press the only way to perform a critical function. Users first try Tap — if Tap doesn't work as expected, they get frustrated. Add visual cues: context menus can be indicated by a three-dot icon, and elements supporting Long Press — by a visual hint on touch.

Haptic feedback is mandatory for Long Press. When the gesture is recognized, the device should confirm it with haptic feedback: in iOS this is UIImpactFeedbackGenerator with a light impulse, in Android — HapticFeedbackConstants.LONG_PRESS. Without haptic feedback, the user is not sure the gesture registered and may press again, causing unwanted actions.

Accessibility: not all users can perform a long press (people with motor impairments, elderly users). Always provide an alternative way to access Long Press actions — for example, via a "More" button in the interface or through system accessibility features (VoiceOver on iOS, TalkBack on Android). For iOS, you can add Custom Actions via UIAccessibilityCustomAction, which are available through the VoiceOver rotor.