Input
Camera images, microphone audio, app commands or a video source. Only models with the corresponding hardware can provide that input.
SDK & integration
Define the hardware and app together
Camera and audio glasses use separate SDKs. We review supported functions, phone compatibility and software responsibilities for the model you plan to build.
From input to AI response
Connection
Bluetooth/BLE, Wi-Fi or USB-C video, depending on the model. Specify pairing, transfer, latency and power requirements.
Processing
Separate device firmware, phone-app logic and backend AI. Agree which functions operate offline and which require network/service access.
Output
Open-ear audio, monochrome waveguide text or a full-colour cinema screen. Display type determines what information is practical to present.
A chipset name, camera sensor or display does not prove standalone AI, local large-model inference, real-time streaming, SLAM or spatial tracking. These require an agreed architecture and working evidence for the selected configuration.
Camera and audio SDK scopes
Camera glasses / Scout
A camera-line reference App SDK can support project evaluation. The specific model, SDK package, operating-system support and available interfaces must be reviewed before development.
Your brief should cover pairing, camera controls, media transfer, storage, permissions, AI services and update responsibilities. These are review topics, not a promise that every interface is provided.
Explore Scout One →Audio glasses / Verse
The audio line has a separate SDK and development schedule. Availability and mobile App SDK function coverage are confirmed for the selected Verse model; camera SDK support does not establish audio-line support.
Phone music and calls, controls, supported voice-assistant access and optional app requirements should be evaluated on the intended sample configuration.
Explore Verse Pro →AR and cinema need different integration plans
Waveguide AR / Cue
Cue One and Cue Air display app information without a built-in camera. Cue Pro adds camera input in a scoped project. Review display transport, text layout, notification access, phone location, voice input, AI request/response and update responsibilities. Confirm SDK/API availability; the Camera or Audio SDK is not automatically compatible.
Review AR models →Personal cinema / Cinema One
The core path is source-device video to the glasses display. Confirm USB-C DisplayPort output, power and adapters first. AI applications belong to the connected source or optional companion setup; wireless casting and 3DOF need their applicable accessories. A cinema screen alone does not provide camera capture or tracked AR overlays.
Review Cinema One compatibility →What each team needs before launch
Product management
Define the user task, required input/output, offline needs, supported languages and measurable acceptance criteria.
Engineering
Confirm firmware/App/backend boundaries, SDK interfaces, permissions, data transfer, service credentials, updates and sample test coverage.
Sales
Use the exact model and configuration in quotations. Confirm sample readiness, MOQ, accessories and delivery commitments.
Marketing
Describe hardware and app-supported features separately. Use model-specific media, version-qualified claims and confirmed certification scope.
Business owners
Review sample and production costs, NRE/tooling, AI service fees, licences, IP deliverables, target markets and after-sales ownership.
Custom offline wake words
Custom offline wake words can be developed for supported configurations. The wake phrase, languages and commands are defined per project and verified on the target hardware. This capability is not a standard feature on every Verse model.
Supported phone multimedia and call actions can be included in the project scope. An offline wake word does not mean that translation, cloud AI or every assistant function operates offline. Confirm the full device, phone and service workflow.
Firmware is generally delivered as a customised product implementation. App SDK access does not imply delivery of device firmware source code. Engineering fees, tooling, licences, IP and deliverables are agreed in the project contract.
What to send for an integration review
1
Choose the model
Camera, audio or display; target sample and required hardware functions.
2
Describe the phone workflow
Target iOS/Android versions, pairing, controls, transfers and app permissions.
3
Define the AI service
Your backend or model, network requirements, supported languages and data responsibilities.
4
List custom interactions
Wake phrase, commands, touch controls and expected behaviour during music or calls.
5
Agree development responsibilities
App, firmware, SDK maintenance, updates, engineering fees and IP deliverables.
6
Verify on a sample
Document app/firmware versions and repeat the required workflows before production.
Bring your app requirements.
Share the model, target phones, essential functions and estimated volume. We will scope a feasible integration and sample evaluation.