ProductClientsDevice Studio
Device Studio
Device Studio is the future mobile companion direction for Prox OS. It is not
Device Studio is the future mobile companion direction for Prox OS. It is not a replacement for the Web OS shell and it is not a promise to ship a native mobile app now.
Device Studio should make the Prox OS platform useful in high-frequency mobile moments: capture, review, AI interaction, notification triage, lightweight approval, dynamic view preview, and continue-on-desktop.
Document Map
- Overview: product and sequencing overview.
- Mobile Launchpad: early pocket-entry product shape.
- PWA Positioning: why mobile web and PWA come before a native app.
- Native Companion Expo Boundary: proposed future Expo decision and non-goals.
- Studio View JSON: declarative dynamic UI contract draft for mobile rendering.
- Gallery And Mini Experiences: naming boundary for Launchpad, templates, verified views, and future mini experiences.
- Policy Boundaries: App Store / Google Play policy risk notes and future governance requirements.
Core Position
| Principle | Meaning |
|---|---|
| Web-first | The Web Studio remains the primary creation, editing, publishing, and public-link surface. |
| Runtime-first | Mobile works with Studios, Views, Sources, Connectors, AI Context, and permissions rather than becoming a separate app universe. |
| Companion layer | Mobile prioritizes fast capture, review, notification, preview, AI, and approval loops. |
| Declarative dynamic UI | Mobile dynamic views should render trusted data-driven blocks, not arbitrary uploaded code. |
| Native later | Expo or React Native becomes useful only after PWA usage and native-capability needs are validated. |