What Is the Haptic Feedback on Your Phone and in Games?

What is the haptic feedback your phone keeps mentioning in its settings? It is the small tap, click or buzz you feel when you type, flip a switch or receive a notification. Haptic feedback is a device using your sense of touch to tell you that something happened. A small motor or actuator inside the phone, watch or game controller produces it, and well-made apps use it sparingly so that an action feels acknowledged without you having to look or listen.

What is the haptic feedback on a phone, exactly?

"Haptic" comes from the Greek word for touch. In technology it means any touch sensation a device produces on purpose, either in response to what you did or to get your attention.

On a phone it shows up in three places:

• Touch feedback. The tick under your thumb when you type, long-press an icon or drag a slider past a notch.
• Alerts. The vibration for calls, messages and alarms when the sound is off.
• App effects. A tap when a payment goes through, a double pulse when a form is rejected, the rumble of a game.

People often ask whether haptics and vibration are the same thing. The hardware is the same. The difference is intent. Vibration is a long buzz meant to be noticed from a pocket. Haptics are short, shaped effects meant to be felt in the hand while you are using the device.

How phones produce haptic feedback

Every phone that vibrates has a small component whose only job is to move a weight. There are two broad designs, and the difference between them explains why some phones feel precise and others feel like an angry bee.

Older vibration motors

The traditional design is a tiny electric motor with an off-centre weight on its shaft. When the motor spins, the lopsided weight shakes the whole phone. It is cheap and strong, but it takes a moment to spin up and a moment to stop, so everything it produces is a buzz. Strength and speed are tied together as well, because both depend on how fast the motor turns.

Linear actuators

Most current mid-range and flagship phones use a linear actuator instead. A weight sits on a spring and is driven back and forth along a single line by an electromagnet, a little like a miniature loudspeaker without the cone. It starts and stops quickly, which is what makes a crisp, single tap possible. Software can vary the strength and, on better hardware, the character of the effect. Apple calls its version the Taptic Engine, and Android manufacturers fit their own.

	Rotating vibration motor	Linear actuator
How it moves	An off-centre weight spins on a motor shaft	A weight on a spring moves back and forth along one line
Response	Slow to start and slow to stop	Starts and stops quickly
What it feels like	A buzz or rumble	Crisp taps and clicks, plus controlled longer effects
What software can control	Mostly on, off and duration	Strength, timing and, on some hardware, the sharpness of the effect
Where you find it	Older and low-cost phones, and the rumble motors in many game controllers	Most current mid-range and flagship phones, smartwatches and newer game controllers

This matters to anyone building an app, because Android hardware varies widely. An effect that feels like a neat click on one phone can come out as a rattle on a cheaper one.

What is haptic service on a phone?

Some Android users notice an entry with a name like "haptic service" in a list of system apps, running services or battery usage, and wonder what it is. I cannot tell you precisely what that entry does on your particular handset, because manufacturers use the name for their own components and I would be guessing.

In general terms, it is the part of the system that drives vibration. Apps never control the motor directly. They ask a system service to play an effect, and that service checks your settings, chooses a signal that suits the hardware and sends it to the actuator. Manufacturers add their own layers to tune effects for the specific actuator they fitted.

So a haptic service is most likely part of that plumbing. If it came with the phone, leave it enabled, since disabling a system component can remove touch vibration or cause other problems. If you simply want less vibration, use the sound and vibration settings.

Where apps use haptic feedback well

The best haptics are the ones you would only notice if they were taken away. They fall into four groups.

Confirmation

A single light tap that says "done". A payment accepted, a message sent, a toggle switched, a refresh completed. It lets the user look away sooner, which is useful when they are paying at a till or walking.

Errors and warnings

A distinct pattern, usually two or three quick pulses, that says "that did not work". A wrong passcode, a declined card, a required field left empty. It needs to feel different from success, or it teaches nothing.

Selection and boundaries

Small ticks as a picker wheel turns, a slider passes a notch, a dragged item snaps into place or a list reaches its end. These give physical texture to controls that are otherwise flat glass.

Vibration feedback for phones and games

Games are where haptics do the most work. Impacts, recoil, engine rumble and the texture of different surfaces all read more clearly when they are felt as well as seen. Console controllers have pushed this furthest: Sony's DualSense controller pairs detailed haptics with triggers that can resist your finger, and the Nintendo Switch has its own high-definition rumble. On a phone, a game uses the same actuator as the keyboard, so the range is narrower, but a well-timed pulse still makes a hit land.

The common thread is timing. A haptic that arrives a fraction late, or out of step with the sound and animation, feels broken.

What Apple and Android say about haptics, in general terms

Both platforms publish design guidance for haptics: Apple in its Human Interface Guidelines, and Google in its Android haptics documentation. I will not quote either, and both are worth reading in full. The principles they share are easy to summarise:

• Use the system's standard effects and use them for their intended meaning. Users learn what a success tap feels like across all their apps, and an app that uses it for something else confuses them.
• Be consistent. The same action should always produce the same effect.
• Support what is on screen. Haptics should accompany a visual change or a sound. They should not replace it.
• Use them sparingly. Feedback on everything becomes noise, and people switch it off.
• Prefer short, clear effects to long buzzes.
• Respect the user's settings and never make haptics the only way to receive information.
• Test on real hardware, because devices differ.

How developers implement haptic feedback

At a high level, the developer does not control the motor. They ask the operating system for an effect, and the system plays it if the hardware and the user's settings allow.

• iOS. The simple route is the system feedback generators, which come in three families: impact, selection and notification (success, warning and error). For custom patterns, such as in games, the Core Haptics framework lets you compose effects from short taps and continuous vibrations and control their intensity and sharpness.
• Android. The simple route is to ask a view to perform one of the platform's standard haptic constants, which respects the system setting and needs no special permission. For more control, the vibrator API plays predefined or custom effects, and lets you check what the device can actually do before you try.
• Cross-platform. React Native has a basic built-in vibration module, and libraries such as expo-haptics expose the proper platform feedback types. Flutter ships a HapticFeedback class with light, medium and heavy impacts and a selection click.
• Web. Browsers offer a Vibration API, which works in Chrome on Android and has not been supported in Safari on iPhone. Treat it as an extra on the web, never as something the interface relies on.
• Games. Engines such as Unity provide controller rumble and a basic phone vibration call. Finer control on phones usually needs a plugin or a little native code.

If haptics are central to the product, as they can be in a game or a fitness app, that is one of the arguments for native code. The wider trade-off is covered in native vs cross-platform apps, and the full range of options in types of apps.

My advice on structure: do not scatter haptic calls through the codebase. Define a small set of named events in one place, such as success, warning, error and selection, and map each to the right call per platform. That keeps the app consistent, gives you one switch to turn everything off, and makes it obvious when someone adds a seventh kind of buzz that nobody needs.

Then test it in your hand. Simulators and emulators cannot tell you how an effect feels, and a cheap Android phone will tell you things a flagship will not.

Accessibility and battery considerations

Accessibility

Haptics are a real accessibility aid. For someone who is blind or has low vision, a tap confirms an action they cannot see. For someone who is deaf or hard of hearing, it carries what a sound would have. That is a good reason to implement them properly.

They can also be a barrier. Some people find vibration uncomfortable or distracting, some have conditions that make it hard to perceive, and many tablets have no vibration hardware at all. Both platforms let the user reduce or turn off vibration, and the standard APIs honour that choice. Two rules follow: never carry information through haptics alone, and never override the user's setting.

Battery

The actuator only draws power while it is moving. A short tap from a linear actuator costs very little, and occasional feedback in an ordinary app is unlikely to be noticeable. Long or continuous vibration is a different matter, which is why a game with constant rumble will use more than a banking app. Apple's own support note for keyboard haptics mentions that the feature may affect battery life, which is a fair summary: each tap is small, but taps add up. Some power-saving modes also reduce or disable touch vibration, so do not assume an effect was felt.

When haptics hurt the experience

• Too many. If every tap, scroll and screen change buzzes, the signal is lost, and users turn the whole thing off, including the parts that helped.
• Out of sync. Feedback that lags the animation or sound makes the app feel slow or faulty.
• Wrong meaning. An error pattern on a successful action, or a heavy thud for a trivial one.
• Long buzzes. On a table, a vibrating phone is loud. In a meeting or at night, that is the opposite of discreet.
• During recording. Vibration can shake the camera and be picked up by the microphone. iOS suppresses haptics by default while an app is recording audio for that reason.
• As decoration. Haptics added to make an app feel "premium", with no action to confirm, read as a gimmick within a day.
• Untested on cheaper hardware. A pattern designed on a flagship may be harsh, or barely felt, elsewhere.

The test I use is simple: if you removed the effect, would the user lose information? If not, remove it.

A sensible starting set

For most apps I would start with four effects and stop there: a light tap for a successful primary action, a distinct pattern for errors, a tick for selection controls such as pickers and sliders, and a soft impact when a dragged item snaps into place. Add more only when testing shows a moment where users are unsure whether something registered.

Haptics are a small part of interaction design, but they are one of the places where the care taken over an app can literally be felt. It is the kind of detail we work through in product design and mobile app development projects.

Frequently asked questions

What is the haptic feedback setting on my phone?

It controls the small vibrations the phone makes when you touch it: typing, long presses, switches and system gestures. Turning it off stops those taps. On most phones, call and notification vibration is a separate setting.

What is haptic service?

In general it refers to the system component that takes vibration requests from apps and drives the phone's vibration hardware. The exact name and role vary by manufacturer and Android version. It is part of the system, so adjust vibration through the settings screen and leave the component itself alone.

Is haptic feedback the same as vibration?

Same hardware, different use. Vibration usually means a long buzz for calls and alerts. Haptic feedback means short, designed effects that respond to what you are doing on screen.

Does haptic feedback drain the battery?

A little. Each tap uses a small amount of energy, so occasional feedback is unlikely to be noticeable, while constant vibration in games or on every keystroke uses more. If battery life is tight, keyboard haptics are the first thing to switch off.

How is vibration feedback for phones and games different?

Phones have one small actuator, so effects are short taps and pulses. Game controllers have larger or multiple actuators, and some add resistance in the triggers, so they can produce stronger and more varied sensations over a longer time.