--- title: "INMO" seoTitle: "INMO for developers: SDK, app model & distribution (2026)" description: "INMO for third-party developers — SDK access, app model, distribution, capabilities & AI, and where it sits in the 2026 smart-glasses landscape." type: reference platform: all vendor: inmo related: - /docs/ecosystem - /docs/ecosystem/openness - /docs/ecosystem/ai - /docs/ecosystem/distribution - /docs/vendors/meta - /docs/concepts/capabilities --- > **Openness verdict.** Unusually open at build time — the in-scope INMO Air3 is a standalone Android 14 device that ships (internationally) with the Google Play Store, plus a Unity SDK and a beta n8n-style agent platform — but the openness is qualified: the SDK's real API reference sits behind a login-walled Feishu doc, the sample kit carries Air2/RING2 heritage rather than being cleanly Air3-first, app distribution mixes an open Play-Store path with a curated first-party Air3 store, and there is both a reserved first-party wake word ("OK Amu") and a curated INMO-hosted in-app runtime for agent workflows. **Covered here:** INMO Air3. **Not covered here:** INMO GO · INMO GO3 · INMO Air2. ## Overview INMO XR (Shenzhen-based Yingmu Technology / 影目科技) builds standalone AR + AI eyewear. The in-scope developer device is the **INMO Air3**: an all-in-one, standalone AR headset rather than a phone-tethered viewer. Hardware snapshot ([product page](https://www.inmoxr.com/products/inmo-air3-ar-glasses-all-in-one-full-color-waveguide)): binocular Sony Micro-OLED via 1D diffractive waveguide at 1920×1080, 36° FOV, up to 600 nits, 60/120 Hz; a 16 MP 120° ultra-wide camera with EIS; 4 microphones and 2 speakers; a Qualcomm Snapdragon 8-core (8 GB RAM / 128 GB storage) running **Android 14 / IMOS 3.0**; a 660 mAh battery. On-board compute is **standalone** (a full Android device on your face), not a peripheral. Input is a bundled touchpad, an optional 3DoF smart ring, and a hand-tracking wristband described as a future accessory. Shipping now as a **Global version at $1,099**. The lighter INMO **GO / GO3** translation glasses are out of scope (closed-function appliances, no published SDK). ## Access The published toolkit is the INMO Unity SDK, whose canonical home appears to be [Gitee under the INMOLens org](https://gitee.com/inmolens/inmo-sdk-sample-unity), with the [GitHub air3-unity-sdk repo](https://github.com/INMOXR/air3-unity-sdk) a thin mirror (~30 stars, a handful of commits). The sample kit historically targets **INMO Air2 + RING2** (touchpad interaction and AR-capability development, min Android API 28, Unity 2020.3 LTS) ([dev guide](https://medium.com/@hanlanyi/inmo-development-guide-adb-activation-unity-sdk-f13ba6797c1e)), so the toolchain carries Air2/RING2 heritage rather than being cleanly Air3-first. Its real API reference lives in external [Feishu docs](https://inmolens.feishu.cn/docx/XeN4dUM2KomVfDxTuWMcgWdlnob) that are **login-walled**, so the exact exposed surface (camera/mic/display-region/ring/head-tracking APIs) can't be verified from a primary public source; a community [Unofficial INMO Air 3 Wiki](https://github.com/sam1am/inmo_air_3_wiki) partly fills that gap. Because Air3 is native **Android 14**, standard Android/Kotlin/Java development also applies — there is no need to go through the Unity SDK to ship an app. Maturity: preview/early — no version tags or license file are visible in the repo (license **unknown**). Who can build: **open** — any developer enables Developer Mode on-device by tapping the build number 10 times ([support](https://support.inmoxr.com/air3/development/unlock-developer-mode/)); enabling ADB mode is a separate on-glass step (long-press the right touchpad twice, ~1.5s each, then enter a factory password) that is documented to **void the 7-day no-reason return policy** — a real developer gotcha. No invite or partner gate to develop. Docs hub: [support.inmoxr.com/air3](https://support.inmoxr.com/air3/) plus the Feishu SDK docs. ## App model Code runs **on the glasses** as a standalone Android 14 app — there is no required phone host. **Three developer surfaces** exist: (1) native **Android** (Kotlin/Java) apps installed directly on the device; (2) **Unity** apps built with the INMO SDK; and (3) the **[INMO Multimodal Agent Developer Platform](https://www.inmoxr.com/blogs/news/introduction-inmo-multimodal-agent-developer-platform)**, an n8n-based low-code orchestrator (beta) whose 'apps' are **not standalone Android packages** but visual workflows **published into the on-device INMO Air3 'Super App'** via one-click publish and server-side **hot updates**. Those agent apps run in a curated, INMO-hosted **in-app surface** — rendering into screen regions and controlling volume and progress bars while capturing image/voice/text and returning text/image/audio/video — the closest analog to Meta's Display Web Apps, and distinct from sideloading an APK. Otherwise transport is self-contained (native/Unity apps are on-device); an INMOLens companion app handles casting/management to phone/PC. **Fit with Extentos's phone-companion model:** weak/orthogonal — Extentos assumes a phone app driving a display-limited peripheral over BLE, whereas Air3 runs full Android apps locally. An Extentos-style integration would look like a normal Android app on Air3, not a companion-and-peripheral split. ## Distribution Multiple paths, unusually open for AR: the **international Air3 ships with Google Play Store and Chrome** (INMO cites an official Google deal and 90%+ Android-app compatibility, per the [product line page](https://www.inmoxr.com/pages/inmo-air3) and third-party review coverage), so apps reach users the same friction-free way as on a phone. There is also a curated **INMO Air3 App Store** for glasses-optimized apps (submission-based), plain **ADB sideloading** after Developer Mode, and **one-click publish / hot updates** into the Super App from the Multimodal Agent platform. Public publishing is therefore **open via Google Play** and **submission-gated via the Air3 store**; content-review specifics for the Air3 store are not documented publicly. No preview→GA release-channel invite gate like Meta's DAT exists. ## Capabilities, limits & AI Camera: 16 MP 120° ultra-wide with EIS, video-capable — photo/video capture supported at the OS level; frame-level API gating is not documented in a public source. Microphone: 4-mic array; audio out: 2 speakers — both available to Android apps. On-lens display/UI: **yes**, a real binocular 1080p waveguide you render to as a standard Android/Unity full-screen surface (the agent platform can also target screen regions). Sensors: head-tracking/IMU implied by the AR positioning and Unity SDK but not confirmed via a public API doc; a SLAM/spatial-anchor API appears absent from public docs, though that absence could not be confirmed against a primary source. Input: bundled touchpad, optional 3DoF smart ring, future hand-tracking wristband; no neural band. **Reserved surfaces:** Air3 ships a first-party AI assistant activated by the reserved wake word **'OK Amu'** (Amu = 影目/INMO), documented in INMO copy and hands-on [reviews](https://www.androidfaithful.com/inmo-air3-review-android-apps-on-your-face-but-the-battery-cant-keep-up/) — a reserved wake surface analogous to Meta's 'Hey Meta'. Whether third-party apps can claim their own wake phrase or must yield to 'OK Amu' is not documented; gesture-monopoly and IMU restrictions are likewise undocumented either way. **AI & the assistant:** beyond the first-party Super App, the **Multimodal Agent platform is an explicit bring-your-own-AI path** — developers compose agents against OpenAI, Gemini, Claude, DeepSeek and Llama, plus HTTP/code/database/**MCP** tools, with voice/image/text invocation from the glasses. It is not purely bring-your-own-key: the platform also layers a **managed** governance surface — centralized credential management with platform-wide reuse of model API keys, granular credits/token metering, access control, and end-to-end execution logs — a managed-gateway/billing analog over the BYO-model providers. AI execution is **cloud or self-hosted** (models run off-device); on-device local inference is not claimed. Overall the platform reads as broadly open Android rather than a walled first-party runtime. ## Roadmap Air3 is shipping globally at $1,099 (Android 14 / IMOS 3.0) and reviewed in the wild in 2026. The **Multimodal Agent Developer Platform is in beta** (2026), signaling INMO is pushing an agent-first developer story on top of the raw Android/Unity access. The Unity SDK is live but minimal, slow-moving, and Air2/RING2-rooted. Adjacent lineup momentum: **INMO GO3** launched on [Kickstarter (announced 2026-04-02, $499)](https://www.prnewswire.com/news-releases/inmo-unveils-go3-next-generation-everyday-ai-smart-glasses-launching-on-kickstarter-302730972.html) as a translation-focused successor to GO — appliance-class, not a developer target. Announced-but-unshipped for Air3: the hand-tracking wristband accessory (described as tested/future). No public preview→GA gating timeline for app publishing beyond the existing open Play-Store + Air3-store paths. ## In the landscape INMO is one platform in the third-party [smart-glasses landscape](/docs/ecosystem). See [how open it is](/docs/ecosystem/openness) relative to other platforms, [how AI works](/docs/ecosystem/ai) across them, and the full [platform comparison](/docs/ecosystem).