Phone Haptics Explained: Why Some Vibrations Feel So Much Better Than Others

Every phone buzzes, but not every buzz feels the same. Pick up a recent iPhone and tap a keyboard key, and the click feels almost mechanical, a crisp little snap that stops instantly. Pick up a budget Android phone and do the same thing, and the vibration often feels mushy, a dull rumble that starts a beat late and keeps shaking after your finger has already moved on. That difference isn't random, and it isn't really about software polish either, even though software plays a role. It comes down to what kind of haptic motor is physically inside the phone and how tightly the software driving it is tuned to that specific piece of hardware.

The two kinds of vibration motor

Almost every phone sold today uses one of two fundamentally different types of vibration hardware. The older, cheaper design is an eccentric rotating mass motor, often shortened to ERM, which is essentially a tiny electric motor spinning an off-center weight. Because it relies on a physical motor spinning up and down, an ERM motor is inherently slow to start and slow to stop, which is why cheap phones tend to feel like they're vibrating for slightly longer than the tap that triggered it, with a soft, imprecise rumble rather than a sharp tap.

The design used in nearly every flagship phone now, including Apple's Taptic Engine and the linear motors found in Samsung's Galaxy S and Google's Pixel lines, is a linear resonant actuator, or LRA. Instead of spinning a weight, an LRA moves a magnetic mass back and forth along a single axis, driven electromagnetically, similar in principle to a tiny speaker driver. Because there's no motor that needs to physically spin up, an LRA can start and stop moving almost instantly, which is what allows it to produce short, sharp, precisely timed pulses instead of a lingering buzz. That speed is the entire reason high-end haptics feel so much more like a real mechanical click than a vibration.

Why the click feels so different

The sensation of a crisp haptic tap comes from a property engineers call rise time, essentially how quickly the motor goes from standing still to peak movement and back to standing still again. A well-tuned LRA can complete an entire pulse in well under 50 milliseconds, fast enough that your finger perceives it as a single, discrete event rather than a continuous buzz. Apple's implementation goes further by pairing the Taptic Engine with a closed-loop control system that constantly measures the motor's actual movement dozens of times per second and adjusts the drive signal in real time, which is part of why the same haptic feedback feels consistent whether the phone is resting on a hard table or being held loosely in a hand, two situations that would otherwise produce noticeably different vibration intensity from an open-loop system.

This is also why software matters almost as much as the motor itself. A phone's operating system has to translate an abstract event, a keyboard press, a notification, the click of a virtual button, into a specific waveform sent to the motor: how strong, how long, whether it's a single pulse or a rapid double-tap pattern. Apple ships dozens of distinct pre-tuned haptic patterns as part of iOS specifically because a generic "buzz for 40 milliseconds" instruction produces a noticeably worse result than a waveform engineered for that exact motor's resonant frequency. Android's haptics have historically been more inconsistent across manufacturers precisely because Google's base APIs allow phone makers to implement their own tuning, and cheaper devices often ship with minimal effort put into that layer even when the underlying motor hardware is reasonably capable.

Where haptics actually matters beyond typing

Keyboard feedback is the most noticeable daily use case, but it's far from the only one. Fingerprint sensors use a quick haptic pulse to confirm a successful unlock without you needing to look at the screen, camera apps use it to confirm a photo was captured (a small companion cue to the camera hardware actually doing the work), and navigation apps increasingly use distinct vibration patterns, a long pulse for a turn coming up, two short pulses for "you've arrived", so you can get directional cues without glancing at the screen while driving or walking. Gaming is another growing use case: modern game engines can trigger haptic patterns tied to in-game events, a controller-style rumble when a car crashes or a weapon fires, something that was essentially impossible on ERM motors because they simply couldn't respond fast enough to feel synchronized with on-screen action.

Accessibility is arguably the most underrated application. For users with visual impairments, distinct haptic patterns paired with VoiceOver or TalkBack provide a non-visual confirmation channel that's faster and less intrusive than audio feedback, particularly useful in quiet public settings where audio cues aren't practical. This overlaps with how phone makers think about other sensor-driven confirmation systems, the same instinct that shaped how in-display fingerprint sensors pair a scan with instant tactile confirmation rather than making users wait for a visual checkmark.

Why some phones still feel worse than others

Cost is the obvious factor: a well-tuned LRA with a closed-loop haptic driver costs more than a basic ERM motor, so budget phones frequently cut this corner even when the rest of the spec sheet looks competitive. But physical space matters too. A larger, higher-quality LRA needs more internal volume than manufacturers always want to spare, especially in slim phones where battery capacity and camera modules already compete aggressively for the same limited space, which is one of the quieter tradeoffs buyers rarely see listed next to specs like RAM and storage capacity but that affects how premium a phone feels in daily use just as much as raw performance numbers do.

There's also a genuine engineering ceiling for how good haptics can get on a phone at all, compared to something like a game controller. A phone's LRA has to be small and thin enough to fit inside a device that's also trying to house a battery, cameras, and a display, while a dedicated controller like a DualSense can afford much larger, more powerful actuators purely dedicated to haptic feedback. That's why even the best phone haptics, impressive as they've become, still can't replicate the nuanced rumble variation that dedicated gaming hardware produces, and why phone haptics are best understood as a refinement of an existing sensation rather than a wholly new one.

What to actually check before buying

Spec sheets almost never list haptic motor type or quality, which makes this one of the few phone characteristics you genuinely have to feel in person, or trust a hands-on review for, rather than compare on paper. If you can test a phone before buying, type on the on-screen keyboard with haptic feedback enabled and compare it directly against a phone you already own; the difference between a well-tuned LRA and a cheap ERM motor is immediately obvious once you feel both back to back, in a way that's hard to describe accurately in a spec sheet but impossible to miss in person. It's a small detail, but it's one of the clearest examples of how a phone's perceived quality comes from dozens of these unglamorous engineering choices rather than any single headline spec.