The Buzz That Isn't Really a Buzz
You scroll past a toggle switch and feel a small, satisfying click under your thumb. Pause on that. There's no moving part making that sensation. No physical notch, no ridge, nothing your fingernail could catch if you ran it across the glass. The surface is completely flat, and yet something just happened to your nervous system that felt unmistakably like texture.
That's not an accident. It's engineering disguised as instinct.
Modern smartphones use a component called a linear resonant actuator, or LRA. Forget the old cylindrical motors that spun an off-balance weight (those early Nokia handsets, coarse and buzzy, felt like holding a trapped wasp). An LRA works more like a tiny speaker driver. A magnetic mass oscillates back and forth along a single axis, driven by alternating current, completing the whole movement in milliseconds. Because nothing is spinning, it can start and stop almost instantly. That near-instant response is exactly what makes nuanced haptic feedback possible in the first place.
Apple calls its version the Taptic Engine. Google's Pixel line runs its own LRA, tuned differently. Same hardware category, wildly different software choreography on top.
How Software Sculpts What Your Skin Feels
Here's where things get genuinely strange.
Your fingertip doesn't process vibration the way your ear processes sound. Skin has mechanoreceptors, specifically Meissner's corpuscles and Pacinian corpuscles, that respond to different frequencies of pressure change. Pacinian corpuscles peak around 250 Hz. Meissner's corpuscles are most sensitive closer to 30-40 Hz. Fire a short 250 Hz burst and you get a sharp, crisp sensation. Drop to 150 Hz with a longer envelope and it reads as a dull thump. Layer two bursts 80 milliseconds apart and the brain stitches them into a single textured event rather than two distinct ones.
That's the core trick. The phone produces no physical texture whatsoever. It produces temporal patterns of vibration that your nervous system reconstructs as texture. The difference matters.
A worked example: when you drag a slider in iOS, the Taptic Engine fires a repeating series of pulses, each around 10-15 milliseconds long, spaced to match the pixel distance your thumb has traveled. Move slower and the pulses space out. Move faster and they compress. Your brain reads the changing rhythm as the sensation of moving over a ridged surface, like running a thumbnail along a comb. No comb exists. The phone is doing arithmetic on your thumb, and your thumb is completely taken in.
Two Phones, Same Hands, Different Worlds
Take Maya and Daniel, who both bought flagship Android phones in the same product cycle. Maya got a Pixel. Daniel got a Galaxy. Same LRA hardware category. Entirely different haptic vocabularies.
Maya taps a notification and gets a short, high-frequency pulse: tight, precise, gone. Daniel gets something slightly longer with a softer attack. Neither is wrong. Samsung's haptic library is tuned toward what focus groups called "satisfying." Google's is tuned toward what its engineers called "informative." That distinction sounds trivial until you switch phones and spend two weeks feeling like something is faintly off, the way a borrowed pen never quite writes the way yours does.
This tuning lives in the haptic pattern library, a set of waveform definitions that fire whenever a UI event triggers. Apple's Core Haptics framework lets developers define custom waveforms with specific intensity curves and sharpness values on a scale from 0.0 to 1.0. Sharpness above 0.5 routes toward the higher-frequency, crisper end of the LRA's range. Below 0.5, it shifts toward that low, thumpy register. A well-designed app uses different sharpness values for different actions: a light tap for scrolling past a list item, a heavier thump for a destructive action like deleting a file, a rapid double-pulse for an error.
The result is a haptic grammar. You learn it without knowing you're learning it.
What People Almost Always Get Wrong
The most common assumption is that stronger vibration equals better feedback. It doesn't, and I'd argue this misconception has produced a decade of mediocre haptics on otherwise excellent hardware.
Intensity is only one axis. Overdoing the amplitude on a long vibration just fatigues the mechanoreceptors. After roughly 300 milliseconds of continuous stimulation at the same frequency, your sensitivity drops sharply. That's why the best haptic designers use short, varied bursts rather than sustained rumbles. The goal isn't to be felt. It's to be interpreted.
There's also a persistent myth that haptic feedback is purely cosmetic, a premium flourish bolted on to justify a price tier. It isn't, and the evidence has been clear for years. Studies on motor learning consistently show that tactile confirmation of an action reduces error rates on touchscreens. When you feel the click of a virtual keyboard key, you make fewer double-taps and missed presses than when the feedback is absent or poorly timed. That window is unforgiving: haptic feedback delivered more than 50 milliseconds after a touch event starts to feel disconnected from the action, like a door that closes a half-second after you let go of the handle.
Have you ever noticed that typing on one phone just feels more accurate than another, even when the keyboards look identical? That's not imagination. That's the 50-millisecond window doing its job, or failing to.
The texture under your thumb isn't decoration. It's load-bearing information.
What this all adds up to is your phone running a real-time simulation of physical objects against your skin, and your nervous system falling for it completely. Every toggle, every swipe, every satisfying click is a small act of sensory fiction. The screen is flat glass. The texture is invented. Your thumb believes every word, and the people who designed that response spent years making sure it would.