GID Gestural Interface Device
In active design

Gestural Interface Device

A universal language for wearable controllers.

When a wearable controller sends input today, the phone operating system grabs it first and treats it like a keyboard or mouse - so it goes to whichever app is in front, and developers can never use the raw signals to build anything of their own. So every company invents its own private Bluetooth channel from scratch. GID is one shared language that lets any wearable controller send its input straight to the app meant to receive it.

Why GID exists How it works GitHub

Introduced at AWE XR 2026. A sister standard to HID, stewarded by PeKe Labs.

Two GID reference controllers - small dark devices, each with a circular touch pad - against black.

01 The problem

Apps never get the input

HID made keyboards and mice self-describing and portable. But HID input goes through the operating system, which treats every device like a keyboard or mouse and hands it to whichever app is in front. A developer can't reach in and use a controller's raw signals to build something of their own.

So every company building a wearable controller invents its own private Bluetooth channel from scratch - none of them shared or reusable. GID standardizes the one layer they all keep rebuilding: a single language that lets any controller send its input straight to the app meant to receive it.

HID the system takes it Input device Phone OS App in front input ends here A glasses app no route GID sends it to the right app GID device Phone relay BLE GATT addr GLASSES · APPS App A addressed App B App C
The gap GID closes. The system grabs HID input and hands it to whichever app is in front. A GID event carries an address, so it reaches the one app meant to get it - even among several on a pair of glasses.

02 The idea

Three load-bearing ideas

01

Self-describing

A GID device announces what it is and what it emits. The host interprets the descriptor - no per-device driver. The HID idea, carried forward.

02

Goes to the right app

Every signal says which app it is for, so it reaches that app instead of whatever the system hands it to. This is the thing HID cannot do.

03

Forward-compatible

A versioned envelope, a must-ignore rule for unknown fields, and an extension mechanism. New input types arrive without breaking shipped devices.

03 Where it stands

Designed in the open, foundations first

GID is in active design. The irreversible decisions - how it frames, versions, extends, and addresses input - are largely settled in shape; the remaining work is the encoding, before any of it is frozen. The specifics on this site are intentionally high-level by design.

  1. 00 Concept done
  2. 01 Foundations active
  3. 02 Draft specification next
  4. 03 Reference controller planned
  5. 04 GID 1.0 planned

See the full roadmap and launch plan →

04 Get involved

Help shape the standard

GID is meant to be community-shaped, with explicit provenance. Read the thinking, argue the decisions, and build the first devices with us.

Join the Discord Read on GitHub