Playing haptics

Playing haptics can engage people’s sense of touch and bring their familiarity with the physical world into your app or game.

The system can play haptics in addition to visual and auditory feedback to communicate things like the confirmation of an Apple Pay transaction or the arrival of a notification in iOS and watchOS. On a Mac that’s equipped with a Force Touch trackpad, apps can play haptics while people are dragging content or respond to different strengths of a force click to enable different levels of change in an onscreen element. In a tvOS or iPadOS app, game controllers can provide haptic feedback.

Depending on the platform, the system may provide haptic feedback for standard components by default. For example, components like switches, sliders, and pickers automatically play haptic feedback on supported iPhone models; on Apple Watch, the Taptic Engine generates haptics and watchOS combines an audible tone with some of them. In addition, the system may provide built-in haptic patterns you can use in your app or game or even let you design custom ones.

Best practices

Use system-provided haptic patterns according to their documented meanings. People recognize standard haptics because the system plays them consistently on interactions with standard controls. If the documented use case for a pattern doesn’t make sense in your app, use a generic pattern or create your own, where supported. For guidance, see Custom haptics.

Use haptics consistently. It’s important to build a clear, causal relationship between each haptic and the action that causes it so people learn to associate certain haptic patterns with certain experiences. If a haptic doesn’t reinforce a cause-and-effect relationship, it can be confusing and seem gratuitous. For example, if your app plays a specific haptic pattern when a game character fails to finish a mission, people associate that pattern with a negative outcome. If you use the same haptic pattern for a positive outcome like a level completion, people will be confused.

Use haptics in ways that complement other feedback in your app. When visual, auditory, and tactile feedback are in harmony — as they generally are in the physical world — the user experience is more coherent and can seem more natural. For example, match the intensity and sharpness of a haptic with the animation you use to accompany it. You can also synchronize sound with haptics; for developer guidance, see Delivering rich app experiences with haptics.

Avoid overusing haptics. Sometimes a haptic can feel just right when it happens occasionally, but become tiresome when it plays frequently. It’s important to do user testing that can help you discover a balance that most people appreciate. Often, the best haptic experience is one that people may not be conscious of, but miss when it’s turned off.

Make haptics optional. Let people turn off or mute haptics if they wish, and make sure people can still enjoy your app without them.

Be aware that playing haptics might impact other user experiences. By design, haptics produce enough physical force for people to feel the vibration. Ensure that haptic vibrations don’t disrupt user experiences involving the camera, gyroscope, or microphone.

Custom haptics

Games often use custom haptics to enhance gameplay. Although it’s less common, nongame apps might also use custom haptics to provide a richer, more delightful experience.

You can design custom haptic patterns that vary dynamically, based on user input or context. For example, the impact players feel when a game character jumps from a tree can be stronger than when the character jumps in place, and substantial experiences — like a collision or a hit — can feel very different from subtle experiences like the approach of footsteps or a looming danger.

There are two basic building blocks you can use to generate custom haptic patterns.

  • Transient events are brief and compact, often feeling like taps or impulses. The experience of tapping the Flashlight button on the Home Screen is an example of a transient event.
  • Continuous events feel like sustained vibrations, such as the experience of the lasers effect in a message.

Regardless of the type of haptic event you use to generate a custom haptic, you can also control its sharpness and intensity. You can think of sharpness as a way to abstract a haptic experience into the waveform that produces the corresponding physical sensations. Specifying sharpness lets you relay to the system your intent for the experience. For example, you might use sharpness values to convey an experience that’s soft, rounded, or organic, or one that’s crisp, precise, or mechanical. As the term implies, intensity means the strength of the haptic.

By combining transient and continuous events, varying sharpness and intensity, and including optional audio content, you can create a wide range of different haptic experiences. For developer guidance, see Core Haptics.

Platform considerations

iOS, iPadOS

Although iPad doesn’t play haptics, you can support game controller input in your iPadOS apps. For developer guidance, see Playing haptics on game controllers.

On supported iPhone models, you can add haptics to your experience in the following ways:


Notification haptics provide feedback about the outcome of a task or action, such as depositing a check or unlocking a vehicle.


Success. Indicates that a task or action has completed.


Warning. Indicates that a task or action has produced a warning of some kind.


Error. Indicates that an error has occurred.


Impact haptics provide a physical metaphor you can use to complement a visual experience. For example, people might feel a tap when a view snaps into place or a thud when two heavy objects collide.


Light. Indicates a collision between small or lightweight UI objects.


Medium. Indicates a collision between medium-sized or medium-weight UI objects.


Heavy. Indicates a collision between large or heavyweight UI objects.


Rigid. Indicates a collision between hard or inflexible UI objects.


Soft. Indicates a collision between soft or flexible UI objects.


Selection haptics provide feedback while the values of a UI element are changing.


Selection. Indicates that a UI element’s values are changing.


When a Magic Trackpad is available, your app can provide one of the three following haptic patterns in response to a drag operation or force click.

Haptic feedback pattern Description
Alignment Indicates the alignment of a dragged item. For example, this pattern could be used in a drawing app when the people drag a shape into alignment with another shape. Other scenarios where this type of feedback could be used might include scaling an object to fit within specific dimensions, positioning an object at a preferred location, or reaching the beginning/end or minimum/maximum of something like a scrubber in a video app.
Level change Indicates movement between discrete levels of pressure. For example, as people press a fast-forward button on a video player, playback could increase or decrease and haptic feedback could be provided as different levels of pressure are reached.
Generic Intended for providing general feedback when the other patterns don’t apply.

For developer guidance, see NSHapticFeedbackPerformer.


On Apple TV, game controllers can play haptics. For developer guidance, see Playing haptics on game controllers.


Apple Watch Series 4 and later provides haptic feedback for the Digital Crown, which gives people a more tactile experience as they scroll through content. By default, the system provides linear haptic detents that people can feel as they rotate the Digital Crown. Some system controls, like table views, provide detents as new items scroll onto the screen. For developer guidance, see WKHapticType (WatchKit).

watchOS defines the following set of haptics, each of which conveys a specific meaning to people.

  • Notification. Tells the user that something significant or out of the ordinary has happened and requires the user’s attention. The system plays this same haptic when a local or remote notification arrives.

  • Up. Tells the user that an important value increased above a significant threshold.

  • Down. Tells the user that an important value decreased below a significant threshold.

  • Success. Tells the user that an action completed successfully.

  • Failure. Tells the user that an action failed.

  • Retry. Tells the user that an action failed but may be retried.

  • Start. Tells the user that an activity started. Use this haptic when starting a timer or any other activity that can be explicitly started and stopped. This haptic is usually followed by the Stop haptic.

  • Stop. Tells the user that an activity stopped. Use this haptic when stopping a timer or other activity that was previously started.

  • Click. Provides the sensation of a dial clicking or progress at predefined increments or intervals. Use this haptic sparingly. Overuse of the click haptic diminishes its utility and can even be confusing when clicks overlap each other.



Developer documentation


Supported platforms