Capabilities
Quickly check where each platform capability runs, its SDK entry point, permissions, and prerequisites.
Platform capabilities at a glance#
| Capability category | Runtime and entry point | Permissions or prerequisites |
|---|---|---|
| Display and UI | Glasses C Host / LVGL; phone Web gm.display. | C: check Host capabilities and the function table. Web: declare display. |
| Buttons, sensors, and device state | Glasses C callbacks and device APIs; phone Web gm.device events and information. | Check support on the target device. Web: declare device.info / device.events. |
| Phone–glasses messages | Phone Web and glasses GMP exchange custom messages through the Bridge. | Declare device.messaging and the send/receive channels. Keep the App connected to the glasses. |
| Storage and user files | Phone Web gm.storage / gm.files. | Declare storage / files.user-selected. Data follows account and installation ownership. |
| Audio | Phone Web capture, short recordings, and standard media playback. | Declare audio.capture / audio.playback. Availability depends on host authorization and resource state. |
| Foreground location | Phone Web gm.location. | Declare location.foreground, obtain system location permission, and keep the application in the foreground. |
| Networking and your own AI service | Phone Web uses fetch or similar APIs to call the developer's own services. | Declare network. Handle CORS, authentication, timeouts, and keys on the server. |
| HOGP peripherals | Compatible peripherals connect to the glasses through BLE HOGP and map their input. | Check device compatibility, pairing state, and inputmap. This does not depend on Studio's LAN connection. |