GlassKit vs Meta's official toolkit
An honest comparison of GlassKit and Meta's official Web Apps toolkit for building Meta Ray-Ban Display apps: what each one is, what each costs, and which to choose.
TL;DR: Meta's official toolkit is a free scaffold: it generates a bare vanilla Web App and it's the right call for prototypes. GlassKit is the production layer: a typed React system for the glasses plus the companion site, auth, payments, and backend a commercial product needs, for $99 one-time. Meta's toolkit gets you to "it runs on the glasses"; GlassKit gets you to "it's a business."
What Meta's official toolkit is
Meta ships an AI-assisted toolkit alongside its Web Apps
documentation
(wearables.developer.meta.com):
a plugin for Claude Code, Cursor, Codex, and GitHub Copilot. You
describe an app, and it scaffolds index.html, styles.css, and
app.js following the display glasses design constraints, with a
handful of skills (create-webapp, add-screen, add-button,
connect-api, add-sensors) and a few example apps.
It is genuinely good at what it does: getting a single, simple Web App on the glasses fast. It is free and official.
What it does not include: authentication, payments, a database, a companion site, transactional email, a typed component system, or any of the commercial scaffolding a real product needs. That's by design: it's a scaffold, not a boilerplate.
What GlassKit is
GlassKit is three products on one ladder:
- GlassKit UI (free, MIT):
the typed React library for the platform:
GlassViewport,useDpadfocus,useNavigator, sensor hooks. - GlassKit Studio (pay-as-you-go): generates working glasses apps from a prompt.
- GlassKit Stack ($99 Maker / $399 Agency, one-time): the production monorepo this page compares against Meta's scaffold: a Vite + React glasses app, a Next.js companion site (marketing, Clerk sign-up, billing, dashboard), and a shared Convex backend, with opt-in add-ons for payments, email, and AI, plus six forkable AI demos and an app slot that accepts an ejected Studio app.
Side by side
| Meta's toolkit | GlassKit Stack | |
|---|---|---|
| Price | Free | $99 / $399 one-time |
| What you get | A scaffolded vanilla Web App | A 3-workspace fullstack monorepo |
| Glasses app | index.html + styles.css + app.js | Typed Vite + React app with primitives + hooks |
| Auth | None | Clerk, wired, shared to the glasses |
| Payments | None | Checkout + customer portal, opt-in add-on |
| Backend | None | Convex, shared |
| None | Resend, opt-in add-on | |
| Companion site | None | Next.js marketing + dashboard |
| Templates | A few examples | 6 AI + device demos |
| TypeScript | No | Yes, strict, across all workspaces |
| Studio credits | n/a | 2,500 included |
| Best for | Prototypes, hobby apps | Commercial products you ship and sell |
Which should you choose?
Choose Meta's toolkit if
You're prototyping, learning the platform, or building something small and personal. It's free and it's official, so there's no reason to pay for a hobby project.
Choose GlassKit if
You're building a product. The moment you need users to sign in, pay you, receive an email, or have their data persist, you need auth, payments, email, and a backend. Wiring those yourself is the "two identical weeks" every project starts with. GlassKit ships them done, and ships the companion site to sell the thing.
They're not mutually exclusive in spirit: GlassKit is what Meta's scaffold would look like if it were built for commercial launch. And if you want the middle path, the free GlassKit UI library gives you the typed platform layer with no purchase at all.
Best framework for Meta Ray-Ban Display apps (2026)
The honest 2026 comparison of every way to build a Meta Ray-Ban Display app: vanilla Web Apps, Meta's AI toolkit, GlassKit UI, GlassKit Studio, and the GlassKit Stack.
GlassKit Stack vs building from scratch
What the $99 GlassKit Stack actually replaces: the auth, payments, backend, and companion-site wiring every commercial Meta Ray-Ban Display app needs before its own features.