Clients
Pages in this section of the Maia OS documentation.
In this section
- Desktop and mobile clients
Status: implemented as an unqualified source candidate: Tauri Desktop hosts the shared Expo renderer as routed pages… This document owns the client platform, authority boundaries, live data path,…
- Maia Desktop and mobile UI
Status: user-approved target, not implemented. The full Desktop app section below is the planned complete Desktop.
- Mobile connection and pairing proposal
Status: proposal, not implemented. The Node API is an authenticated HTTP/WebSocket server bound to 127.0.0.1.
- Portfolio voice contract
Moved from the roadmap. Status: Planned.
- Presentation runtime
Status: implemented as an operator-local source candidate: four read-only operations (presentation.catalog.show,… This is the R9a specification. Reasons for json-render and Jev: decision.
- Workspace hierarchy delivery
Status: Source candidate, verified in code. container.list, container.show, container.index.list, container.create.preview, container.create.confirm, container.rename.preview and…
Imported from Maia OS docs at a2175bb