03 · Multimodal AI
Smart Glasses Field Assistant
The people doing the work had their hands full — literally. Asking a question meant putting something down, finding a device, typing, and losing the thread. The requirement was simple to state and hard to build: look at something, ask about it out loud, get a spoken answer in a second or two, touch nothing.
- Client
- An applied research group working in a lab environment
- Sector
- R&D / Wearable Computing
- Engagement
- Hardware-to-cloud prototype
- Year
- 2026
3
Surfaces: glasses, phone, desk
On-device
Wake word — never always-streaming
1–2 sent.
Spoken answer budget
Local
Face recognition, no cloud enrollment
Three devices, one session
A SwiftUI iOS application captures camera and microphone from glasses-mounted hardware and streams it to a Python backend over WebSockets, with a media server handling the video transport. A companion desktop client handles system audio, and a desk-mounted camera provides a second fixed viewpoint.
Every one of those inputs feeds a single conversational session with shared memory. The assistant does not care which camera saw the thing you are asking about.
Latency is the whole product
A wearable assistant that takes five seconds to answer is a wearable assistant nobody wears. The budget runs capture → relay → model → speech, and every hop had to be defended.
Frames are encoded and relayed rather than round-tripped through disk. The model runs as a live streaming session instead of discrete request/response calls, so audio and video flow continuously and the reply begins before the question is fully processed. The system prompt caps answers at one or two sentences unless more is explicitly asked for, because a spoken paragraph is a latency cost the wearer pays in full.
Privacy by construction
Always-on cameras and microphones are a trust problem before they are a technical one. Activation runs through an on-device wake-word model, so the stream opens on intent rather than running continuously into the cloud.
Face recognition is enrolled from a local directory of known faces and matched on the machine. The assistant can tell the wearer who walked in without anyone’s face being uploaded to a third-party identity service.
A control surface for the operator
The backend serves a small web console for monitoring live feeds, checking session state, and configuring which inputs are active. Prototypes get abandoned when nobody can see what they are doing; this one is observable from a browser tab.
A working end-to-end wearable assistant: glasses to phone to backend to multimodal model to spoken reply, with wake-word activation and local face identification.
The architecture is device-agnostic. The iOS client is one producer among several, so new capture hardware attaches without touching the reasoning layer.
Built with
Next case study
Offline-First Study Platform
An 8,000-entry classical dictionary turned into a study product — web and native, shipped, and fast offline.