Rokid

Openness verdict. Openly documented, registration-free developer suite with a bimodal openness story: the native glasses/phone SDKs are proprietary (closed-source AARs), while the on-glasses AIUI app framework — a JavaScript + Ink web-style runtime (JSAR) — is open source (Apache-2.0). Four dev axes ship in parallel (phone companion, on-glasses native, on-glasses AIUI web-runtime apps, and cloud/bring-your-own-model agents), with an unusually open third-party-AI path. Distribution is the least-settled part: sideload-to-glasses (phone app, WebUSB, community stores) works today, but a first-party public app store and review pipeline are only partially in place.

Covered here: Rokid Glasses (2025) · Rokid AI Glasses Style (2026).
Not covered here: Rokid Max / Max Pro · Rokid AR Lite / AR Spatial · Rokid Station / Station 2 · Rokid Dock.

Overview

Rokid is a Hangzhou-based XR/AI-wearables maker. Rokid Glasses (launched Aug 27 2025, newsroom) are 49 g standalone AI+HUD glasses and the in-scope device here. Hardware snapshot: dual-eye monochrome-green Micro-LED engines on a diffractive optical waveguide (~480×398 per eye, up to 1500 nits; the product page cites a 30° FOV while launch coverage cited ~23°), a 12MP Sony IMX681 first-person camera (fixed-focus, no AF), 4 directional microphones, 2 speakers, Wi-Fi 6 / BT 5.3, 2 GB RAM / 32 GB storage, 210 mAh battery. Compute is standalone (Snapdragon AR1 Gen 1 for the app OS + an NXP RT600 for low-power voice/wake), not a dumb phone peripheral — but a paired phone (Hi Rokid app) drives setup, heavy AI and most third-party UX. Price is $599–$699 depending on region/promo; shipping globally now (orders outside the EU ship from China). Out of scope: the birdbath Max viewers and Station-puck-driven AR Lite/Spatial (tethered/controller AR). A display-less sibling, Rokid AI Glasses Style ($299, 38.5 g, camera+audio only), shares the ecosystem but has no HUD.

Access

The developer surface centers on Rokid's connected-XR SDKs, documented at x-docs.rokid.com and the Rokid Open Platform (ar.rokid.com/sdk redirects here). The official docs frame it as a Glasses SDK (device side) + Phone SDK (companion) pairing targeting 'Rokid Glass3'; the widely-cited CXR-M / CXR-S / CXR-L nomenclature (phone-companion / on-glasses / standalone-replacement) comes from the community mirror buildwithfenna/rokid-docs rather than the primary pages. The phone companion connects over BLE / Wi-Fi Direct; on-glasses apps run natively on YodaOS-Sprite (an Android-12/API-32-based OS) and talk to the phone over a bidirectional data channel; a standalone variant binds to the on-device Rokid AI service via Android AIDL. Languages/frameworks are broader than the native SDKs alone: the Glasses/Phone SDKs are Kotlin/Java (Android) and native iOS for companions, but a second, materially different toolchain exists for on-glasses AIUI apps — JavaScript + the 'Ink' declarative UI framework (.ink single-file components) running on the JSAR (JavaScript-AR) web-style runtime. A separate, older Unity UXR SDK exists but targets the legacy Dock/phone-tethered line (archived 2021) — not Rokid Glasses. (Community-mirror specifics — Android minSdk 28, the Maven coordinate com.rokid.cxr:client-m on maven.rokid.com, and version client-m:1.0.8 — are reported by that mirror, not confirmed against a primary Rokid page.) License is bimodal: the native Glasses/Phone SDKs are proprietary (closed-source AARs, no OSS license), whereas the AIUI app tooling — CLI, samples, agent skills — and the underlying JSAR runtime are open source (jsar-project/AIUI, Apache-2.0). Maturity: shipping/GA product with actively evolving 1.x SDKs. Who can build: open self-serve — free developer registration/verification on the Open Platform unlocks the SDKs, the AIUI agent tooling, and the forum (Rokid cites 30k+ registered developers). Docs are English + Chinese.

App model

Rokid deliberately exposes multiple dev systems, so where your code runs is a design choice: (1) Phone-companion — your Android/iOS app owns the UX and calls the glasses for camera/mic/display/voice over BLE or Wi-Fi Direct; (2) On-glasses native — Kotlin/Java Android apps running on YodaOS-Sprite on the glasses themselves; (3) On-glasses AIUI apps — a distinct web-runtime app framework where you write JavaScript + Ink (.ink SFCs), scaffold with the official CLI npm create @yodaos-pkg/aiui-agent, and render UI to the HUD via the JSAR runtime — the Rokid analogue to Meta's Display Web Apps, and publishable without physical hardware (jsar-project/AIUI); and (4) a cloud AI agent via AIUI (an SSE endpoint your glasses call). So the platform is not uniformly 'native Android/iOS' — the AIUI/Ink path is an explicitly web-style runtime, and Unity is only the legacy tethered path. Fit with Extentos's phone-companion model: strong on the phone-companion axis — a phone app mediating capture/voice/HUD to the glasses over BLE/Wi-Fi is exactly the companion shape Extentos targets, so a phone-side integration is the natural mapping. The on-glasses native, AIUI/JSAR, and cloud-agent paths are Rokid-specific extras with no Extentos analogue.

Distribution

Reaching users is the least-settled part of the platform, and the install landscape is more active-but-fragmented than a single 'community store exists' conveys. Today the practical path is sideload-to-glasses over several transports — the Hi Rokid companion app (App Store + Google Play) installs local apps from the phone onto the glasses, but sideload also spans Bluetooth SPP, Wi-Fi LAN, and USB, including browser-based WebUSB installation where a catalog page (e.g. the EUNG SOFT catalog) flashes an app onto the glasses directly from the web. Multiple community stores exist (RokidBrew plus the store referenced by awesome-rokid). Rokid has publicly said an SDK + first-party app store is on the roadmap, but a fully open first-party store with a documented submission/review pipeline for on-glasses binaries is not yet clearly in place in English docs. The clearly-open first-party publishing path is for the AIUI app/agent class: the Open Platform's AIUI agent console (AIUI Studio) offers a design→code→debug→deploy flow that publishes without physical hardware, and AIUI custom agents additionally support unreviewed private deployment (point the glasses at your own endpoint — no store gate). Public publishing / content review: partial — first-party and documented for AIUI apps/agents, but undocumented in English for on-glasses native binaries, where sideload and self-hosted agents remain the reliable routes. No MDM-specific path is documented publicly.

Capabilities, limits & AI

Camera: 12MP photo, video, and frame/media capture exposed through the Glasses SDK's camera-and-media module (fixed-focus, 3°-inward tilt; gated behind SDK connection/permissions). Microphone/audio capture: 4 directional mics with ASR; audio output/TTS via the 2 speakers, all first-class SDK capabilities (the voice/AI module covers ASR, TTS, chat). Recognition/CV: the Glasses SDK ships a dedicated recognition module with packaged face detection and vehicle license-plate recognition as SDK-exposed primitives — notable for an in-class device (the module set is media, voice/AI, recognition, messaging/files, device-state, Bluetooth/ring, and P2P). On-lens display/UI: yes — a monochrome-green Micro-LED waveguide HUD for glanceable text/overlays; you render either by running an on-glasses app (native or an AIUI/Ink JSAR app) or by pushing messages/notifications from the phone. It is a low-FOV glanceable HUD, not a rich spatial-AR canvas. Sensors/input: temple touchpad, buttons, head gestures, voice, and an optional smart ring accessory (the SDK enumerates Bluetooth smart-ring connectivity); IMU is present but not prominently documented as a public stream, and location typically comes from the phone. Reserved surfaces: the 'Hi Rokid' wake phrase/trigger and the default assistant ship first-party; there is no clean third-party wake API, and community integrations resort to intercepting assistant responses/notifications via the Android Accessibility Service. AI & the assistant: unusually open at the model layer even though the wake trigger stays reserved. Via AIUI and the Customizable Agent feature (announced Feb 2026), developers can bring their own model — privately-deployed DeepSeek R1, Qwen3, Kimi K2.5, etc. — by registering on the Open Platform and configuring an agent URL + auth key; the glasses call it over SSE, with support for tool/agent frameworks (OpenClaw) doing browser/file/Python actions. Voice invocation drives it; on-device compute (the NXP RT600) handles wake/low-power voice while heavier inference is cloud or phone. Net: third-party AI is a supported, first-class path, which is rare in this class.

Roadmap

Recent: Rokid Glasses launched Aug 27 2025 (NYC event + Kickstarter that topped $400–500k in hours) and are now shipping globally at $599–$699; the Glasses/Phone SDKs and the AIUI app tooling are live on the Open Platform. Feb 11 2026: the 'Customizable Agent' bring-your-own-model feature (DeepSeek/Qwen/Kimi via SSE, unreviewed private deployment) was announced — the platform's most notable openness move. The display-less AI Glasses Style ($299) expanded the lineup in 2026. Announced-but-maturing: a first-party app store / public publishing pipeline for on-glasses native binaries (referenced by Rokid but not yet fully documented in English). Momentum: high — a large existing CN developer base (Rokid cites 30k+ registered developers), an active global developer push, an open-source AIUI/JSAR app runtime, and frequent SDK iteration; the main gap for outside developers is a clear public distribution/store story for native apps.

In the landscape

Rokid 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