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. Nothing is installed
anywhere; it is for building and checking, not for sharing.
1. Dev install (you, iterating)
While you’re building,glassly dev serves
your project over the LAN with hot reload. Scan the QR from the Glassly App and
your changes reload on save. This is the inner loop; see the
Quickstart.
Dev mode is not an installation: the computer and CLI must remain running to
serve each miniapp’s runtime bundle. The Glassly App keeps a separate dev entry
for each manifest package name and caches its name and icon, so you can scan and
test multiple dev miniapps together. Rescanning the same package updates that
entry. Use a release install when you want the miniapp to run without the
computer.
2. Release install (sharing a build over LAN)
To put a real, installed build on one or more phones without going through the Glassly Miniapp Store, run:miniapp://release QR. Anyone
on the same network can scan it to install. The miniapp installs on the device,
runs offline, and persists across restarts: no laptop required once it’s
installed. Great for testers, demos, and dogfooding.
Each install is logged in your terminal, and the server stays up so multiple
devices can install from the same QR.
3. Share the file
To hand a build to someone who is not on your network, pack it and send the file:build/<packageName>-<version>.gls, a zip under the Glassly
miniapp extension. Send it any way you like: AirDrop, chat, email, a shared
drive. On the receiving phone, save the file, then choose it from Settings ›
Miniapp Developer › Install Miniapp from File. The app opens a Store-style
page for it (icon, description, version, permissions and glasses hardware)
with an Install button. Like a release
install, it runs offline and persists across restarts.
A file installed this way is tagged “Installed from a file” on its settings
page. It is never auto-updated by the Store, though the Store still offers an
update when it has a newer version of the same package. Users are told the
file did not come through the Store, so share builds only with people who
know you.
4. Store submission (reaching everyone)
To reach users who aren’t on your network, publish to the Glassly Miniapp Store. Sign in to the Developer Console once to create your developer org. The org owns a package prefix such ascom.example, and
every miniapp you publish must have a packageName under it (the scaffolder
asks for the prefix so a new project starts out right). Then, from the miniapp
folder:
glassly login prints a one-time console.glassly.ai/device link and code, and opens Glassly’s sign-in
page so you can approve this machine. Your org, package prefix, releases, and
API keys live in the Developer Console. For CI or
an AI coding agent that can’t open a browser, an org owner or admin can create
an API key on the console’s API keys page
and export it as CLI_TOKEN.
publish reserves the package name for your org on first use and submits the
release for review; the console shows its status. Make sure your
miniapp.json is accurate before
you publish: its hardwareRequirements decide which glasses can see your
miniapp, its permissions drive the OS prompts users see, and its tagline and
tags are the copy on your store card. If you only want the artifact,
glassly pack writes the same build/<packageName>-<version>.zip without
uploading it.
Once a release is published, the listing shows in the Glassly Miniapp Store
inside the Glassly App and on the web at
store.glassly.ai, at
https://store.glassly.ai/<packageName>. The web Store is browse-only: it
shows the same card and detail page and sends visitors to get the Glassly App
to install.
Store listing media
The store icon is theicon.png from your bundle. To ship screenshots with a
release, add a store/ folder next to miniapp.json:
glassly publish uploads the folder with the release. After a release is
published, the Developer Console’s miniapp page lets you replace the icon,
add or reorder screenshots, and override the tagline, description, and tags
without shipping a new version.
Camera, photo, and live-streaming features run through the on-glasses Bluetooth
stack, not a cloud server. See the Bluetooth SDK docs
for those workflows.
Versioning
Bumpversion in miniapp.json for every release you distribute. The CLI names
the artifact <packageName>-<version>.zip, and installed miniapps are stored per
version (lmas/<package>/<version>/), so a new version installs cleanly alongside
or over the old one.
Next steps
CLI reference
dev, release, pack, and publish in detail.The manifest
Get permissions and hardware requirements right before you ship.

