Mobile AI-first Remote OS

Summary

Desktop Prox OS uses:

OS Workspace + Alma

Mobile Prox OS should use:

Alma first + Remote OS control + Notifications + Workspace preview

This document is the roadmap note for mobile control and AI-first workflows. The more detailed product, PWA, native companion, dynamic UI, gallery naming, and policy boundaries live in Device Studio.

This direction does not build a native mobile app.

Mobile Product Shape

Future mobile tabs can include:

• Today
• AI
• Workspaces
• Inbox / Approvals
• Connectors / Permissions
• Profile / Data Vault

Mobile should prioritize:

• approvals
• workflow review
• workspace restore
• artifact preview
• AI action logs
• permission review
• remote workspace control

Native Path

1. PWA and responsive web first.
2. Mobile Launchpad PWA after high-frequency mobile flows are validated.
3. Declarative Studio View JSON renderer for mobile dynamic views.
4. Expo-based native companion only if capture, push notifications, share extension, files, camera, or secure local affordances become necessary.

Native app is not a current implementation target. It should remain a companion shell around Device Studio capabilities, not the full Prox OS runtime.

Safety

Mobile high-impact actions should be stricter, not looser. Publish, share, deploy, and external write actions should require explicit confirmation and audit.

Dynamic mobile UI must be declarative and contract-driven. Mobile should render trusted Studio View JSON blocks instead of arbitrary remote JavaScript or React bundles.