Apple smart glasses
Apple smart glasses for third-party developers — SDK access, app model, distribution, capabilities & AI, and where it sits in the 2026 smart-glasses landscape.
Openness verdict. Closed by absence: as of July 2026 there is no shipping Apple glasses product and no glasses developer SDK. The only concrete developer surface is phone-side on-device AI — and that surface is real and increasingly open (Foundation Models, the new Core AI framework, MLX, and a first-party LoRA-adapter toolkit on iOS/iPadOS/macOS/visionOS), just not scoped to any glasses device.
Covered here: Apple smart glasses.
Not covered here: Apple Vision Pro · Rumored "Vision Air" · Camera-equipped AirPods (rumored, reported ~late-2027).
Overview
Apple has not shipped a smart-glasses product, and as of July 2026 has made no official announcement of one — nothing on the Apple Newsroom or Apple Developer site names a glasses device. Multiple press reports (Bloomberg's Mark Gurman, relayed via outlets such as 9to5Mac) describe an internal program ("N50") aimed at an audio-and-camera AI accessory — cameras, mics, speakers, Siri/Apple Intelligence for interaction, no on-lens display in the first generation, iPhone-tethered — reportedly slipped to a late-2027 launch. Treat all of that as unverified signal, not product. The closest in-class precedent is not Vision Pro but Apple's own audio accessories: reporting points to camera-equipped AirPods on a similar ~late-2027 window and the same audio-first + camera + Siri-visual-intelligence design (MacRumors), and AirPods Live Translation (iOS 26, processed on-device on the paired iPhone) is the actual shipping pattern for an Apple audio accessory driving on-device Apple Intelligence (Apple Support) — the concrete template a glasses accessory would most plausibly inherit. The only Apple hardware in the adjacent MR space that actually ships is Apple Vision Pro (out of scope here — it is not glasses). Pricing, hardware spec, and ship date for any Apple glasses are unknown; the figures circulating point to a reported ~$200–$500 target, which is analyst/rumor, not Apple.
Access
There is no Apple glasses SDK — no framework, package, or documentation for building glasses apps, because there is no device. What Apple does ship is a deep and increasingly open phone-side on-device AI stack, none of it glasses-scoped: (1) the Foundation Models framework — a native Swift API giving direct access to the same on-device model that powers Apple Intelligence, introduced at WWDC in June 2025 (session 286) and made available with iOS 26 / iPadOS 26 / macOS 26 / visionOS 26 in September 2025 (Newsroom), backed by Private Cloud Compute for heavier inference; (2) the new Core AI framework, announced at WWDC26 (June 2026) and shipping with the 2026 OS line — a memory-safe Swift API to load, specialize, and run arbitrary on-device models, 'everything from compact vision models to large-scale generative AI,' with ahead-of-time compilation and fine-grained inference/memory control, paired with a curated Core AI Models repo (Qwen, Mistral, SAM3) each convertible with one command via standard Python/PyTorch workflows (What's new in ML, session 324); and (3) MLX, Apple's open-source array framework for Apple silicon, which lets developers run and fine-tune arbitrary LLMs on-device via the MLX / MLX-LM Python packages (the mlx-community org hosts thousands of quantized models) (opensource.apple.com). All of it is buildable in Xcode by anyone in the paid Apple Developer Program under the standard license agreement; models run on-device and offline. This is the substrate an eventual glasses accessory would most plausibly build on — but it is phone/Mac software, not a glasses platform.
App model
Undefined for glasses — no app model exists because no device or SDK ships. For the phone-side paths, code runs natively in Swift inside a standard iOS/iPadOS/macOS/visionOS app: Foundation Models runs the on-device model with optional escalation to Private Cloud Compute, while Core AI and MLX let an app load and run arbitrary on-device models with no server dependency and no token cost. There is no glasses runtime, no web-app layer, and no game-engine target. Apple has published no phone↔glasses transport, but it already ships the exact frameworks a phone-tethered Bluetooth accessory uses: AccessorySetupKit (iOS 18+, proximity-triggered secure pairing without broad Bluetooth scanning), the ExternalAccessory framework, and the MFi Program (Apple-licensed accessory protocol strings via UISupportedExternalAccessoryProtocols) (AccessorySetupKit, Accessories). A reported audio-first iPhone-companion accessory would almost certainly surface through these — MFi in particular is a genuine gating/reserved surface — though nothing glasses-specific is documented. The plausible shape is an iPhone-companion accessory (phone does the AI) rather than an on-device third-party app platform, but that is inference from reporting, not documentation.
Distribution
Not applicable to glasses — with no device and no SDK there is no distribution channel, no publishing path, and no review process for glasses apps. For context, Apple's general model is the App Store with mandatory App Review, and a licensed hardware accessory additionally routes through the MFi Program (Accessories). A companion glasses accessory would most likely surface as features inside existing iPhone apps distributed through the App Store rather than as a separate storefront, but Apple has published nothing on this. Any developer/publishing timeline is unknown and gated on Apple first announcing hardware.
Capabilities, limits & AI
All glasses hardware capabilities are unknown/unshipped. Reporting (unverified) describes cameras, microphones, and speakers with no on-lens display in the first generation and Siri/audio as the primary interaction — but Apple has documented none of it, so camera access, mic/audio streaming, TTS/audio-out APIs, sensors, gesture input, and any reserved system surfaces are all undefined for third parties. AI & the assistant: there is no glasses assistant to open up. On the phone side, Siri/Apple Intelligence is not a general third-party programmable assistant — developers integrate via App Intents/Shortcuts and, for on-device generation, the Foundation Models framework, which supports tool calling, guided (structured) generation, and streaming, runs on-device and offline, and — as of WWDC26 — is materially more capable in glasses-relevant ways: it now accepts multimodal prompts (images alongside text), can call on-device Vision tools (OCR, barcode), supports Dynamic Profiles (swap models/tools/instructions at runtime), ships an Evaluations framework, and gives free Private Cloud Compute access to the latest server model for apps under 2M first-time downloads (What's new in ML). The BYO-model story is genuinely rich and mostly first-party: the Foundation Models adapter training toolkit lets you fine-tune Apple's own on-device model with your data via rank-32 LoRA adapters (~160MB each, loadable at runtime, with an optional speculative-decoding draft model) — the most glasses-relevant path, a small model specialized for an accessory's task (adapter toolkit); the new Core AI framework and MLX let you load, run, and fine-tune arbitrary open models on-device; and a third-party provider layer lets other LLM vendors plug in, with Anthropic (Claude) and Google (Gemini) packages announced/upcoming (WWDC26 session 339). Apple's own next-generation Apple Intelligence uses Google Gemini for server-side tasks. Voice invocation of custom logic goes through Siri/App Intents, not a raw wake-word API. None of these AI hooks are exposed on or scoped to a glasses device today.
Roadmap
Shipped/dated (primary): Foundation Models framework introduced at WWDC June 2025 (session 286), available with iOS/iPadOS/macOS 26 in September 2025; at WWDC26 (June 2026) Apple announced the Core AI framework for running arbitrary on-device models, expanded Foundation Models to multimodal + Dynamic Profiles + Evaluations + free PCC under 2M downloads, and surfaced a third-party provider layer (Claude/Gemini packages announced/upcoming, session 339); next-generation Apple Intelligence + a more capable Siri, built with Google Gemini for server tasks, detailed June 2026. Glasses (reported, not announced): press reporting through 2026 (Gurman/Bloomberg via outlets like AppleInsider and 9to5Mac) points to a late-2027 launch for an audio-first "N50" accessory, delayed to let Apple's visual AI mature, with a lighter "Vision Air" headset reportedly ~2029. Momentum: heavy, accelerating investment in the on-device AI substrate (Foundation Models → Core AI → MLX → the adapter toolkit — the likely foundation for any future glasses), but zero official glasses hardware or SDK signal — no announced device, no developer preview, no dated SDK. Extentos will add an Apple glasses transport if and when Apple ships an actual SDK; until then there is nothing to target.
In the landscape
Apple smart glasses 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
The third-party smart-glasses landscape
Can you build third-party apps for smart glasses today? A platform-by-platform comparison — Meta, Snap Spectacles, Brilliant Labs, Rokid, RayNeo, Even Realities, Vuzix, Android XR, Apple and more: which have an official SDK, how apps are built and distributed, and whether you can publish publicly.
How open is smart-glasses development?
A mental model for the openness spectrum in smart-glasses development — SDK availability, license, build-time gating, and publishing gating — with today's platforms placed on it.
AI on smart glasses
How third-party AI works across smart-glasses platforms — which first-party assistants are reserved (Meta AI, Gemini, Ari), where you bring your own AI (phone-side, cloud, on-device), wake-word limits, and the voice-in → AI → voice-out surface that generalizes even where the assistant is closed.
How third-party smart-glasses apps are distributed
Smart glasses don't have one app store. The app-model taxonomy — companion mobile app vs. an app that runs on the glasses (native or web) — and why a single platform (Meta) offers two entirely separate developer systems: DAT and Ray-Ban Display Web Apps.
Meta smart glasses (Meta DAT)
Meta smart glasses developer guide: DAT 0.8.0 capabilities, supported models (Ray-Ban Meta, Oakley Meta, Ray-Ban Display), 2026 distribution state, and how Extentos abstracts the toolkit.
Capabilities
The Extentos capability vocabulary — the vendor-agnostic SDK primitives (audio, camera, voice, assistant, display, hardware events) your handler subscribes to.
Solos
Solos for third-party developers — SDK access, app model, distribution, capabilities & AI, and where it sits in the 2026 smart-glasses landscape.
MCP server
The Extentos MCP server (`@extentos/mcp-server`) is an npm package an AI agent (Claude Code, Cursor, Windsurf, Cline) installs once and then uses to add Meta Ray-Ban smart-glasses capabilities to a native iOS or Android app. It exposes a tight set of deterministic tools across 10 categories — discovery, generation, agent configuration, credentials, analytics, guidance, validation, simulation, production-readiness, and documentation — plus a CLI for account linking, telemetry consent, and update checks. This is the agent's operating manual.