Skip to content

Architecture

Overview

Maverick AI is wirelessly tethered to your smartphone via Bluetooth.

The Maverick AI SDK runs as a part of your mobile application, as simple as that.

There's no need to develop a separate app or adapt to a new development environment. Simply add the Maverick AI SDK to your application, and use it to display your existing app data on the glasses.

The SDK handles all aspects of the interaction with the glasses - from Bluetooth communication to rendering commands and receiving sensor data - and exposes a modern, intuitive API for you to build Maverick AI-enabled applications.

System Overview

%%{init: {"flowchart": {"nodeSpacing": 38, "rankSpacing": 44, "padding": 12, "htmlLabels": true}}}%%
flowchart TB
    subgraph App["Your mobile app"]
        subgraph SDK["Maverick AI SDK"]
            GS["Glasses<br/>service"]
            SS["Screen<br/>service"]
            DS["Display<br/>service"]
            CM["Camera · Mic<br/>Sensors · Eye tracker"]
            RS["Resources<br/>service"]
            OL["OTA · Logger<br/>Preferences"]
            %% invisible links only pin the boxes into a 3 x 2 grid
            GS ~~~ CM
            SS ~~~ RS
            DS ~~~ OL
        end
    end

    subgraph Glasses["Maverick AI glasses"]
        OS["Embedded OS · render engine — ~67 Hz"]
        HW["IMU · Camera · Mic<br/>Display · Touch"]
        OS ~~~ HW
    end

    SDK -- "BLE 4.2+<br/>BLE 5 recommended" --> Glasses

On-Device Rendering

Unlike traditional phone-rendered HUDs, Maverick AI uses an on-device rendering model:

  • Draw objects and their parameters (position, size, color, resources) are sent from the SDK to the glasses once as definitions.
  • The glasses' embedded OS continuously renders frames on-device at ~67 Hz without further phone involvement.
  • The client only sends lightweight incremental updates: object property changes, animator start/stop commands, camera/mic/LOS toggles.

This architecture dramatically reduces Bluetooth bandwidth usage and enables high-quality, high-precision Line of Sight tracking and rendering, since the on-board render loop is decoupled from BLE latency.

Data Flow

sequenceDiagram
    participant P as Phone (SDK)
    participant G as Glasses (Firmware)
    P->>G: 1. Connect (BLE handshake)
    P->>G: 2. Object definitions<br/>(text, shapes, images, resources)
    Note right of G: Create on-device scene graph
    Note right of G: 3. Render at ~67 Hz<br/>(continuous, autonomous)
    P->>G: 4. Property deltas<br/>(position, color, text, etc.)
    Note right of G: Apply changes
    G->>P: 5. Events<br/>(quaternions, camera, mic, touch)
    Note right of G: Sensor data, LOS quaternions,<br/>camera frames, touch events

Key insight: After the initial setup, the phone only sends small deltas when properties change. The glasses handle all rendering independently, making the system resilient to BLE latency and bandwidth constraints.

See Also