The Buzz That Either Clicks or Grates

You press the shutter button. The phone gives a tiny, crisp knock against your palm: satisfying, done, move on. Now think about the last budget phone you borrowed. Same action, but the vibration was a low, trailing rattle that felt like something was loose inside. You tapped again just to make sure it registered.

Same feature. Completely different experience. The gap between them isn't a mystery or a matter of taste. It's specific engineering, and once you see it, you can't unfeel it.

The Motor That Does the Work

Almost every phone uses one of two types of vibration motor. The older, cheaper kind is an ERM: an Eccentric Rotating Mass motor. A small DC motor with a lopsided weight on the shaft. It spins, the weight creates imbalance, the phone shakes. Simple, cheap, and the reason budget phones feel like they're buzzing through a tin can.

ERMs have a significant lag between receiving a signal and producing any sensation, often 20 to 30 milliseconds, and they coast after the signal cuts off. The vibration lingers. You can't make a crisp sensation with a motor that takes time to spin up and can't stop on command.

The better kind is an LRA: a Linear Resonant Actuator. Instead of spinning, it drives a small mass back and forth along a single axis using a voice coil, the same basic principle as a speaker. Because it's not fighting rotational inertia, it can start and stop in under 10 milliseconds. That's what lets a phone deliver a sensation that feels like a distinct tap rather than a smear.

Apple calls their version the Taptic Engine. The hardware inside is a refined LRA, but the name matters less than what it enables: a motor precise enough that software can script individual waveforms, not just toggle a buzzer on and off.

Waveforms: Where It Gets Interesting

Here's the part most guides skip entirely. The motor is only half the story.

An LRA by itself is just a capable instrument. What you actually feel depends on the waveform the software sends to it. Think of it like a speaker driver: the component can reproduce almost anything, but feed it a single monotone signal and that's all you'll hear. Haptic feedback works the same way. A well-designed system fires a precisely shaped pulse: a sharp attack, maybe a brief sustain, then a controlled decay. That profile is what makes a digital keyboard tap feel like a physical keypress rather than a coincidental vibration.

Android's Vibration API has supported waveform composition for years, letting developers specify amplitude and timing in milliseconds. Apple's Core Haptics framework goes further, letting developers control both intensity and sharpness on a continuous curve. The result is a vocabulary of sensations: a light tick for selecting text, a heavier thud for an error, a rapid double-pulse for a notification that feels different from a call.

Put those two things together, a fast LRA and a thoughtfully scripted waveform, and you get haptics that feel like part of the interface rather than a side effect of it.

What People Get Wrong

The common assumption is that stronger equals better. It doesn't.

A phone vibrating at maximum amplitude for every interaction is exhausting, and more importantly, it destroys meaning. Haptics are most useful when they carry information through variation: a long, heavy buzz for a destructive action; a light tick for each item you scroll past; a sharp double-tap confirming a payment went through. When everything is the same intensity, none of it communicates anything. It's the tactile equivalent of a car alarm that nobody looks up for anymore.

The other mistake: blaming the software when the hardware is the actual bottleneck. A developer can write the most elegant Core Haptics waveform imaginable, but if the device has a cheap ERM motor, the output will still feel mushy. The waveform instructions are there; the actuator just can't execute them with enough precision. It's like sending a lossless audio file to a 99-cent speaker.

A Tale of Two Phones

Consider two people who both buy a mid-range phone in the same product cycle, one from a manufacturer that invested in a custom LRA and one from a manufacturer that used a standard ERM to hit a price target.

Sarah's phone delivers a keyboard that feels responsive enough that she turns off the click sounds within a week. The haptic alone is convincing. She also notices that the "slide to confirm" gesture on her banking app has a satisfying ratchet quality, each little step distinct.

Marcus's phone buzzes when he types, technically. But the sensation arrives slightly late and then trails off. After a month he's turned keyboard haptics off because they feel disconnected from his taps rather than tied to them. He still gets vibration alerts for calls. The finer tactile vocabulary the app developers designed? Gone entirely.

Same apps. Same code. Different hardware. Marcus isn't getting a worse haptic experience so much as he's getting no haptic experience at all.

Resonance and the Chassis Factor

One last variable that almost nobody talks about: the phone's physical chassis changes how vibration propagates to your hand.

A glass-and-aluminum body transmits vibration cleanly, with relatively little damping. The sharp pulse from an LRA arrives at your fingertips close to what the motor produced. A thick polycarbonate shell, or a phone with a lot of internal air gaps and loose-fitting components, acts like insulation. It absorbs and scatters the vibration before it reaches your skin, turning a precise waveform into something vague and diffuse.

This is why two phones using nominally similar LRA hardware can still feel meaningfully different. It's not just the actuator. It's the whole acoustic path from the motor through the chassis to your palm. Good haptic design accounts for this: engineers tune the waveform to compensate for how that specific device body will modify the signal, which is why haptic calibration happens on physical prototypes, not in simulation.

So why does your friend's phone feel noticeably better than yours even though the spec sheets look similar? This is probably why.

The phones that feel best aren't simply the ones with the most expensive motors. They're the ones where someone sat with a prototype and kept adjusting until the tap felt right.

That last step is the one you can't buy off a component spec sheet.