The number of haptic patterns is capped by discriminability

What it is

Only a handful of watch vibrations can be named without training. The system already spends most of that handful: a notification arrived, the crown ticked a detent, payment succeeded, the timer ended. If an app then invents different rhythms for mail, calendar, and workout, people walking cannot tell them apart. They feel “it buzzed again.” This entry is about that already crowded discriminable budget on the wrist, not about how many codes a tactile channel can theoretically pack in a lab.

Why it happens

Encoding dimensions at the wrist are few: mainly pulse count and spacing; intensity steps shrink further under motion noise. Identification is absolute—there is no pair of patterns side by side to compare, only this buzz against a memory of “the last kind.” System events arrive first and fire far more often than any app’s custom pulse. People attach stable feel-labels to high-frequency events; leftover slots are tiny. A new pattern is not competing with silence. It is competing with those occupied slots; similar short pulses collapse into one class. A watch is almost always felt during a secondary task, and the identification window is one pulse long—there is no “play it again so I can hear it.” Discriminable count is therefore not the channel’s bandwidth ceiling. It is what remains after system events have taken their share.

Studying it

Use absolute identification: train a set of wrist patterns while seated, then play them while walking and ask “which kind was that.” The stimulus set must include the system classes already in use (notification, confirm, crown detent, alarm) before adding app customs. Plot the confusion matrix to see what a new pattern collides with.

Independent variables: number of patterns, structural similarity to system patterns, walking versus sitting, gap between plays. Dependent variables: identification accuracy, pairwise confusions, drop from sitting to walking.

Do not stop at pairwise discrimination—that overestimates how many kinds work in the field. Well-trained participants also inflate the count; report training time and include a zero-training condition. Present on a worn watch; a handheld mock-up is not a substitute.

Where it stops holding

Specialist users (people who rely on haptics accessibly, athletes who live by split buzzes) can name a few more after long training; their vocabulary is not the default. Lengthening patterns can buy distinction but breaks the short window of eyes-free confirm—trading duration for slots. Turning system haptics off to free slots for apps also kills notification and crown detents; the trade is usually a loss. Quiet rooms may tolerate more patterns; motion noise tolerates fewer. Those thresholds do not transfer.

Applying it

• Inventory patterns the system already owns. By default an app takes only one more: something happened. Put the type on the lit screen, not in the buzz.
• If a split is mandatory, use two levels only—“ordinary” versus “handle now”—separated by pulse count, not by a fine intensity step.
• Do not invent a unique rhythm per notification channel; channel differences belong in the text of one raise.
• Verify by listing every pattern that will ship (system included) and running absolute identification while walking. If accuracy falls toward chance, or app patterns are stably heard as system notifications, delete patterns rather than tweaking gaps.

Related

• Within the group: K4.04.1 Skin contact at the wrist makes haptics reliable · K4.04.2 Haptics can confirm without looking at the screen
• Adjacent: D3.10 Discriminable Size of a Haptic Vocabulary · D3.03 Semantic Encoding of Haptic Patterns · D3.08 Haptic Overload and Numbing
• Search terms: tactons · absolute identification · haptic vocabulary