App Store Collections

The Próx OS App Store is an App Store, App Incubator, Template Gallery, Space Gallery, Data Source Catalog, and AI Workflow entry in one surface.

The store should make a user understand that Próx OS is not just opening apps. It is incubating connected workspaces that can bring external information into structured views, AI context, permissions, workflows, and future public Spaces.

The App Store is a curated discovery layer, not the whole platform. The long-term platform core is Space + Studio + Connector + Permission + MCP Gateway. See prox-os-platform-vision.md.

Surface Families

The App Store should progressively understand three catalog families:

Family	Meaning
`Single App`	One runnable app that can be first-party, community, system, iframe-backed, route-backed, or local.
`Hub / Bundle`	A runnable workspace or bundle that can include apps, modules, workflows, and future pricing logic.
`Collection / Editorial`	A curated list that references apps, hubs, spaces, templates, or links; not normally a billing unit.

The current App Store UI also exposes three user-facing store families:

Store family	Current role
`Native Apps`	Registered Prox OS apps and broader incubating native catalog entries.
`Proxied Apps`	Third-party websites represented as manageable app-like assets with compatibility and launch mode.
`Spaces`	Proxied Space templates, installed spaces, and future workspace bundles.

Hub is not Folder. Folder is desktop organization for shortcuts and layout. Hub is product packaging with workflow logic, installation semantics, and future subscription or revenue split potential.

Official, featured, verified, built-in, and community status should be displayed as badges or tags. They should not create ownerless Store listing aliases. See App Store Surfaces and URL And Surface Model.

Collection Priority

Priority	Collection	User Promise
1	Information Radar	Turn outside signals into radars, inboxes, digests, and comparison boards.
2	Developer Workspace	Bring repos, architecture, issues, docs, releases, prompts, and review work into one control surface.
3	AI Context	Prepare safe, scoped, reusable context for agents and models.
4	Cloud Console	Track cloud dashboards, deploys, domains, uptime, cost, analytics, and incidents.
5	Data Hub	Understand where data lives, what is canonical, what is backed up, and what can be exported.
6	Automation	Turn information into workflows, notifications, webhooks, sync recipes, and agent tasks.
7	Learning & Research	Manage papers, videos, courses, reading queues, citations, and learning timelines.
8	Publishing	Turn internal notes, projects, dashboards, and spaces into public output.
9	Community Spaces	Publish, clone, remix, and showcase public project/data/app workspaces.
10	Games	Start browser-native games, iframe game placeholders, and community game submission thinking.
11	Personal Command Center	Give the user a daily operating surface for inbox, tasks, GitHub, RSS, cloud alerts, AI tasks, and review.

Collection To Platform Mapping

App Collection	User Understanding	Main Platform Layers
Information Radar Apps	Turn external information into tables, cards, radars, and digests.	Source, Information, Knowledge, View
Developer Workspace Apps	Manage repos, architecture, issues, docs, prompts, and reviews.	Source, Knowledge, Workflow, View
AI Context Apps	Prepare safe context for AI.	Knowledge, Permission, Workflow, App Runtime
Cloud Console Apps	Manage Cloudflare, GitHub, Neon, deployments, monitoring, and incidents.	Source, View, Workflow
Data Hub Apps	Show where data lives, what is canonical, and what can be deleted or exported.	Source, Permission, View, Publishing
Automation Apps	Trigger tasks, webhooks, agents, sync rules, and cleanup routines.	Workflow, Permission, Source
Learning & Research Apps	Manage courses, papers, videos, RSS, and research material.	Information, Knowledge, View
Publishing Apps	Publish internal material as sites, posts, portfolios, feeds, or showcases.	Publishing, Knowledge, Permission
Community Spaces Apps	Show public spaces, templates, clone/remix, and project galleries.	Publishing, App Runtime, View
Games Apps	Run local games now and prepare sandboxed community game embeds later.	App Runtime, Permission, Trust, View
Personal Command Center Apps	Show what to read, do, process, and review today.	Information, Workflow, View, Permission

App collections are user and market categories. Platform layers are architecture and developer ecosystem capabilities. The App Store displays collections; architecture docs capture platform capabilities; future developer docs should expose capability APIs.

Space Model

A Prox Space is a public or private project, data, or app workspace. It can eventually bundle:

Apps and templates.
README or project narrative.
Data sources and sync state.
AI context and permission scopes.
Dashboard, table, timeline, graph, or gallery views.
Publish, clone, remix, and badge metadata.

This is roadmap capability, not a completed publishing system. The current App Store UI should reserve space for these flows without pretending they are already live.

Current UI Implementation

The current App Store app lives in packages/apps/system-apps/src/apps/core/app-store.

Implementation shape:

data/appStoreCatalog.ts owns collection, Space template, platform capability, and roadmap teaser fixtures.
types.ts defines catalog types separately from shell runtime manifest types.
data/appStoreDetails.ts owns Phase 1 detail metadata for runnable apps and fallback detail records for catalog concepts.
components/* renders hero, featured apps, collection tabs, cards, App Details modal, Space templates, platform capability summary, and roadmap teaser.
AppStoreApp.tsx enriches catalog items with the runtime registry snapshot so only real registered apps can open.

This split is deliberate: the runtime registry is operational truth, while the store catalog is product incubation inventory.