Haptic feedback on Android: confirm actions without looking

On a phone used in the field, the user's eyes belong on the shelf, the meter or the road, not on the screen. Good feedback lets them feel and glance rather than read: a short vibration says "done", a brief notice says what changed, and Undo fixes the rare mistake.

Why feedback matters more on a phone

On a desktop, the cursor and a big screen make it obvious whether a click worked. On a phone, the finger covers the button it pressed, the screen is small, and the user is often looking somewhere else. Without feedback, people are left guessing whether the tap registered, and the usual response to uncertainty is to tap again, which doubles the action.

Feedback has three jobs on a small screen:

• Acknowledge the touch instantly, so the user knows the app heard them.
• Confirm the outcome, so they know what changed.
• Offer a way back, so a mistake costs one tap instead of a frustrated search.

Eyes-free interaction with haptics

A vibration is the one signal that reaches the user whether they are looking at the screen or not, in a noisy warehouse where a sound would be lost, and in a quiet meeting where a sound would be rude. That makes haptic feedback the natural confirmation for repetitive, eyes-free tasks:

• counting items on a shelf while looking at the shelf,
• ticking off a checklist while walking a site,
• scanning or logging something while holding it in the other hand.

After a few dozen actions, users stop looking at the screen to check each one. They feel the tick and move on. That is the moment the app gets out of the way.

Choosing the right kind of vibration

Android offers predefined haptic effects tuned for each device's motor. Use them instead of raw vibration durations: they feel crisp on good hardware and degrade gracefully on cheap phones. Keep a small, consistent vocabulary.

Avoid long or repeated buzzing. A vibration that lasts longer than the action feels like an alarm, drains battery, and trains people to switch haptics off entirely.

Adding haptic feedback in Jetpack Compose

In Compose, get the current HapticFeedback from LocalHapticFeedback and call performHapticFeedback when an action succeeds. HapticFeedbackType.LongPress and TextHandleMove work on every Compose version; recent Compose releases add more specific types such as Confirm, Reject and SegmentTick.

@Composable
fun CountButton(label: String, onCount: () -> Unit) {
    val haptics = LocalHapticFeedback.current
    Button(
        onClick = {
            onCount()
            haptics.performHapticFeedback(HapticFeedbackType.LongPress)
        },
        modifier = Modifier.heightIn(min = 64.dp)
    ) {
        Text(label, fontSize = 20.sp)
    }
}

System haptics respect the user's settings: if they have turned touch feedback off, these calls do nothing, which is exactly what you want. Do not work around that setting with the raw vibrator service.

The Thumb Inventory example wraps every stock change in one helper that performs a haptic tick and then updates the count, so every action feels the same and no code path forgets the feedback.

Visual feedback that reads at a glance

Haptics say "something happened". The screen should say "what happened" in a form that is readable in a glance from arm's length:

For tips on making those numbers and labels legible outdoors and at large font sizes, see readable text and contrast.

Short notices with Undo

A short notice at the bottom of the screen, a snackbar, closes the loop: it names the change in plain words and offers Undo. It appears in the thumb zone, does not block the screen, and disappears by itself.

val snackbarHostState = remember { SnackbarHostState() }
val scope = rememberCoroutineScope()

fun announce(message: String, undo: () -> Unit) {
    scope.launch {
        snackbarHostState.currentSnackbarData?.dismiss()
        val result = snackbarHostState.showSnackbar(message, actionLabel = "Undo")
        if (result == SnackbarResult.ActionPerformed) undo()
    }
}

Dismiss the previous notice before showing a new one. When someone taps quickly ten times, they want to see the latest state, not a queue of ten messages playing out over the next minute.

Write notices as outcomes, not as system messages: "Milk −1 · now 3" is more useful than "Item updated successfully".

Feedback that works for everyone

Not everyone feels, sees or hears feedback the same way. Layer the signals so that losing one still leaves the others:

• Haptic tick for people looking away.
• A visible change for people with haptics off or a weak vibration motor.
• Text in the notice so TalkBack announces it; snackbars are announced automatically.
• For custom status text, mark it with Modifier.semantics { liveRegion = LiveRegionMode.Polite } so screen readers read updates.

Combined with the gesture guidance in touch targets and gestures, this gives an interaction loop that is fast, forgiving and usable without looking. You can try it on your own phone in a few minutes with the quick start.

Frequently asked questions