TS

TypeScript SDK

@gestura/ring-sdk · in development

The TypeScript SDK is in active development: an ergonomic, W3C UI-Events-style API for the Haptic Harmony ring and its simulator. The wire codec is not re-implemented in TypeScript — it is the Rust gestura-protocol crate compiled to WebAssembly, so the SDK shares the exact contract the firmware uses.

View on GitHub

Installation

Not yet published to npm — until the first release, build from source in the public repository:

git clone https://github.com/gestura-ai/gestura-app
cd gestura-app/sdk/typescript
npm install
npm run build   # builds the WASM core, then compiles TS
npm test        # vitest, against MockTransport — no hardware needed

Current integration shape

  1. Model gestures and haptic signals as typed application events.
  2. Expose only the MCP tools and resources that should be visible outside your app boundary.
  3. Keep orchestration, device control, and policy inside your main runtime while TypeScript handles browser-facing integration points.

What TypeScript is for right now

  • • Browser-side gesture capture and normalization.
  • • Typed event payloads for MCP-facing integrations.
  • • Lightweight protocol bridges that expose curated capabilities to external agents.
  • • UI-adjacent tooling where TypeScript is the integration shell, not the entire application core.

Features

  • ✓
    Typed gesture event modeling

    Define stable event shapes before they cross an MCP boundary.

  • ✓
    Protocol-facing browser integration

    Good fit for web surfaces that need to publish carefully scoped gesture capabilities.

  • ✓
    Async integration flows

    Use async boundaries for transport, approvals, and capability exposure.

  • ✓
    Gesture-first integration scope

    Positioned around gesture MCP workflows, not a full cross-product SDK story yet.

  • ✓
    Pair with the MCP docs

    Follow the protocol boundary guidance in the MCP integration section for architecture decisions.

API Reference

MCP integration guidance

Start with the MCP integration guidance for boundary design, capability exposure, and protocol shape.

View MCP integration docs →

Gesture library guidance

Use gesture library docs to define typed events and haptic semantics before exposing them to external agents.

View gesture library docs →

More Resources

Documentation

Complete guides and tutorials

Examples

Sample projects and code