Haptic Feedback: Rumble, DualSense, and Touch Vibration

Haptic feedback is the third channel in the three-channel rule, after visual and audio. It delivers physical sensation directly - vibration through a controller, resistance in a trigger, tap feedback through a phone screen. At its best, it bridges the gap between the digital event on screen and the player's body, making impacts feel like something that happened to them, not just something they watched. At its worst, it's a constant buzz that players turn off in the first five minutes.

The principles that govern good haptic design mirror good visual and audio feedback design: be reactive rather than constant, scale intensity to event significance, and build a consistent vocabulary players can learn. The difference is that haptics are the most intimate of the three channels - they literally touch the player - and abuse of that intimacy is more irritating than visual or audio excess.

Controller Rumble

Standard controllers have two rumble motors: a low-frequency motor in the left grip and a high-frequency motor in the right grip. Using both independently allows nuanced haptic design that matches the physical properties of the in-game event.

Heavy impacts - explosions, heavy stomps, large-caliber weapon fire - should drive the left (low-frequency) motor at high intensity. The low-frequency rumble reads as weight and force in the gut, not just vibration in the fingers. Rapid, light events - footsteps on hard surfaces, sparks, light weapon fire - suit the right (high-frequency) motor at lower intensity. The distinction mirrors how we perceive these events acoustically: low frequencies carry weight, high frequencies carry texture.

Environmental haptics - sustained low rumble while driving over rough terrain, a slight buzz near a high-voltage hazard, rhythmic pulses matching footsteps during a run - add ambience that makes the world feel physically real. These should be subtle: background vibration at 10 to 20% intensity. Their purpose is to contrast with impact events, making the sharp spike of a hit feel more significant against a quieter baseline.

Low-health heartbeat haptics - alternating pulses at a slow heartbeat rhythm - are one of the most effective tension-building tools available. Combined with a low-health vignette and tense audio, the physical pulse in the controller creates a visceral urgency that no amount of visual feedback alone produces. Keep the pulse slow and ominous: 60 to 70 BPM, with a sharp attack and slower decay per beat.

DualSense Adaptive Triggers

PlayStation 5's DualSense controller adds a fourth feedback channel: trigger resistance. The L2 and R2 triggers can apply dynamic physical resistance - the button fights back against the player's finger. This is not rumble. It is mechanical resistance that communicates material properties through the player's muscles rather than their fingertips.

A wet or jammed gun trigger feels stiff and requires deliberate force. A bow being drawn increases resistance as the draw weight builds and then releases suddenly at full draw. A car tyre losing traction changes the trigger feel as grip gives way. These are not simulations of real forces - they're exaggerated, designed signals that communicate mechanical state directly to the player's body. The player feels information they could not read from the screen alone.

DualSense haptics require targeting PS5 specifically and using Sony's platform APIs or an engine wrapper (Unity and Unreal both have native DualSense support). Consider the feature as an enhancement layer rather than a required feedback channel - your game must communicate clearly on controllers without adaptive triggers before you add the DualSense layer on top. Xbox and PC controllers do not have equivalent hardware.

Mobile Haptics

Mobile devices use the Taptic Engine (iOS) or vibration motor (Android) to deliver haptic feedback through the device body. Mobile haptics are less nuanced than controller rumble - there is no left/right motor distinction, and the feedback is felt in the whole hand rather than specific grip points. The design philosophy shifts accordingly: use haptics for confirmation and rhythm, not for spatial or intensity-graded feedback.

Good mobile haptic patterns: a brief, sharp tap on button press (the most basic confirmation pattern, used everywhere in native iOS and Android UI for good reason), subtle tap feedback during fast swipe gestures to give physical texture to touch interactions, a pulse on damage taken or failed action, and a strong multi-tap pattern for significant events like level completion or achievement unlock.

iOS provides the UIFeedbackGenerator API with distinct patterns for impact, selection, and notification events. Use the semantic API rather than raw vibration values - Apple tuned these patterns for the specific Taptic Engine hardware and they translate better across device generations. Android's VibrationEffect API provides similar semantic patterns on modern devices but with more hardware variation across manufacturers.

Designing a Haptic Vocabulary

Like colour and sound, haptics need a consistent vocabulary to be readable. Define your haptic events and their patterns before implementation, then stick to them. A sharp short pulse always means button confirmed. A long strong rumble always means player damage. A rhythmic pulse always means low health. Inconsistency - the same physical pattern for unrelated events - erodes the player's ability to read haptic information and reduces it to noise.

The intensity hierarchy matters the same way it does for visual and audio feedback. If every action produces maximum rumble, the system communicates nothing. Define which events deserve what intensity tier. Small inputs (button press, menu selection) get minimal haptics. Medium events (hit landed, ability activated) get moderate haptics. Major events (boss hit, player damage, level complete) get full-intensity haptics. The contrast between tiers is what makes the significant events feel significant.

Accessibility and Opt-Out

Haptic feedback must always be optional. Players with motor sensitivities, those using controllers with dead vibration motors, and players who simply find vibration distracting should be able to disable haptics entirely without losing game-critical information. This is non-negotiable: haptics are an enhancement layer, never the primary feedback channel for anything the player needs to respond to.

Provide separate intensity controls for rumble and trigger resistance if you implement both. Some players want the tactile feedback of trigger resistance but find constant rumble distracting. Others love rumble but find adaptive triggers break their muscle memory for trigger inputs. The settings cost one afternoon to implement and eliminate a common source of negative reviews from players who would otherwise enjoy the game.