Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
lochie avatar

Web Haptics

  • 719 installs
  • 2.7k repo stars
  • Updated March 9, 2026
  • lochie/web-haptics

web-haptics is a frontend skill that adds tactile haptic feedback to mobile web interfaces for developers who want buttons, forms, toggles, and pickers to feel responsive on touch devices.

About

web-haptics is a frontend skill at version 1.0 from lochie/web-haptics for integrating the MIT-licensed web-haptics npm package into mobile-facing web apps. Install with npm i web-haptics; the library wraps the Web Vibration API with zero dependencies and silently no-ops on unsupported desktop browsers without requiring feature-detection boilerplate. The trigger() API accepts predefined haptic type strings for buttons, toggles, forms, and pickers. Developers reach for web-haptics when progressive web or responsive sites need native-feeling tap feedback on iOS and Android browsers where subtle vibration confirms successful interactions.

  • Adds haptic feedback using the Web Vibration API with zero dependencies
  • Silently no-ops on desktop and unsupported platforms
  • Supports 9 distinct trigger types across notification, impact, and selection categories
  • One-line React hook integration with useWebHaptics()
  • MIT licensed, no error handling or feature detection required

Web Haptics by the numbers

  • 719 all-time installs (skills.sh)
  • +16 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #476 of 2,245 Frontend Development skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/lochie/web-haptics --skill web-haptics

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs719
repo stars2.7k
Security audit3 / 3 scanners passed
Last updatedMarch 9, 2026
Repositorylochie/web-haptics

How do you add haptic feedback to mobile web apps?

Add realistic tactile feedback to mobile-facing web interfaces so users feel confident when tapping buttons, submitting forms, or changing settings.

Who is it for?

Frontend developers building mobile-first or PWA interfaces that need tactile confirmation on taps and toggles.

Skip if: Desktop-only applications where vibration hardware is unavailable and haptic feedback provides no user benefit.

When should I use this skill?

A mobile-facing web UI needs tactile feedback on buttons, toggles, forms, or pickers during implementation.

What you get

Integrated web-haptics trigger calls on interactive UI elements with Web Vibration API feedback on supported devices.

  • Haptic-enabled UI components
  • trigger() integration on interactive elements

By the numbers

  • web-haptics npm package ships with zero dependencies
  • Skill metadata version 1.0

Files

SKILL.mdMarkdownGitHub ↗

Install web-haptics (npm i web-haptics) and add haptic feedback to the app following these rules:

Package: web-haptics

Repository: https://github.com/lochie/web-haptics | License: MIT | Zero dependencies Uses the Web Vibration API. Silently no-ops on unsupported platforms (desktop). No error handling or feature detection needed.

Trigger Types

trigger() accepts one of these strings (empty value defaults to a sensible "medium" impact):

Notification (task outcomes):

  • "success" -- form saved, payment confirmed, upload complete
  • "warning" -- destructive action ahead, approaching limit, irreversible step
  • "error" -- validation failure, network error, permission denied

Impact (physical collisions):

  • "light" -- small toggle, subtle tap, minor interaction
  • "medium" -- button press, card snap-to-position, drop into place
  • "heavy" -- major state change, heavy element landed, force press

Selection (discrete stepping):

  • "selection" -- picker scroll, stepper increment, slider detent, segment switch

Framework Imports

React:

import { useWebHaptics } from "web-haptics/react";

const haptic = useWebHaptics();

<button onClick={() => haptic.trigger()}>Tap me</button>;

Vue:

<script setup>
import { useWebHaptics } from "web-haptics/vue";
const haptic = useWebHaptics();
</script>

<template>
  <button @click="haptic.trigger()">Tap me</button>
</template>

Svelte:

<script>
  import { createWebHaptics } from "web-haptics/svelte";
  import { onDestroy } from "svelte";
  const haptic = createWebHaptics();
  onDestroy(() => haptic.destroy());
</script>

<button on:click={() => haptic.trigger()}>Tap me</button>

Vanilla JS:

import { WebHaptics } from "web-haptics";

const haptics = new WebHaptics();
haptics.trigger(); // medium impact
haptics.trigger("success");

Next.js: add "use client" to any component using useWebHaptics(). Nuxt/SvelteKit: works directly, library handles SSR.

Trigger Presets & defaultPatterns

All named string presets have a corresponding object in defaultPatterns. Use when you need to pass a preset as a value rather than a string literal:

import { WebHaptics, defaultPatterns } from 'web-haptics'

const haptics = new WebHaptics()
haptics.trigger(defaultPatterns.light)

Extra presets not listed above: "soft", "rigid", "nudge", "buzz". See defaultPatterns for all available values.

Apple HIG Design Rules -- FOLLOW THESE

1. Haptics supplement, never replace. Always pair with visual feedback. UI must work fully without haptics. 2. Build causal relationships. The haptic must feel like a direct physical consequence of the user action. 3. Match intensity to significance. Light interactions = light/selection. Standard = medium/success. Major = heavy/error/warning. 4. Do not overuse. If every tap vibrates, nothing feels special. Reserve for meaningful moments only. 5. Synchronize perfectly. Fire haptic at the exact instant the visual change occurs. 6. Respect conventions. success=positive, error=negative, warning=cautionary, selection=discrete ticks only. 7. For async ops, trigger when the RESULT arrives, synced with the visual state change:

   try {
     await submit();
     haptic.trigger("success");
   } catch {
     haptic.trigger("error");
   }

Interaction to Type Quick Reference

Primary button tap = "medium" | Secondary button = "light" Form success = "success" | Validation error = "error" | Network error = "error" Toggle switch = "light" | Delete before confirm = "warning" Picker/wheel = "selection" | Slider detents = "selection" | Tab switch = "selection" Drag-drop snap = "medium" | Long press = "heavy" | Modal appear = "medium" Pull-to-refresh threshold = "light" | Swipe dismiss threshold = "light" Payment confirmed = "success"

Anti-Patterns -- AVOID

  • Haptic on every tap (fatigue)
  • "error" for non-errors (breaks conventions)
  • Haptic without visual feedback (some devices cannot vibrate)
  • Haptic on page load or passive scroll (invasive)
  • "heavy" for minor interactions (jarring)
  • Long continuous vibrations (web haptics = brief transient pulses)

Before implementing, confirm with the user:

  • Which interactive elements to target
  • Whether to add at shared component level or individual call sites

Related skills

FAQ

Does web-haptics work on desktop browsers?

The web-haptics library silently no-ops on unsupported platforms such as desktop browsers. The skill does not require explicit feature detection or error handling for missing vibration support.

How do you install web-haptics in a project?

The web-haptics skill installs the package with npm i web-haptics, then wires trigger() calls on buttons, toggles, forms, and pickers. The library is MIT-licensed with zero dependencies at version 1.0.

Is Web Haptics safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Frontend Developmentfrontendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.