Skip to main content
Your app runs on a phone in someone’s hand, and the hand is a display too. haptics() plays one vibration through the phone’s engine — the wheel stops, the pick lands, the win pays, and the moment registers physically as well as on screen.

​
The types

An omitted or unknown type plays the host default, a heavy impact — a value from a newer SDK degrades on an older host rather than erroring.

​
It never rejects

Haptics is decoration, so unlike every other capability this call never rejects: in a plain browser, under a Bankroll host too old to carry it, or on any bridge failure, it resolves having done nothing. Call it freely at the moments that deserve weight, and gate nothing on it. It is also fire-and-forget on the host side — the call resolves as soon as the host accepts it, not when the vibration ends, so it never holds your frame or your game loop.

​
Nothing to declare

Haptics moves no money and reads no data, so it rides the connection your app already has: no manifest claim, no consent line, and no re-consent for users who connected before it existed. Any connected app may call it. Requires a Bankroll host at client version 4 or later. The SDK feature-detects the method, so there is no version number for you to check.