HTC VIVE Eagle

Covered here: VIVE Eagle (HTC's AI smart glasses) and the VIVE AI Glasses SDK for iOS and Android.

Not covered here: VIVE XR Elite, the VIVE Focus series and VIVE Flow (VR/MR headsets on the VIVE Wave / OpenXR stack) · VIVERSE (HTC's web metaverse platform, not a wearable).

Overview

HTC's VIVE Eagle is a displayless pair of AI smart glasses: a 12MP ultra-wide camera with AI auto-correction, a four-mic beamforming array, and bass-enhanced open-ear speakers on a Qualcomm Snapdragon AR1 Gen 1 with 4 GB RAM and 32 GB storage, driven by a phone (spec sheet). There is no display and no HUD — HTC's own structured data for the product says so outright, describing the lenses as "鏡片為一般鏡片，無 AR 或 HUD 顯示" (ordinary lenses, no AR or HUD display) (VIVE Eagle, Taiwan). Everything the device tells the wearer, it says out loud. Video is capped at ten minutes per clip in a vertical, social-native format, and two privacy behaviours are enforced in hardware: camera functions auto-disable when the glasses are not worn or when the capture LED is covered. A smartphone is mandatory (iOS 17.6+ or Android 10+), along with an HTC account and the VIVE Connect companion app, with use gated at 13+.

Regional availability is the sharpest thing to get right about this platform, because HTC's own pages disagree with each other. Eagle is buyable now in at least four markets, each publishing its own price: Taiwan from TWD$15,600 (TWD$19,888 for the limited photochromic UV lens), with a first-party configurator and structured data marking it InStock (Taiwan); Hong Kong at HK$3,988 (Hong Kong); Singapore from S$730 (S$880 for AdaptiveSun lenses) (Singapore); and Japan from 税込82,500円 (98,000円 for the photochromic lens) (Japan). HTC's newsroom dates each expansion — Hong Kong 11 Dec 2025, Singapore 9 Mar 2026, Japan 22 Apr 2026 (newsroom). Meanwhile vive.com/us, /uk, /de, /eu and /fr still state "VIVE Eagle is currently only available in Taiwan" — a claim HTC's own newsroom and its Asian storefronts have overtaken. Those pages are stale marketing surfaces, not evidence of unavailability; they are also why no US-dollar price for Eagle should be trusted, since no US purchase path exists at all. The device is not sold in the US, UK or EU. The openness verdict then splits along the build/ship line: the SDK, its full API reference and a working simulator are free to anyone on earth, while running on real hardware means importing from one of four Asian markets and getting your app registered by HTC through a route HTC does not document.

What you can buy

Cheapest way to run your own code: The VIVE AI Glasses SDK 0.6.0 beta downloads free for Android or iOS with no sign-in and no hardware, and runs against a documented simulator, though your app must be a debug version. Real glasses cost far more — Taiwan from TWD$15,600, Hong Kong HK$3,988, Singapore from S$730, Japan from 税込82,500円 — and the app must also be registered with HTC, by a route HTC does not document publicly, before it can talk to the device at all.

What the listings leave out

Access

The VIVE AI Glasses SDK covers Android (Kotlin/Java) and iOS (Swift) from a single documented API surface, and it is not gated.

The real access wall sits one step later, at runtime. The Android setup page opens with "Step 1: Register the application — You must register your app to enable communication between the software and hardware" (Android setup), and the SDK enforces it as UnregisteredAppException, "thrown when the app has not yet been officially registered" (exceptions). HTC documents no way to become registered — no form, portal, email or contact route appears in the developer resources, in either shipped archive, or in any public repository. Anyone may build and simulate; who may ship against hardware is decided off-document.

App model

Code runs on the phone, not on the glasses. There is no documented way to deploy an application, applet or web view to the device; Eagle is a peripheral and the developer's own iOS or Android app is the application. The root object is ViveGlass, which "provides a unified interface for managing connections and interactions with VIVE AI Glasses" across four documented jobs — device connection, voice interaction (TTS/STT), audio input, and image input (ViveGlass reference). On Android you instantiate ViveGlass, assign a ViveGlassKit as the adapter, and call connect() with a ViveGlassClientCallback receiving onConnectionStateChanged, onImageCaptured, onSpeechTranscribed, onTextSpoken and onKeyEvent.

What HTC does provide is a first-party simulator, which matters given the hardware sells only in Asia. You import com.htc.viveglass.sdk.simulator.ViveGlassSimulator, call create(appContext), set it as the ViveGlass.adapter in place of the real kit, and call showUI(supportFragmentManager). Sample media is swapped by pushing files into the app's files directory with Device Explorer at documented specs — HEIC 1440×1920 for stills, MP4 480×856 30 FPS with AAC 44.1 kHz 32 kbps stereo audio — and the page is explicit that "Your app must be a debug version" (simulator setup). The iOS simulator works differently: it borrows the iPhone's own microphone and Speech framework to stand in for the glasses rather than replaying files.

Distribution

An Eagle app is an ordinary phone app, so it reaches users through the App Store and Google Play like any other — there is no HTC store, no Eagle storefront and no on-device catalogue, because there is no on-device runtime to host one. HTC's own developer programme confirmed the shape by asking finalists for exactly what a normal mobile release requires: an Android APK, an iOS TestFlight build, a connected software backend, and store presentation assets including icon and UI screenshots (2026 VIVE Eagle developer programme). Content review is therefore Apple's and Google's; HTC documents no review or certification process of its own for third-party Eagle apps.

The gating that does exist is upstream of publishing. Your app must be officially registered with HTC before it can communicate with the glasses at all, enforced both as UnregisteredAppException and — importantly for anyone building a connection flow — as a connection state, ConnectionState.ERROR_UNREGISTER_APP, which HTC's own bundled sample handles alongside ConnectionState.ERROR_UNSUPPORTED_ROM_VERSION. An unregistered app does not crash; it silently fails to connect. Publishing one to a store is possible but pointless.

Because HTC publishes no self-serve registration route, the only documented path to registered status ran through its developer programme — and that programme was geographically restricted and has now ended. Entrants had to be ROC (Taiwan) nationals, foreign nationals holding valid Taiwan residency and actually resident there, or organisations legally registered in Taiwan. Its published schedule ran proposals 8 Jan – 9 Feb 2026, 15 teams selected 12 Feb (each receiving a pair of glasses), POC submissions 9 Mar – 19 Apr, 10 teams advancing 22 Apr, commercial development 30 Apr – 14 Jul, live demos 15–16 July, and four winners announced 22 July 2026 at NT$100,000 each. The second round was defined as teams who passed screening and "取得 HTC VIVE Eagle AI SDK" — HTC treating hardware-capable SDK entitlement as something it grants, even though the archives download publicly. Selected teams were also bound by a confidentiality and non-compete clause covering the SDK and technical documentation, a notable contrast with binaries that download with no NDA at all. No successor programme or replacement registration route is currently published. For a developer outside Taiwan the practical position today is: build and simulate freely, ship to a real wearer only by arrangement with HTC. The public third-party footprint reflects that — a GitHub search for viveglass or "vive eagle" returns two repositories in total, both with zero stars.

Capabilities, limits & AI

Roadmap

3 July 2026: SDK 0.6.0 shipped, adding advanced video streaming configurations — the sixth release in four months, after 0.1.0 (6 Mar), 0.2.0 (30 Mar), 0.5.0 (1 Jun), 0.5.1 (5 Jun) and 0.5.2 (9 Jun), all beta-labelled and pre-1.0 (archive). That cadence, and the steady growth of the video API, mark active development rather than a parked SDK.

8 January to 22 July 2026: HTC ran the 2026 VIVE Eagle AI Glasses Developer Programme with published dates — proposals 8 Jan – 9 Feb, 15 teams selected 12 Feb (each receiving hardware), POC submissions 9 Mar – 19 Apr, 10 teams advancing 22 Apr, commercial development 30 Apr – 14 Jul, live demos online 15 July and at HTC headquarters 16 July, and four winners announced 22 July 2026 at NT$100,000 each (programme page). That cycle closed days before this writing. HTC has not announced a successor, and whether it reopens is the single most useful signal to watch, because it is the only documented route to a registered app.

Market expansion is the live storyline. HTC's newsroom dates a steady march outward from Taiwan — Hong Kong 11 Dec 2025, Singapore with Singtel 9 Mar 2026, Japan 22 Apr 2026 (alongside a Red Dot award) — plus recurring feature drops: AI continuous-conversation mode (13 Nov 2025), Cantonese support (9 Mar 2026) and VIVE AI Notes with 12-language transcripts and summaries (31 Mar 2026) (newsroom). The programme materials also dangled international promotion for selected teams "搭配HTC海外上市計畫" (in step with HTC's overseas launch plan), pointing at further expansion. But no Western market, date or price has been announced, and HTC's US, UK, German, EU and French pages have not been updated since the Asian launches — they still assert Taiwan-only availability, which is now inaccurate rather than informative. Treat US/UK/EU availability as unannounced.

Also outstanding: a 1.0 SDK, any published licence terms, a remote dependency-manager distribution, a documented minSdk and ROM-version compatibility matrix, and a self-serve app-registration route.

In the landscape

HTC VIVE Eagle 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