Vibration and haptics
Lets the app vibrate the phone.
In one line
Can make the phone buzz, with no prompt and no personal data
Lets the app vibrate the phone.
A harmless-looking motor trigger; no sensitive data. Android requires a manifest permission; iOS needs none.
What it can and can't do
What the user does: Nothing. It happens when the app gives feedback, like a tap or an alert
It can
- Buzz the phone
- Play tap style feedback through the Taptic engine (iPhone)
- Use a haptic pattern on Android 8 and later
It cannot
- See any of your data
- Work on devices without the vibration motor
- Ask you first; Android grants it at install and iPhone needs nothing
How it differs between platforms: Android needs a manifest permission, granted at install; iPhone needs none.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Android 1.0 (API 1) | iOS 10 |
| Permission or entitlement | VIBRATE | none |
| Protection level | normal | none |
| How access is granted | install | none |
| What the user sees | None (granted at install) | None |
| How long it lasts | Not revocable | n/a |
| How to take it back | n/a | n/a |
| Store policy | Play: none | none |
| API | Vibrator, VibrationEffect (API 26) | UIImpactFeedbackGenerator, Core Haptics |
| Notes | Not required for haptic feedback via View.performHapticFeedback. | Taptic engine; hardware dependent. |
Data you get
What comes back: Vibration trigger
Shape: event
How often: on demand
No individual data fields. The signal is the access itself.
Technical limits
- User controls system vibration settings
- Background vibration is limited to notifications and foreground services
- Android 13 can silence vibration when media haptics are off
The story
What it is
Lets the app make the phone buzz.
For you
Your phone buzzes when a message comes in, a button clicks or a game explosion goes off. You rarely see a prompt, since it reads nothing about you.
For makers
Touch feedback makes apps feel solid and guides eyes away from the screen. It is used in games, maps and alerts. It carries no personal data, but it can annoy people and drain the battery.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A racing game rumbles when you hit a wall and a shooter thumps with each shot. | Call of Duty Mobile |
| maps | A map buzzes in a pattern for left and right turns. | Apple Maps |
| messaging | A chat app taps you for a new message and a heart reaction. | |
| music | A music app syncs buzzes to a drum beat. | None named |
| accessibility | A blind user feels different patterns for each type of alert. | None named |
| fitness | A running app buzzes at each mile. | None named |
| payments | A payment confirmation gives a gentle click so you know it went through. | None named |
Risks
- Annoying buzzes
- Battery use
- Covers for hidden alerts
Android and iPhone in short
- Android: Android needs a manifest permission for the vibrate call, but not for haptic feedback on views.
- iPhone: iPhone uses the taptic engine and the result depends on the hardware.
What the platform says
- Apple: Core Haptics. Add custom touch feedback with the phone's taptic engine.
- Google: Haptics on Android. Design touch feedback that feels natural on Android.
Good uses and abuse
Legitimate uses
- Feedback
Known abuse
- Annoyance
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 1 | Rough identifying entropy, when known |
History
- 2017-08, Android 8.0 (API 26): VibrationEffect introduced
- 2019-09, iPhone iOS 13: Core Haptics custom patterns
- 2021-10, Android 12 (API 31): Haptic composition primitives and haptic coupled audio
Related capabilities
Same idea on the web
- Vibrate the device. Can buzz the phone in short pulses, after you have tapped the page
- Vibration. Can buzz the phone in a pattern, after you have tapped on the page
Sources
How well checked: Based on official documentation.