Device Studio Overview

Prox OS is web-first and Runtime-first. The main product surface remains the Web

Position

Prox OS is web-first and Runtime-first. The main product surface remains the Web Studio because the browser is the best early environment for dynamic UI, community Spaces, Studio editing, public links, Cloudflare-first deployment, and AI-assisted collaboration.

Mobile should not become a full replacement for the Web OS shell. It should be a companion layer for capture, review, AI interaction, notifications, dynamic view preview, lightweight control, and continue-on-desktop.

Recommended Sequence

Stage	Goal	Why this stage comes first
Responsive mobile web	Make core public, Studio, and companion surfaces readable and usable on phones.	It improves the existing Web Studio without creating a separate runtime.
Mobile Launchpad PWA	Provide a homescreen-friendly pocket entry for recent Studios, AI, capture, notifications, and approvals.	It validates frequency before store review, native permissions, or app distribution.
Declarative Studio View JSON renderer	Render trusted mobile cards, feeds, summaries, forms, and approval blocks from contract data.	It lets mobile show dynamic work without executing user-provided code.
Studio Gallery / Templates	Let users discover verified views, templates, and Studio previews.	It supports reuse while avoiding early marketplace obligations.
Expo-based native companion app	Add native capabilities only when validated by PWA usage and permission needs.	It keeps native scope focused on camera, share, push, files, and secure local affordances.

Surface Differences

Surface	Primary role	Good at	Not good at
Web Studio	Full creation, editing, app composition, community Spaces, publishing, and AI collaboration.	Dynamic UI, complex layout, public links, Cloudflare deployment, app registry experiments.	Quick mobile capture and notification-driven workflows.
Mobile Web / PWA	Early mobile access and validation channel.	Low-friction entry, shareable URLs, responsive previews, installable Launchpad, fast iteration.	Deep native integrations and app-store discovery.
Native Companion App	Future native shell around Device Studio capabilities.	Camera, photos, push, share extension, files, contacts, background upload, deep links, biometrics.	Becoming the full Prox OS runtime or an unreviewed app marketplace.
Future Mini Experiences / Gallery	Governed discovery of verified views, templates, and constrained interactive experiences.	Reuse, remix, public templates, official blocks, curated mobile experiences.	Arbitrary third-party code execution before governance exists.

Why Not A Fully Dynamic Mobile Platform Now

Launching a fully dynamic mobile app platform too early creates product, engineering, and policy risk:

It can confuse Device Studio with an app marketplace.
It can imply third-party executable code inside a native app before review, metadata, permissions, moderation, and takedown workflows exist.
It can expose native APIs to experiences that were designed for web sandbox assumptions.
It can split attention away from the Web Studio, where Prox OS has the best current leverage.
It can force App Store / Google Play policy obligations before the product has validated high-frequency mobile demand.

Device Studio Non-goals

Do not clone the full desktop OS shell on a phone.
Do not launch a native app as the main platform before mobile web and PWA usage are validated.
Do not execute arbitrary remote JavaScript or React bundles in a future native companion app.
Do not call early mobile discovery an App Store.
Do not expose native capabilities directly to user-generated mini experiences.
Do not promise App Store or Google Play approval.

Product Thesis

Device Studio should answer:

What can the user do in five seconds while away from the desktop?

The early answer is:

open Launchpad;
ask AI;
capture a note, image, link, or voice memo;
preview a Studio card;
approve or reject an AI-generated suggestion;
continue on desktop.