Farglance for developers

Build for the Display.
We'll carry it.

A Farglance app is a plain web page. No framework, no build step, no SDK to learn. If you can write HTML, you can ship something to a pair of glasses tonight.

Submit an app

There is no fee. No listing charge, no yearly membership, no revenue cut on anything you charge for. If that ever changes, it changes for new apps only and we'll say so here first.

What you're building for

Be honest with yourself about the hardware before you design anything. It is small, it is monocular, and it has six buttons.

600 × 600, fixedOne square, right eye, about 20° of your view. No scrolling, no resizing. Design screens, not pages.

Black is transparentThe waveguide is additive. #000 disappears completely — that's the feature. Anything you want to look solid needs to be around #0a0a0f–#1C1E21, and pure white text reads best.

Six inputs. That's all.Four arrow keys and Enter, delivered as plain keydown events from the Neural Band. Plus a back gesture the system keeps for itself.

Always onlineHTTPS only, no offline guarantees, nothing runs in the background. If the network drops, your app should say something useful immediately.

What actually works

Verified against Meta's own developer documentation. Check back — the platform is in developer preview and this list moves.

Capabilities for code running on the glasses.
Capability	Status
Arrow keys + Enter	Yes — the Band's swipes and pinches arrive as standard `keydown` events
Canvas 2D and WebGL	Yes — aim for 60fps and keep an eye on the 128 MB memory budget
fetch / REST / WebSocket	Yes — over HTTPS and `wss://`
Head orientation and motion	Yes — `DeviceOrientationEvent`. Read it; don't steer with it. It's the head, not the wrist
Location	Yes — `navigator.geolocation`, sourced from the paired phone. Use long timeouts
localStorage / sessionStorage	Yes — 5 MB each
Microphone	No — not a permission you're failing to request. There's no path to it from the glasses. Voice has to come from a phone
Camera	No — same story
System text input	No — build an on-screen keyboard the arrows can drive, or design so nobody has to type
Notifications	No — nothing can wake the glasses on your behalf
Owning the back gesture	No — a middle-finger pinch opens the system's own menu above your page. Give every screen its own visible Back
Offline / service workers	Don't rely on it — officially unsupported. Preload into `localStorage` instead

The whole starter

This is a complete, working Farglance app. Serve it over HTTPS and you're done.

<!DOCTYPE html>
<meta charset="utf-8">
<meta name="viewport" content="width=600, height=600, initial-scale=1, user-scalable=no">
<meta name="mrbd-web-app-capable" content="yes">
<title>Hello</title>
<style>
  body { margin:0; width:600px; height:600px; overflow:hidden;
         background:#000; color:#fff; display:grid; place-items:center;
         font:600 28px/1.3 -apple-system, sans-serif; }
  button { font:700 20px/1 inherit; color:#fff; background:#111A2B;
           border:1px solid #24344f; border-radius:16px; padding:16px 26px; }
  button.on { outline:3px solid #4D9EFF; outline-offset:3px; }
</style>

<div><button class="on">Left</button> <button>Right</button></div>

<script>
  // Six inputs, and this is all of them.
  var btns = [].slice.call(document.querySelectorAll('button')), i = 0;
  addEventListener('keydown', function (e) {
    if (e.key === 'ArrowRight') i = Math.min(i + 1, btns.length - 1);
    else if (e.key === 'ArrowLeft') i = Math.max(i - 1, 0);
    else if (e.key === 'Enter') { btns[i].textContent = 'Pressed'; return; }
    else return;
    btns.forEach(function (b, n) { b.classList.toggle('on', n === i); });
    e.preventDefault();
  });
</script>

House rules

Every screen reachable by arrows alone. If a control can't be reached with four arrows and Enter, it doesn't exist on this device.
Body text at 16px or bigger, tap targets generous. This is read at arm's length through a small window, often while walking.
Survive a cold start. The system can restart your page at any moment. Keep state in localStorage or on your own server.
Your own art. No third-party logos, wordmarks or mascots. No ads, no third-party analytics, and never personal data in a URL.
Light on the glasses. Under half a megabyte of JavaScript, few requests, no per-frame blur. The battery is small and it is shared with everything else.

How submission works

No queue theatre. A person reads it, and you hear back either way.

Send us an HTTPS URL and a 512×512 PNG icon. You keep hosting it, so you ship updates whenever you like without asking anyone.
We check it loads, behaves on arrows alone, and doesn't do anything nasty. Then it goes on the shelf with a one-tap install link of its own.
Want out? Say the word and it's delisted. We don't hold your app hostage and we never change your code.

Submit your app

Free. A person reviews it and you hear back either way. You keep hosting it, so you ship updates whenever you like.

See what's on the shelf →