ProductClientsDevice Studio
Gallery And Mini Experiences Naming Boundary
App Store implies installable software, third-party execution, review
Why Not App Store Early
App Store implies installable software, third-party execution, review
obligations, payment expectations, app metadata, age/content policy, and
platform governance. Those obligations are larger on mobile, especially if a
native app distributes dynamic experiences.
Early mobile Prox OS should use safer vocabulary that matches the actual capability:
- Launchpad;
- Studio Gallery;
- Experience Gallery;
- Templates;
- Verified Views;
- Dynamic Blocks.
Naming Table
| Term | Use now | Later | Avoid for now | Notes |
|---|---|---|---|---|
| Launchpad | Yes | Yes | No | Pocket entry for recents, pinned Studios, AI, capture, and approvals. |
| Device Studio | Yes | Yes | No | Companion layer and mobile rendering direction. |
| Studio Gallery | Yes | Yes | No | Curated Studio and template browsing without implying installable software. |
| Experience Gallery | Yes, cautiously | Yes | No | Useful for grouped previews and guided flows. |
| Templates | Yes | Yes | No | Safe for reusable schemas, layouts, and starter views. |
| Verified Views | Yes | Yes | No | Good for reviewed, render-only Studio View JSON. |
| Dynamic Blocks | Yes | Yes | No | Describes declarative building blocks without implying executable apps. |
| Mini Experiences | No | Yes, after governance | Avoid for now | Requires metadata, reporting, permissions, and review workflows first. |
| Mini Apps | No | Possible long-term | Avoid for now | Too close to app-platform and mobile policy obligations. |
| App Store | Existing web catalog only | Possible with real governance | Avoid for early mobile | Mobile use implies marketplace, payments, and review obligations. |
| Marketplace | No | Possible long-term | Avoid for now | Implies payments, seller terms, tax, support, and policy enforcement. |
Resource Distinctions
| Resource | Meaning | Mobile posture |
|---|---|---|
| Official system app | Prox-owned capability registered through official manifests. | Can be previewed or linked; complex use remains web-first. |
| User Studio | User-owned workspace resource with apps, data, views, AI context, and permissions. | Can be pinned, previewed, captured into, or resumed on web. |
| Public template | Reusable starting point for a Studio, View, or workflow. | Safe for Gallery if reviewed and non-executable. |
| Verified view | Declarative Studio View JSON approved for render-only mobile display. | Good early mobile dynamic UI surface. |
| Mini experience | Future constrained interactive experience with governance. | Later only after policy, metadata, and review flows exist. |
| Third-party app | Externally authored software or remote runtime. | Not a mobile native runtime target now. |
Governance Needed Before Mini Experiences
Future Mini Experiences require:
- owner identity and contact metadata;
- review status and version metadata;
- permission manifest;
- content rating and age metadata;
- reporting and takedown flow;
- block, mute, and hide controls where public or community distribution exists;
- audit log for sensitive actions;
- privacy and data-use descriptions;
- developer agreement and support expectations;
- payment and revenue split policy if monetization appears.
Until those exist, mobile should remain focused on Launchpad, Gallery, Templates, Verified Views, and Dynamic Blocks.