EcosystemPlatforms

RayNeo (TCL)

RayNeo (TCL) for third-party developers — SDK access, app model, distribution, capabilities & AI, and where it sits in the 2026 smart-glasses landscape.

Verified 2026-08-24 against primary sources

RayNeo (TCL) at a glance
Third-party SDK
OpenXR Unity + Android ARDK (Unity MIT)github.com
App model
On-glasses standalone Android/Unity APKqualcomm.com
Distribution today
Sideload via ADB; App Lab launcher, no catalogskarredghost.com
Public publishing
No self-serve store; brokered submission existsskarredghost.com
Third-party UI on-lens
Binocular micro-LED waveguide, Unity renderrayneo.com
AI / assistant access
Assistant closed & region-split; BYO-AI in your appxrom.in

Openness verdict. Open, standard-based build path (MIT OpenXR Unity ARDK + a native Android ARDK, no partner/invite gate) — but there's a real developer-mode unlock and no consumer publishing surface. X-series apps run standalone on the glasses (not phone-companion), ship as sideloaded Android/Unity APKs, and reach devices via ADB or community sideload tooling (GBox); there is no self-serve public app store, though RayNeo's X-series docs publish a manually brokered submission and review route through its Open Platform. The platform assistant is first-party and closed, and region-split — Google Gemini in Western firmware, Alibaba's Qwen (Tongyi Qianwen) on China-market devices.

Covered here: RayNeo X2 · RayNeo X3 Pro.
Not covered here: RayNeo Air 4 Pro / Air 3s / Air 3s Pro · RayNeo Air / Air 2 / Air 2s · RayNeo GT Max · RayNeo V3 / V4 · RayNeo earlier XR viewers.

Overview

RayNeo is the smart-glasses brand of Thunderbird Innovation, a TCL-backed venture. Its X-series are standalone binocular AR smart glasses with full-color micro-LED optical-waveguide displays — the in-scope class here. The X3 Pro (shipped late 2025) runs a self-contained Android-based OS on a Qualcomm Snapdragon AR1 Gen 1 (4GB RAM / 32GB storage), with a dual-camera rig (Sony IMX681 RGB for 12MP photos / up to 4K video plus an OV monochrome camera for spatial tracking), open-ear speakers and mics, an IMU, and SLAM-based tracking (3DoF at launch — see capabilities); the co-developed waveguide runs ~3,500 nits typical / 6,000 nits peak, 30° FOV, at ~76g. Its predecessor, the X2 (shipped 2024, Snapdragon XR2, ~1,000-nit micro-LED waveguide), was billed as the first binocular full-color micro-LED waveguide consumer AR smart glasses. Pricing for the X3 Pro is $1,299.00 regular on the US store, currently discounted to $1,099.00 in an "End of Summer Sale" ending 31 August 2026 (€1.259,00 against a €1.399,00 regular price on the EU store), sold via RayNeo's US/EU regional stores; the X2 launched on Indiegogo at ~$699 early-bird. Out of scope: the RayNeo Air line (Air 3s / Air 3s Pro etc.) are tethered birdbath micro-OLED viewers with no on-board compute or app runtime; separately, the display-less RayNeo V3 camera-and-audio AI glasses are a distinct Ray-Ban-Meta-class line (scoped out below, though it is the RayNeo device closest to Extentos's target class).

What you can buy

ModelPriceStatus
RayNeo X3 Pro
rayneo.com
$1,299.00 on the rayneo.com US store, with no compare-at price shown. On the EU store it is €1.259,00, marked down from a regular price of €1.399,00 ("Save €140,00"); the Shopify product record gives price €1,259.00 with compare_at_price €1,399.00.On sale
RayNeo X2
rayneo.com
$499.00 on the rayneo.com US store, the standing store price. EU store: €799,00. It launched on Indiegogo at roughly $699 early-bird; the current store prices are later standing prices, not the crowdfunding figure.Discontinued by vendor

Cheapest way to run your own code: The cheapest RayNeo you can buy and run your own code on is the RayNeo X3 Pro at $1,299.00 (€1.259,00 promotional against a €1.399,00 list price on the EU store) — the cheaper Air-series models from $149.00 are tethered display viewers with no on-board compute or app runtime, and the $499.00 / €799,00 X2 is Sold Out on both storefronts. Even at $1,299.00 the device does not arrive ready to run your code: consumer firmware blocks third-party installs until ADB is unlocked through an undocumented hidden gesture, and there is no self-serve app store.

What the listings leave out

RayNeo X3 Pro

  • One purchase configuration on each storefront (a single "Default Title" Shopify variant on both US and EU), with no frame colours, lens tints, or sizes selectable; prescription correction is an off-store add-on through a third-party lens partner.
  • The regional price split is real rather than an exchange-rate artefact: $1,299.00 on the US store against a €1.399,00 EU list price. Neither figure is a conversion of the other.
  • The €1.259,00 shown on the EU store is a promotional price against a €1.399,00 compare-at figure, not the list price, so quoting €1.259,00 as the EU price will be wrong once the promotion ends.
  • The roughly $1,099 early-bird price this product launched against is no longer offered on either storefront as of 2026-07-30; both stores now sell at standing or promotional pricing.
  • There is a single purchase configuration on both stores, with no frame colour, lens tint, or size selectable at checkout — one "Default Title" variant in each storefront's Shopify record.
  • Prescription lenses are not included and are not a store variant; the product page routes customers to a third-party lens partner as a separate paid service. An unreleased first-party "Super-Fit Optics" single-lens solution is teased on the EU page with launch details still to be announced.
  • A "Trade In, See Beyond" promotion offering $799 trade-in credit against Meta Ray-Ban Display or RayNeo X2 trade-ins ran 12/5/2025-1/5/2026, US only, with limited slots, and expired as of 2026-07-30. It is still rendered on the EU product page despite being stated as US-only, so the page contradicts itself.
  • Seel "Worry-Free Purchase" financing and "Seel Electronics Protection" (listed separately at From $8.99) are optional paid add-ons rather than part of the sticker price.
  • On consumer ("user version") firmware, third-party installs are blocked by default. Running your own code requires unlocking ADB through an undocumented hidden gesture — repeated swipes on Settings › General › About Device, which toggles back off — and Windows sideloading can require an ADB driver downgrade. The purchase price does not buy an unlocked device.
  • There is no self-serve consumer app store. The only documented listing route is a manually brokered Open Platform submission: register and certify, upload the APK, email Developer@rayneo.com, and pass RayNeo functional and test-department sign-off. Shipping to real users is not a solved path at any price.
  • AR tracking is 3DoF at launch, short of the marketing. 6DoF SLAM is gated behind Creator Mode and, per hands-on reporting, world-locked 3D content is not reliably stable today. Eye- and hand-tracking have no ARDK API.
  • The assistant is first-party, closed, and split by region — Google Gemini on Western firmware, Alibaba Qwen on China-market devices — and reserved behind the "Hey RayNeo" wake word with no third-party hook, so what an identically-named unit does depends on which market's firmware it carries.
  • The public GitHub OpenXR Unity ARDK package is the X2-era 1.0.1-r3 (Unity 2020.3, last commit October 2024), while current X3 Pro tooling (native Android ARDK v0.2.6, Unity ARDK 1.1.2, Unity 2022.3.36f1) is distributed through RayNeo's Chinese-language developer manual instead. The freshest tooling is not on the public repo.
  • China-market pricing and availability are unverified as of 2026-07-30, as rayneo.cn refused the connection. No CNY figure is asserted here.

RayNeo X2

  • One purchase configuration with no appearance variants — no frame colours or lens tints — and the only Shopify option is "Selling Countries" with the single value "US", which is a region flag rather than an appearance choice.
  • It is Sold Out, shown as "Out of stock", on both storefronts as of 2026-07-30, with the buy button disabled on the US and EU pages alike. It cannot be bought at either listed price today.
  • RayNeo lists this model in a vendor-curated collection titled verbatim "Discontinued Products" on BOTH storefronts — the sole member on the US store, one of five on the EU store. The collection is curated rather than stock-driven: other fully sold-out items are left out of it, so membership is RayNeo's own classification, not an automatic consequence of zero stock. That is what makes this a vendor statement rather than an inference from absence. The price stays live on both listings ($499.00 / €799,00) and the buy control reads "Sold Out".
  • "Out of stock" is the vendor's own status string and normally implies a temporary condition, but this is a 2024 product superseded by the X3 Pro and unbuyable on both stores, and no vendor statement addresses how temporary it actually is.
  • The regional price split is large and unexplained: $499.00 against €799,00, roughly a 60% gap in nominal terms and far beyond any exchange-rate movement.
  • The current $499.00 store price sits well below the roughly $699 Indiegogo early-bird the product launched at, so the historical crowdfunding figure and the store price are separate facts and should not be blended.
  • On the EU store the listing's only variant is flagged "Selling Countries: US", so even the EU-priced listing is nominally not an EU-sold configuration.
  • Because it cannot be bought, the cheaper X-series entry point is unavailable in practice and the X3 Pro is the actual price floor for building on this platform.
  • The same platform-level gating as the X3 Pro applies to any unit sourced secondhand: consumer firmware blocks third-party installs until ADB is unlocked by hidden gesture, and there is no self-serve app store.

Access

The developer toolkit is the RayNeo ARDK, offered in two flavors: an OpenXR Unity ARDK (C#/ShaderLab, MIT-licensed on GitHub) and a native Android ARDK.

SDKRayNeo ARDK, in two flavors — OpenXR Unity ARDK and native Android ARDK
LanguagesC#/ShaderLab for the Unity flavor; Android native for the other
ToolchainPer Qualcomm's X3 Pro getting-started guide, the recommended stack is Unity 2022.3.36f1 (2020.3.20 LTS+ supported) with the Android SDK/NDK, OpenJDK, and ADB; you enable OpenXR + the 'RayNeo XR feature group' in Unity's XR Plug-in Management
MaturityEarly — usable and shipping but China-first. The full ARDK is distributed through RayNeo's public, login-free developer manual (with a full English mirror) as dated, versioned downloads covering the native Android ARDK (v0.2.6, April 2026) and the Unity ARDK (1.1.2), plus a RayNeo Open Platform registration portal
Who can buildEffectively open — Qualcomm's guide targets 'AR enthusiasts to professional creators' with no stated invite/partner gate, and the Unity ARDK is public on GitHub
CostNo documented developer fee; tools are free
LicenseThe OpenXR Unity ARDK repo is MIT; the native Android ARDK's license terms are not clearly published
DocsThe Open Platform and Feishu. X3 Pro hardware capabilities are also documented through Qualcomm's Snapdragon developer program

App model

Code runs on the glasses, standalone — the X-series is a self-contained Android device.

What you shipAn ordinary Android APK built in Unity (or native Android) and installed onto the glasses over ADB/USB-C
Manifest requirementThere is no phone-hosted application model — the app's main logic always runs on the glasses, and documented phone-side roles are companion-only (the IPC SDK receives phone-pushed GPS; an official sample offloads RTMP livestream relay to a phone app over Wi-Fi P2P): the AndroidManifest must set the launch activity to com.rayneo.openxradapter.UnityOpenXrActivity so the app is treated as a glasses (OpenXR) app rather than a phone app
Getting a build onOn consumer firmware ADB itself must first be unlocked (see distribution)
The phone's roleA companion 'RayNeo AR' phone app (iOS / Android) exists for pairing/management but is not the app-development target
TransportUSB-C/ADB for development; runtime networking/AI is over the glasses' own Wi-Fi
How many dev systemsEffectively one for XR apps (OpenXR/Android ARDK) with two front-ends (Unity vs. native Android); the X2 additionally documents a WeChat mini-program path via an embedded mini-program framework, a separate non-APK route that carries no XR content and publishes through WeChat's open platform and then RayNeo's

Fit with Extentos's phone-companion model: poor / n/a for the X-series — unlike Meta's DAT (where the app lives on the phone and the glasses are a Bluetooth peripheral), RayNeo X apps execute standalone on the headset, so a phone-hosted-app abstraction doesn't map onto this platform. State this plainly to developers rather than implying parity.

Distribution

An app reaches a device today by sideload: build the APK and adb install it over USB-C.

Where sideloaded apps appearThe on-device 'App Lab' launcher (RayNeo's own name — 'App Lab Features' is a toggle in on-device Settings, and the RayNeo AR phone app exposes a 'Glasses App Center')
The developer gateReal: the consumer ('user version') firmware does not permit third-party installs by default, so you must unlock ADB via a hidden gesture (swiping left ~10 times on Settings › General › About Device, which repeating turns back off), and Windows sideload can require an ADB driver downgrade
A public storeNone self-serve for third-party apps — on Western firmware the on-device menu at launch was dominated by RayNeo's own bundled apps, with no RayNeo-run discovery surface for third-party ones, while China-market X3 Pro units launched with a 'RayNeo AR application virtual machine' carrying a first batch of 30-odd mainstream Android apps (Douyin, Bilibili, Honor of Kings), with an AI Agent store announced but not shipped
The brokered routeRayNeo's X-series dev docs do publish a self-serve submission console followed by a manual, brokered review and listing: register and certify on the Open Platform, upload the APK under "Android 应用管理", email Developer@rayneo.com, then pass RayNeo functional and test-department sign-off before listing
ReviewRayNeo's docs describe an internal functional and listing test rather than a published policy. Preview→GA gating/timeline for a store: not published
Community toolingCovers sideload plumbing: GBox, a compatibility layer that runs the Google Play Store, Chrome, and similar Android apps on the glasses, and TapLink, a community-built XR web browser for the X3 Pro; its bundled "GlassApps Store" is a dashboard view of the community glassapps.io catalog of Meta Ray-Ban Display web apps, which it opens as URLs rather than installing — neither is a RayNeo channel
Not a publishing pathRayNeo's own 'Creator Mode', which unlocks 6DoF SLAM

Public publishing status: not available as a self-serve store push — the documented route is the brokered Open Platform submission above, with everyday delivery still sideload/community-grade.

Capabilities, limits & AI

CapabilityThird-party access
CameraDual — Sony IMX681 RGB (12MP photo / up to 4K video) plus an OV monochrome camera for positioning/SLAM; the ARDK exposes camera and sensor data access, though per-frame gating/permission specifics aren't publicly detailed.
Microphone / audio captureon-board mic array (used for 'Hey RayNeo' and the platform assistant) — and raw third-party capture is documented: per RayNeo's X-series audio docs, an app records with standard Android AudioRecord against the SPEAKER_MIC device and picks a mic-array mode via AudioManager.setParameters("audio_source_record=…") — X3 documents five modes (OFF, RECORD_TRANSLATION, CAMCORDER, VOICE_RECOGNITION, VOICE_COMMUNICATION), and apps must set audio_source_record=off on exit to release the mics.
Audio output / TTSOpen-ear speakers; TTS available through the assistant path.
On-lens display/UIYes — binocular full-color micro-LED waveguide (X3 Pro ~3,500 nits typ., 30° FOV); you render via Unity dual-screen rendering through the OpenXR/RayNeo feature group.
Tracking/sensorsIMU plus SLAM, but at launch AR tracking is 3DoF only — a hands-on review found 3D apps 'couldn't keep a stable position in the world' and that 'you can not build proper AR applications with it' today; 6DoF SLAM is Creator-Mode-gated/aspirational, and eye- and hand-tracking have no ARDK API (RayNeo separately markets on-device 'gesture recognition'). Plane and face detection are exposed.
InputTemple 5-way touchpad, voice, phone-as-air-mouse, and Apple Watch gesture control, shipped via the RayNeo AR app 2.1.0 (23 January 2026).
AI & the assistantThe platform assistant is a reserved, first-party closed surface invoked by the 'Hey RayNeo' wake word — and it is region-split: Western-market firmware runs Google Gemini ('Gemini Live', Gemini 2.5), while China-market devices run Alibaba's Tongyi Qianwen (Qwen) (the V3 was explicitly co-developed with Alibaba). Either way there is no documented third-party hook into the system assistant or the reserved wake word, and a developer cannot assume Gemini everywhere. Bring-your-own-AI is possible but only inside your own ARDK app — call any cloud model from your APK; it does not integrate with the system assistant. On-device AI: the AR1 Gen 1 can run local inference, but the shipping assistant is cloud-based and no on-device third-party AI API is documented.

Roadmap

  • Shipped: X2 (2024, Indiegogo → global); X3 Pro (launched 2025, shipping late 2025 into 2026, US/EU regional stores); the display-less V3 AI glasses (pre-sale Jan 2025). The X3 Pro ARDK is versioned against Unity 2022.3.36f1 and ships through RayNeo's public developer manual; the GitHub package is the X2-era com.unity.xr.rayneo.openxr 1.0.1-r3 (Unity 2020.3, last commit October 2024).
  • Shipped since launch: Apple Watch gesture control ("X3 Pro & Apple Watch Gesture Interaction System 1.0", RayNeo AR app 2.1.0, 23 January 2026); RayNeo notes it depends on OTA availability and compatible models.
  • Announced-but-unshipped / in flight: reliable 6DoF SLAM (3DoF-only at launch, Creator-Mode-gated); broader 'AR app ecosystem'/App Lab expansion; deeper assistant features.
  • Publishing timeline: no self-serve third-party app-store path or dated GA for one — submission runs through the brokered Open Platform review described above, and everyday distribution remains sideload/community-run (TapLink/GBox).
  • Momentum: active — TCL/RayNeo iterates hardware yearly (X2→X3 Pro, plus the V3 line) and courts developers via the Qualcomm Snapdragon program and a public GitHub ARDK, but the software/publishing side is early and China-first, with the consumer app-store surface still thin.

In the landscape

RayNeo (TCL) 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.

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: Wearables Device Access Toolkit (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.