VModal for Smart Glasses

Turn a first-person view into a live, reliable video experience.

Capture on the glasses. Encode on Android. Stream securely to your ingest.
Keep your product focused on the experience—not the media plumbing.

Build for the point of view no phone camera can reach.

Start here

[!NOTE] This SDK streams live camera video from Android smart glasses. For video upload, indexing, and multimodal search, use the VModal Android SDK instead.

Make presence feel immediate

VModal combines an Android-native Kotlin client with a high-throughput Rust media core. Your app owns the product experience; the SDK owns the demanding path between a wearable camera and your live ingest service.

A clean path from glasses to ingest

flowchart LR
    G[Smart glasses] --> D[Meta DAT]
    D --> K[Android H.264]
    K --> R[Rust media core]
    R --> S[Encrypted SRT]
    S --> I[Live ingest]

    A[Your Android app] --> C[SmartGlassClient]
    B[Authenticated backend] --> T[Short-lived target]
    T --> C
    C --> K
    C --> R

The separation is deliberate:

• Kotlin client manages the public API, Meta DAT integration, capture, MediaCodec, coroutine state, events, and lifecycle.
• Rust core manages bounded encoded-media queues, H.264 normalization, MPEG-TS muxing, SRT transport, reconnects, and transport metrics.
• Your app owns screens, permissions, Meta registration, foreground-service policy, authentication, and stream controls.
• Your backend validates the user and returns a short-lived ingest target, keeping account-level provider credentials away from the device.

The Activity never needs to understand a JNI handle, SRT socket, or encoded GOP. The backend never needs to manage an Android camera session.

Build with the SDK

The implementation guide keeps the Kotlin and command-line setup in one place:

Open the Smart Glass SDK quickstart →

It covers prerequisites, local builds, SmartGlassClient creation, short-lived stream targets, state and metrics collection, and deterministic cleanup.

Engineered for wearable constraints

Bounded latency, not unbounded memory

GOP-aware backpressure and bounded queues keep a weak network from turning into ever-growing latency. The SDK can signal the Kotlin layer to drop safely or request a new keyframe when transport falls behind.

Recovery without a broken experience

SRT reconnects use configurable delays, jitter, and timeouts. When a target is expired or rejected, LiveStreamTargetProvider can fetch a fresh destination while the app continues to present one coherent stream lifecycle.

Native internals behind a Kotlin boundary

The public API does not expose Meta DAT types or Rust handles. Your host app owns the camera permission and registration experience; the SDK owns its one capture session only while streaming.

Metrics your support team can use

client.metrics exposes connection health, queue pressure, and transport behavior for a developer panel, field diagnostic screen, or support workflow.

Production integration checklist

• Android API 31+, JDK 17, and Android compile SDK 36.
• A compatible Meta smart-glasses registration and Meta Wearables DAT setup.
• A user-facing camera permission and Meta registration flow in the host app.
• A foreground service when streaming may continue outside the foreground.
• An authenticated backend endpoint that returns a fresh LiveStreamTarget.
• Exactly one SmartGlassClient for each active capture owner.
• No competing camera session while SmartGlassClient is streaming.

The project provides two build flavors:

Keep credentials on the right side of the boundary

The app may briefly receive the SRT fields required to contribute live video. It should never contain account-level Cloudflare or live-platform credentials. After validating the app user, have your backend mint or lease a short-lived target; do not log or persist its stream ID or passphrase.

Explore the SDK

• SDK quickstart — build commands, Kotlin integration, lifecycle, and cleanup.
• Android simulator — install an Android 14 AVD and exercise the Meta Mock Device Kit without physical glasses.
• VModal — the VModal platform.
• VModal for developers — APIs, SDKs, and integration resources.