pointerInput & detectTapGestures

To handle raw touch in Compose you reach for the pointerInput modifier. It gives any element a place to read finger events directly. 👆

Attach pointerInput in a Modifier chain. Inside its lambda you get a gesture scope where you can listen for taps, drags, and more.

The friendliest helper is detectTapGestures. It bundles tap, double tap, long press, and press into one tidy call for you.

The onTap lambda fires when a finger presses and lifts without moving much. It receives the Offset where the tap landed.

Pass onDoubleTap to react to two quick taps in a row. It is perfect for a like or zoom shortcut on an image. 💙

The onLongPress lambda fires after the finger stays down past a threshold. Use it to open context menus or selection mode.

Use onPress to know the moment a finger touches down. Its lambda is suspendable, so you can await release or cancellation.

Each tap callback hands you an Offset in pixels, measured from the top-left of the composable. Read it to know exactly where the user touched.

The first argument to pointerInput is a key. When it changes the gesture block restarts, so pass any state your handlers depend on.

The pointerInput block is a suspend scope. That is why detectors can await events frame by frame without blocking the UI thread.

One detectTapGestures call can take tap, double tap, and long press together. Compose figures out which one the user meant.

Which helper bundles tap, double tap, and long press into one call?

You met pointerInput and detectTapGestures for tap, double tap, and long press. They are your foundation for custom touch handling. 🎉