App Store Surfaces
This document guides App Store presentation and catalog metadata. It does not
Status
This document guides App Store presentation and catalog metadata. It does not add a marketplace backend, install logic, payment flow, or live route changes.
Three Store Surface Families
Single App
A Single App is one runnable app. It can be first-party, community, system, iframe-backed, route-backed, local-module-backed, or external.
App cards should show launch status honestly. The runtime registry remains the truth for what can open now.
Hub / Bundle
A Hub is a runnable workspace or product bundle. It can include apps, modules, workflows, and data surfaces. Later, it can become a subscription and revenue split container.
Examples:
- Founder Suite Hub.
- AI Agent Control Plane Hub.
- Developer Platform Hub.
Collection / Editorial
A Collection is a curated list or editorial playlist. It can reference apps, hubs, spaces, templates, or external links. It is not normally a direct billing unit or runnable product.
Collections can be official, community, user-curated, or organization-curated. Store collection listing paths should still be owner-scoped.
Badges Are Not Ownership
The App Store can show badges such as:
Official.Featured.Verified.Built-in.Community.Incubating.
Badges help discovery and trust. They must not replace creator namespace or owner-scoped listing URLs.
Hub Is Not Folder
A Folder groups shortcuts and layout for a user or team desktop. It is private or team-scoped by default and does not imply product packaging.
A Hub has product logic. It can be installed, opened, subscribed to later, and listed in the Store with included apps/modules and ownership metadata.
UI Guidance
App Store UI may show:
- Surface type badges:
App,Hub,Collection. - Owner badges and future owner paths.
- Discovery pages for apps, hubs, collections, spaces, featured, and editorial.
- Concept cards for first-party Hubs.
- A short explanation that Store listings are owner-scoped.
App Store UI must not:
- Pretend marketplace backend exists.
- Change real install behavior before the backend exists.
- Use global ownerless listing aliases as canonical URLs.
- Show revenue split as live.