Glassly Miniapp SDK betaThe SDK is in beta, so its APIs may change before general availability.Developing on Mentra Live? We recommend using the
Glassly Bluetooth SDK.The developer tools are available in the Glassly App under Settings →
Miniapp Developer Settings.Share feedback with an in-app bug report, on
Discord, or by email at
[email protected].
glassly sim runs your miniapp on macOS, Linux, or Windows. The background
script runs in a worker, the glasses display is drawn in a browser window, and
the phone page loads in a phone frame beside it. Every input the glasses and
phone would produce can be sent from that window or from the command line, so a
script or a coding agent can change code, act, and check the result without a
person in the loop.
miniapp.json, builds both layers, opens the simulator window, and
rebuilds and reloads when you save a source file. Console output from both
layers prints in the terminal and in the window’s log.
The window
- Glasses: the display, drawn by the same scene pipeline the Glassly App runs (clamping, element budgets, text wrapping, transitions). It simulates the app’s Simulated Glasses, a 576×288 canvas with 16 gray levels that previews what Glassly CFW glasses can show.
- Controls: the touch bar (tap A and tap B, double tap, hold, swipes), look up and
down, speech the glasses hear (typed, delivered as a transcription), phone
notifications, battery, location, and connecting or disconnecting the
glasses. Tap A and tap B are single taps with
index0 and 1, the two fingers a Neural Band tells apart (glassly sim tap/glassly sim tap --b). Button presses come fromglassly sim button. - Phone: your UI page with the same
glasslybridge, safe-area insets and capsule menu it gets inside the Glassly App. Switch it to a folded iPhone Duo (or runglassly sim phone duo) to check the page against the 84 pt status rail on the right, with the capsule and anyuseRailBackButtonback button drawn in the rail. The same page is at/ui/on the simulator’s address if you want it in its own tab. - Log, Scene, State: console output, the elements on the display, and what the miniapp is subscribed to.
Drive it from the terminal
While a simulator is running,glassly sim <command> from the project folder
talks to it:
screen prints the processed frame, which is usually the quickest check:
ui send and ui request act as the phone page, so background logic that
answers the page can be exercised without a browser. To drive the real page, open
http://localhost:<port>/ui/ in any browser or browser automation tool.
The full list is in the CLI reference.
What is simulated
Camera, microphone audio, streaming, navigation,
session.ai, session.auth,
session.blob, session.memory, and miniapp-to-miniapp calls are not simulated.
A call to one of them fails with NOT_IMPLEMENTED, and the simulator names it in
the log and under State. Test those on a phone with glassly dev.
The simulator is a preview, not the hardware. Text is drawn with your
computer’s sans-serif face at the device’s glyph advances, so line breaks match
and letter shapes do not. Timing, brightness, and Bluetooth throughput are not
modelled. Check on glasses before you ship.
Next steps
Quickstart
Run the same project on a phone and glasses.
AI IDE integration
Tell your coding agent how to use the simulator.

