Snap Spectacles

Openness verdict. Very open at both build and ship time. Snap ships a free public SDK (Lens Studio 5) plus a second, independent web path (WebXR Browser Lens, no Lens Studio), standalone on-glasses Lenses, and public Lens Explorer distribution open to any developer in the program. The publish gate is narrow: only Experimental APIs (and unsupported permission combinations) cannot ship to a wide audience — camera/mic/location combined with internet access IS publicly publishable via Snap's Transparent Permission system, including bring-your-own-AI Lenses through the Remote Service Gateway. The real access wall is hardware: the paid, US-only $99/month developer program (or, from fall 2026, a purchased pair of Specs).

Covered here: Spectacles (5th generation, 2024) · Specs (2026).
Not covered here: Spectacles v1 / v2 / Spectacles 3 (2016–2019) · Spectacles (4th gen, 2021).

Overview

Snap Inc.'s Spectacles are standalone, see-through binocular AR smart glasses running Snap OS, on which third-party Lenses (AR apps) execute directly on the device — no tethered phone required (Snap Newsroom, SPS 2024). Two models are in scope. The Spectacles 5th gen (2024) is the current developer edition: Snapdragon AR2 Gen 1, four cameras driving the Spatial Engine and dual-hand tracking, binocular waveguide displays with a 46° stereo FOV at ~37 ppd, 13 ms motion-to-photon latency, 226 g, ~45 min battery (developer-tech). Specs (2026) is the consumer/pro successor unveiled 16 June 2026 at AWE: fully standalone, two Snapdragon processors (one CV, one for Lenses), proprietary LCoS see-through display, 51° FOV, 16M colors, electrochromic lenses, 7 ms latency, TR90 frames at 132–136 g, up to ~4 h mixed-use battery plus a charging case; $2,195 with a $200 refundable deposit, shipping fall 2026 in the US, UK, France (Snap Newsroom, Introducing Specs). Both are camera+mic+speaker AR smart glasses with on-board compute (standalone, not a peripheral).

Access

The primary SDK is Lens Studio 5 — a free, proprietary AR-first IDE from Snap supporting TypeScript and JavaScript natively, plus SnapML for running custom ML models on-device (ar.snap.com/spectacles). It is GA and mature (10 Snap OS updates with 40+ new features/APIs over ~1.5 years, per Snap Newsroom). First-party frameworks — Spectacles Interaction Kit (SIK), UI Kit, Sync Kit, Auth Kit, Navigation Kit, Mobile Kit, and Commerce Kit (closed beta) — install from the Lens Studio Asset Library (Introduction); sample projects are public on GitHub (Snapchat/Spectacles-Sample). Lens Studio itself is proprietary (free download); sample/community code is typically MIT. There is also a second, Lens-Studio-free build path: Spectacles ships a native browser with WebXR, so you can author AR with standard web tech (Snap recommends PlayCanvas) and run it in the on-device Browser Lens (WebXR). Agent-driven development is live, not just previewed: Lens Studio ships a built-in MCP server (AI Assistant → MCP → Configure/Start Server) that lets external coding agents — Claude Code, OpenAI Codex, Cursor — drive the IDE to generate, debug, optimize, and publish Lenses (developer mode with Claude Code). Hardware access is gated by the paid Spectacles Developer Program: US-only, $99/month with a one-year commitment, which ships the glasses and includes Snap support (UploadVR). Anyone can download Lens Studio and read the docs; you need the subscription (or, from fall 2026, a purchased pair of Specs) to run on real hardware. Docs: developers.snap.com/spectacles.

App model

Code runs on the glasses, not on a phone: a Lens is a Snap OS AR application authored in Lens Studio (TypeScript/JS + scene graph, optionally SnapML), deployed wirelessly to the device (Introduction). Snap has broadened well past a single authoring path. A Native Development Kit (NDK), announced at AWE 2026, brings C and C++ code and libraries directly into Lenses (spatial mapping, physics, audio, networking, navigation), and a Unity-to-Lens-Studio Migration Agent translates Unity project structures, components, and scenes into native Lens Studio projects — Niantic Spatial ported its VPS via the NDK and Mapbox ported its Navigation Engine in under two hours (Snap Newsroom, tools for Specs developers). Separately, WebXR Browser Lenses are an entire second dev-and-distribution system: standard web AR that runs in the on-device browser with no Lens Studio involved (WebXR). On-device networking is available (WebSocket API, and the Remote Service Gateway for cloud AI), and Snap now offers a first-party managed backend, Snap Cloud (powered by Supabase): managed Postgres with Row Level Security, Storage, server-side Edge Functions (TS/JS), and Realtime, with auth bridged from Snapchat identity via OpenID Connect — currently alpha/approval-gated and free during alpha (Snap Cloud on Supabase). A companion Spectacles phone app exists only for auxiliary roles — phone-as-game-controller, Spectator Mode, screen mirroring — not for hosting app logic (ar.snap.com blog). Fit with Extentos's phone-companion model: low. Spectacles/Specs is a self-contained on-glasses AR runtime with its own managed backend and web path; there is no phone-side SDK surface where a companion app would drive the glasses the way Meta's DAT exposes the device. Extentos's abstraction targets a fundamentally different (phone-tethered) topology.

Distribution

Publishing is built into Lens Studio: hit Publish, supply an icon, a 3×4 preview image, description, and release notes; Snap's moderation team reviews the Lens within 2–3 business days against community guidelines and, if approved, lists it in Lens Explorer, the on-device store (Publishing Your Spectacles Lens). Max Lens size is 25 MB (vs 8 MB for mobile Snapchat). Public publishing is open to any developer in the program — no partner/enterprise gate — with review for a defined objective, 60 fps performance, no crashes, and design best practices (submission guidelines). Crucially, Snap's Transparent Permission system lets published Lenses combine internet connectivity with sensitive user data (camera, microphone, or location) as long as they use a supported permission combination (e.g. Internet Module + Camera Module, or Remote Service Gateway + Camera Module), gated at runtime by a per-launch permission prompt plus a hardware capture-LED indicator (Transparent Permission). The narrow residual block on wide-audience publishing is Experimental APIs (and unsupported permission combinations / insecure http) — not camera-plus-internet in general. A separate distribution channel bypasses Lens Explorer entirely: WebXR Browser Lenses are served from ordinary web hosting by URL with no app-store requirement or moderation review (WebXR) — the Snap analog of Meta's Display Web Apps. Snap also runs Spectacles Community Challenges with cash prizes and reports 'hundreds of Lenses already published' for Specs.

Capabilities, limits & AI

Camera: the CameraModule provides on-device camera access to Lenses (Camera Module). Combining camera (or other sensitive data) with internet access is publishable via Transparent Permission with a supported permission combination, and Lenses using the dedicated Remote Service Gateway AI integrations can use camera access and ship publicly without Extended Permissions or Experimental APIs (Transparent Permission); the only publish-blocking path is Experimental APIs. Microphone/audio: captured via MicrophoneRecorder; on-device speech via VoiceML. Audio output/TTS: speakers are available; TTS and generative voice come through the Remote Service Gateway (OpenAI TTS/Realtime, Gemini Live) with DynamicAudioOutput for PCM16 playback. Display/UI: full see-through binocular AR — you render a 3D Lens Studio scene (or a WebXR scene) into the wearer's FOV; SIK provides spatial UI. Sensors: Spatial Engine (SLAM), Depth Module, dual-hand tracking, plus GPS/location for outdoor location-based Lenses. Input: hand tracking with three SIK modes (ray-pointer, pinch, poke), voice, and optionally the phone-as-controller; no dedicated hardware controller or neural band. Persistence/backend: beyond on-device WebSocket, Snap Cloud (Supabase-backed) offers managed Postgres/RLS, Storage, Edge Functions, and Realtime with Snapchat-identity auth (Snap Cloud). AI & the assistant: there is no first-party Snap voice assistant exposed to third parties; instead Snap offers a strong bring-your-own-AI path via the Remote Service Gateway, a Snap-brokered proxy to OpenAI (GPT chat, image gen/edit, TTS, Realtime voice), Google (Gemini text/multimodal, Imagen, Lyria), Snap-hosted DeepSeek R1, and Snap3D (text-to-3D GLB) (Remote Service Gateway). On-device AI is available through SnapML custom models. Voice invocation of AI is a developer-built pattern (mic → LLM → TTS), not a reserved system assistant — and, per Transparent Permission, such camera+internet AI Lenses are publicly publishable.

Roadmap

16 Jun 2026 (AWE): Snap unveiled Specs, the 2026 consumer AR smart glasses, at $2,195 + $200 deposit, shipping fall 2026 (US/UK/France), alongside a Snap3D API, a shipping Native Development Kit (C/C++ + Unity Migration Agent), an agentic development path (Lens Studio's built-in MCP server driving Claude Code, Codex, Cursor), a Spatial Benchmark, and location-experience tools (Fleet Management, Guided Mode, Guided Navigation) (Snap Newsroom; tools for Specs developers; investor release, Sep 2025). Momentum is high: 10 Snap OS updates / 40+ APIs over ~18 months, hundreds of Lenses already published. Announced-but-unshipped as of this writing: Specs retail units (fall 2026), Commerce Kit (closed beta), and Snap Cloud (alpha, approval-gated). The 5th-gen Spectacles remain the shipping dev hardware via the $99/mo program until Specs ships.

In the landscape

Snap Spectacles is one platform in the third-party smart-glasses landscape. See how open it is relative to other platforms, how AI works across them, and the full platform comparison.

Related