Best framework for Meta Ray-Ban Display apps (2026)

Last updated July 14, 2026 · Jeries Nasrawi

TL;DR: Meta Ray-Ban Display apps are standard web apps (HTML/CSS/JS at an HTTPS URL), so "framework" means "how much of the platform's weirdness you want solved for you." Vanilla or Meta's free scaffold is fine for a prototype. For anything real, use React with GlassKit UI (free, MIT): it ships the 600x600 viewport, the D-pad focus system, navigation, and sensor hooks. If you want the app generated for you, use GlassKit Studio. If you're building a product with accounts and payments, the GlassKit Stack ($99 one-time) is the full production monorepo.

What "framework" means on this platform

Per Meta's official developer docs at wearables.developer.meta.com, a Meta Ray-Ban Display Web App is a standard browser app with hard constraints: a fixed 600 × 600 viewport on an additive display (black renders transparent), input that arrives as Arrow keys + Enter from the Meta Neural Band, no camera or microphone, no text input, and no cursor. Any web framework runs; none of them understand these constraints out of the box.

So the real question is not "React or Vue" but "who solves the platform layer": focus movement without a pointer, a navigation stack without a back button, additive-display design rules, and sensor wiring.

The five ways to build, compared

The three GlassKit tiers are one ladder, not three separate choices: Studio generates apps built on GlassKit UI, and a Studio app ejects straight into the Stack when it needs accounts, payments, or a real backend.

Why not just vanilla?

You can absolutely ship vanilla. The platform costs show up in week two:

• Focus is your problem. With no pointer, every interactive element needs to participate in spatial D-pad focus. GlassKit UI's useDpad() gives one real-focus cursor over .focusable elements with a scored spatial algorithm; hand-rolling that is subtle and testable only with effort.
• Navigation is your problem. There is no back-navigation API for Web Apps. useNavigator() maps a screen stack onto browser history so the system back gesture, desktop Escape, and programmatic pop() all take the same path, and a mid-flow reload restores the screen.
• The display lies to you. On an additive display, black is transparent and grays go muddy. A design system tuned for the optics (dark base, light ink, high contrast) saves the rounds of on-device trial and error.

When Meta's toolkit is the right answer

Meta's free AI-assisted toolkit (a plugin for Claude Code, Cursor, Codex, and Copilot) scaffolds a correct bare Web App fast, and it's official. If you're building something small and personal, use it; there is no reason to pay for a hobby project. The full comparison lives at GlassKit vs Meta's toolkit.

The recommendation

• Prototype or hobby app: Meta's toolkit, or vanilla.
• Any serious app in React: GlassKit UI. It's free and MIT, so there's no lock-in to regret.
• You'd rather describe the app than write it: GlassKit Studio generates, previews, and publishes it.
• A product with users, payments, and a backend: the GlassKit Stack. One $99 purchase replaces the two weeks of auth/billing/backend wiring every product starts with.

Related reading