01 The plan

Roadmap

GID is built foundations-first. The phases below are ordered by what must be true before the next step, not by a calendar. We would rather be right than early on the decisions that cannot be undone.

02 Phases

  1. 00

    Concept

    Complete

    The thesis, scope, and HID lineage established. Debuted publicly at AWE XR 2026.

  2. 01

    Foundations

    In progress

    The hard, irreversible decisions come first: how GID frames input, versions it safely, extends without breaking, and gets it to the right app. Their shape is largely settled; the remaining work is the encoding, before anything freezes as normative.

  3. 02

    Draft specification

    Up next

    Normative text for the core: descriptors, the envelope, addressing, and the mandatory-to-implement baseline, with a BLE GATT binding.

  4. 03

    Reference controller

    Planned

    PeKe Labs ships the first GID controller and companion relay as a working proof that the model holds in hardware - not a slide, a device.

  5. 04

    GID 1.0

    Planned

    A stable core, a conformance definition, and an open process for extensions. Availability announced here when the foundations are locked.

03 Strategy

Prove it in hardware

A standard nobody builds is a document. GID's strategy is to ship the first device itself.

A hand holding the reference controller between two fingers - a small dark device with a circular touch pad.
Pocket-sized - the controller in hand.
Close-up of the reference controller docked to the back of a phone, beside the camera array.
Docked to the back of a phone.

PeKe Labs is building a reference glasses controller - gesture input, buttons, and positional control - paired with a companion relay app that bridges the controller to the app on your glasses. It is the first real implementation of GID, and its job is to prove the model holds where it matters: on actual hardware, over the BLE GATT channel that glasses use today, against real glasses in hand.

The reference controller is how GID earns the right to be a standard rather than a proposal. If the model cannot drive a real device cleanly, the specification is wrong and we would rather find out on our own hardware first.

Follow along

The work happens in the open. Watch the decisions get made and weigh in.

Join the Discord Watch on GitHub