PWA Positioning

Decision Direction

Prox OS should validate mobile through responsive web and PWA before starting a native app. PWA is not the final answer for every mobile need; it is the lowest-friction early mobile surface and validation channel.

Why PWA First

Advantage	Relevance to Prox OS
Low-friction access	Users can open a link without store installation.
Shareable links	Studios, public Spaces, templates, and previews naturally live at URLs.
SEO and public discovery	Public OS Homes, docs, templates, and Studio previews can be indexed when intended.
Fast validation	Product loops can change without app-store review delay.
No app-store gatekeeping	Early experiments can stay web-first while policy risk is studied.
Natural fit with Web Studio	Creation, editing, publishing, and AI collaboration remain in the same platform model.
Cloudflare-first deployment	The existing deployment posture can serve mobile web and PWA assets.

PWA Weaknesses

Weakness	Product impact
Installation habit is weak	Many users do not understand or remember Add to Home Screen.
Less App Store discovery	PWA does not receive native store browsing and search advantages.
Platform limits	OS integrations vary by browser and operating system.
Push, badge, share, and file constraints	Capabilities exist unevenly and need careful browser support checks.
User education cost	The product must explain why a home-screen web app is useful.
Perceived trust gap	Some users expect a native app for camera, push, share, and offline workflows.

Correct Use In Prox OS

PWA should be used as:

the first mobile Launchpad;
a responsive validation surface for pinned Studios and recent Views;
a route-based preview surface for Studio View JSON;
a testbed for capture, notifications, and approval workflows;
a bridge from mobile preview to Web Studio.

PWA should not be used as:

a claim that Prox OS has solved native mobile;
a replacement for the Web Studio;
a way to bypass native platform policy while acting like an app marketplace;
a place to expose arbitrary user-generated execution.

Future Platform Notes

Android Trusted Web Activity can be researched later as a wrapper around a validated PWA, but it should not be implemented now.

iOS Home Screen Web App behavior and Web Push can be researched later for notification and installability workflows, but they should not be implemented now.

Any future PWA install prompt should explain:

what the user gets from installing;
which permissions are requested;
how notifications and capture work;
how to return to the full Web Studio;
how data is stored and removed.