ProductClients
Clients
Client documentation describes how Prox OS can reach users across browser,
Client documentation describes how Prox OS can reach users across browser, PWA, native companion, extension, desktop-client, and future OS-level surfaces.
The current implementation remains web-first. v0.1 should stay Web/PWA-first;
a native or local companion appears later only when real local LLM, local data,
automation, notification, or local MCP gateway use cases justify the added
security and support burden. Client documents are planning and boundary
references unless they explicitly point to shipped source code.
Start Here
- Device Studio: mobile web, PWA, future native companion, dynamic Studio View JSON, gallery naming, and policy boundaries.
- Client And OS-Level Roadmap: long-term PWA, browser extension, desktop client, local runtime, local LLM, local data vault, local automation, local MCP gateway, and OS-level distribution sequencing.
- Mobile-Friendly Web OS: baseline posture for keeping public, Studio, and community surfaces usable on phones.
Client Maturity
| Client surface | Current posture | Implementation status |
|---|---|---|
| Browser Shell | Primary Prox OS surface for Web Studio, OS Shell, apps, docs, and public routes. | Current |
| Responsive Mobile Web | Required baseline for public, Studio, and companion entry surfaces. | Partial / ongoing |
| Mobile Launchpad PWA | Candidate high-frequency mobile entry for capture, review, notifications, AI, and continue-on-desktop. | Planned |
| Native Companion App | Future Expo-based companion only after mobile-native capabilities are validated. | Future |
| Desktop Client | Future system-level helper for tray, global shortcuts, link capture, and local indexing. | Future |
| Local Companion | Future optional helper for local LLM adapters, local vault, file/browser automation, notifications, and scoped local MCP gateway. | Future |
| OS-Level Distribution | Long-term appliance or OS distribution imagination. | Long-term vision |