Tap a control on a phone and you may feel a tiny click even though nothing physically moved. Type on an on-screen keyboard and each key can seem to answer your finger. That sensation is haptic feedback: information a device communicates through touch.
Haptics are easy to dismiss as ordinary vibration, but modern devices can use carefully timed physical motion to make an interaction feel more definite. A short pulse can confirm a selection, mark a boundary on a slider, or tell you that a long press has been recognised without requiring you to keep watching the screen.
Understanding the basic mechanism also explains why haptics feel different between devices, why a strong vibration is not necessarily a good one, and why turning haptic feedback off changes more than notification buzzing.
Haptics turn a software event into physical motion
A touchscreen has no moving key beneath your finger. When you tap it, the device detects the touch electronically and software decides what that touch means.
If the interface calls for haptic feedback, the operating system sends a command to hardware called a haptic actuator. An actuator converts electrical energy into mechanical movement. In this case, that movement produces a vibration or pulse that you can feel through the device.
The sequence is simple:
- You perform an action, such as tapping a virtual key.
- The device recognises the action.
- Software requests an appropriate haptic effect.
- The actuator moves according to that request.
- You feel the resulting motion through your finger or hand.
The physical response can arrive so close to the visual change that the two seem like one event. The screen still did not mechanically click; the device created a separate touch sensation to accompany the software action.
A haptic effect is more than on or off
The simplest vibration hardware can produce a basic buzz. More capable haptic systems can control the motion more precisely, allowing short taps, longer vibrations, and patterns with different perceived strengths or textures.
Software may vary properties such as duration and intensity. On suitable hardware, the system can also shape a vibration over time or use changes in vibration frequency to create different sensations. The exact controls available depend on the actuator, its driver electronics, the operating system, and the device manufacturer’s implementation.
This is why two phones can respond to the same kind of interface event very differently. One may produce a crisp, brief tap while another produces a softer or more noticeable buzz.
A useful distinction is between haptic feedback and vibration as a general alert. Both can use the same underlying actuator, but their purposes differ. A call or alarm may use a relatively long pattern to attract attention. Interface haptics are commonly brief and tied closely to a particular action.
The actuator determines what the device can reproduce
Not every vibration mechanism behaves the same way.
Some designs use a small motor with an off-centre rotating mass. As the mass spins, its imbalance shakes the device. This approach can create an obvious vibration, but starting and stopping a spinning mass takes time.
Other devices use actuators that move a mass back and forth rather than continuously spinning it. Designs such as linear resonant actuators, often shortened to LRAs, can be driven to produce controlled oscillation and can support sharper responses when the hardware and control system are designed for it.
There are other actuator technologies as well, and manufacturers do not all use identical hardware. The practical point is that software cannot create any imaginable physical sensation by itself. The actuator has limits on how quickly and strongly it can move and on the range of effects it can reproduce.
That is one reason an app or operating system may use predefined haptic effects instead of assuming every device can reproduce the same custom pattern. On platforms with many hardware designs, supported haptic capabilities can vary substantially.
Timing makes a small vibration feel meaningful
The usefulness of haptic feedback depends heavily on when it happens.
Imagine dragging a volume control. If the device produces a small pulse exactly when the control reaches a meaningful step, the sensation can act like a physical marker. If the same pulse arrives noticeably after the visual change, it feels disconnected from the action.
The same principle applies to typing. A short response aligned with a recognised key press can make an on-screen keyboard feel more responsive. A long vibration after every character would slow the perceived interaction and quickly become distracting.
Haptics therefore work best as information, not simply as extra movement. The pattern, timing, and strength should correspond to something the user can understand: a selection changed, a limit was reached, an action succeeded, or attention is required.
Haptics can reduce the need to watch the screen
Visual feedback is useful only when you are looking at it. Sound can communicate without sight, but audible feedback may be undesirable in a quiet room or noisy environment.
Touch provides another channel.
For example, a brief pulse can confirm that a control was activated while your eyes remain on another part of the screen. A sequence of pulses can distinguish a notification from a simple interface tap. Wearable devices can use touch especially effectively because the actuator is already in contact with the body.
Haptics normally complement visual or audible information rather than replacing it completely. A vibration by itself may be ambiguous: without context, you may not know whether it represents a message, an error, or an interface action.
Stronger haptics are not automatically better
A stronger vibration is easier to notice, but noticeability is not the only goal.
Repeated strong pulses can become tiring or irritating, especially during frequent actions such as typing or scrolling through controls. Longer or stronger effects also require the actuator to operate more, which uses energy. The battery effect of occasional short feedback may be small in normal use, but haptic activity is still not free.
Physical construction matters too. A vibration that feels controlled while a phone is in your hand may make the device buzz audibly when it is lying on a hard table. A case can also change how the motion feels or sounds.
Good haptic design therefore depends on context. A subtle selection change and an incoming call have different jobs and do not need the same physical response.
Why an app’s haptics may not feel the same on every device
Applications generally request haptic effects through operating-system interfaces rather than directly controlling an actuator as if it were a raw motor.
The platform and device then determine how to reproduce the request using the available hardware. Some devices support richer effects than others, and operating systems can expose different sets of predefined or custom haptic capabilities.
System settings can also matter. Depending on the platform and device, users may be able to disable certain touch feedback, change vibration intensity, or control notification and interface vibrations separately. Names and available controls vary, so an app cannot assume that every requested effect will be felt exactly as its designer intended.
This variation is normal. A haptic instruction describes a desired physical response, but the final sensation depends on both software and hardware.
Haptic feedback is not the same as force feedback
The terms are sometimes used loosely, but they are useful to separate.
Haptic feedback is the broad idea of communicating through touch. The small pulse from a phone after a tap is haptic feedback.
Force feedback usually refers more specifically to hardware that applies forces that resist or guide movement. A game steering wheel that pushes against your hands as the simulated car turns is a familiar example.
A phone vibration does not normally push your finger along a controlled path or physically stop it from moving. It creates a tactile sensation instead. Both belong to the wider world of touch-based feedback, but they produce different kinds of physical interaction.
When changing haptic settings makes sense
If interface vibrations feel distracting, disabling or reducing them is a reasonable preference. Doing so does not usually disable the touchscreen itself; touch detection and haptic response are separate parts of the interaction.
Before turning off all vibration, however, check what the setting actually controls. Devices may separate keyboard feedback, system touch feedback, calls, alarms, and notifications. The labels and grouping differ between operating systems and versions.
If a device suddenly feels unusually weak or harsh, also consider physical factors. A different case, a loose surface, or simply holding the device differently can change how vibration is transmitted. Comparing the same effect while holding the device normally can help distinguish a settings change from the way the vibration is reaching you.
The useful mental model
Haptic feedback is a physical message generated by hardware under software control. The software decides that an interaction deserves a touch response; the actuator turns that request into motion; and the device’s construction determines how that motion reaches your hand.
That model explains why a glass touchscreen can appear to click, why different devices feel different, and why haptic settings can change the character of an interface without changing what the screen detects.
The most effective haptics are not necessarily the strongest or most complex. They are the ones whose timing and sensation make an action easier to recognise without demanding extra attention.