Platform wishlist

APIs the Meta Ray-Ban Display doesn't expose to web apps yet — with GlassKit components already built and waiting for each one. The UI ships today; the day Meta exposes the API, it plugs in.

Web apps on the Display get four arrow keys, Enter, and the system back gesture — and that's it. No camera, no microphone, no gaze. We built the components anyway: the UI, the focus behavior, the docs, and the exact prop where each API would land are all shipped. This page is the standing request.

If you're building for the Display and want these too, say so — on the Meta Wearables developer community, in the toolkit repo, or wherever Meta devrel is listening. Every request below links the component that would light up the day the API ships.

🎤 Microphone / system dictation

The single highest-leverage API. There is no free-form text input on the glasses today — no keyboard, no mic, no dictation — so every text flow is a picker UI or a phone relay.

Ready and waiting	Where it plugs in
TextField	`onActivate` opens the capture flow — today yours, then the system's
ComposeFlow	the shipped interim: a back-gesture-aware picker — dictation swaps in at the same seam
`--template relay` (create-glasskit)	free-form interim: type on the phone, a 6-char code pairs it to the lens
Dictation	the live transcript view, currently app-driven
LiveCaptions	real-time captioning needs mic + transcription

📷 Camera access

The Display has a 12 MP camera; web apps can't touch it (no getUserMedia, no capture API).

Ready and waiting	Where it plugs in
Viewfinder	the full capture chrome — brackets, zoom badge, REC — wired to app state today

👁 Gaze / head-pose targeting

Head orientation reaches web apps (useDeviceOrientation), but nothing says what the wearer is looking at on screen.

Ready and waiting	Where it plugs in
Reticle	`active` — today derived from your own projection math, then from the platform

🔊 Documented audio playback

Whether <audio> / Web Audio works in the Display webview is undocumented. Even a one-line answer unlocks a category of apps.

Ready and waiting	Where it plugs in
NowPlaying	today a status display for playback your app tracks elsewhere

🤲 Neural Band haptics

The wristband buzzes for system gestures; apps can't ask it to. Even a single "tap" cue would make pinch interactions feel mechanical-real.

Ready and waiting	Where it plugs in
`useFeedback()` (SDK)	call `buzz("tap")` at interaction points today — the `glasskitfeedback` event is the bridge

🖐 Neural Band gesture events

Swipes and pinches arrive as arrow/Enter keydowns — flattened. A richer CustomEvent channel (double-pinch, rotate, wrist-flick) is the seam our useNeuralBand hook already listens on.

Ready and waiting	Where it plugs in
Deck	uncontrolled paging advances on the `neuralband` swipe event, the moment the OS dispatches it

Everything above degrades gracefully today — the honesty notes on each component's page say exactly what you own until the platform catches up. When an API ships, the components update and this page shrinks. We'd love for this page to be empty.