Roadmap
Platform Roadmap
The platform roadmap sequences the 8 platform capabilities behind the App Store collections.
The platform roadmap sequences the 8 platform capabilities behind the App Store collections.
Capability Sequencing
| Phase | Primary Capability Work | Product Surface |
|---|---|---|
| v0.1 | App Runtime and View foundations through registry, windows, iframe hosting, and reusable app package boundaries. | App Store, Today, system apps, developer apps |
| v0.2 | Source and Information foundations for GitHub, RSS, and cloud connector exploration. | Awesome GitHub Radar, RSS Knowledge Inbox, GitHub Workspace |
| v0.3 | Publishing and View foundations for public Spaces, templates, clone/remix, and badge metadata. | Prox Spaces, Public Space Gallery, Template Space |
| v0.4 | App Runtime developer surface: manifest standardization, Prox.js exploration, Window API, Theme API, Permission API, AI Context API. | Developer App Platform, app templates, app validation |
| v0.5 | Source, Permission, and Knowledge expansion through local bridge research and local-first metadata indexes. | Obsidian connector, Eagle connector, local folder index |
App identity and public URLs
Long-term direction (not implemented): manifest-first apps with stable appId, creator-owned path namespaces (GitHub / Hugging Face style), and official subdomains only for infrastructure (docs, ui, api). Do not default to per-app *.prox-os.com DNS.
See app-namespace-and-domain-strategy.md before designing backend registry, App Store tenancy, or public share links.
Rules
- Runtime registry describes what can open now.
- Store catalog may describe roadmap apps, templates, Spaces, sources, and AI workflows.
- Permission Platform must gate source access, AI context access, public publishing, and write-capable workflows.
- View Platform should avoid one-off app-only data shapes when the same data could be rendered as table, board, timeline, graph, calendar, dashboard, or window.
- Publishing Platform should treat public Space, RSS feed, API, embed, and badge output as governed exports from private workspace data.
First API Candidates
The first stable capability APIs should support:
- Source registration and sync status.
- Structured repo/article/tool objects.
- View definitions for cards, tables, and radar boards.
- App and AI permission scopes.
- Space template metadata.
- AI context pack export.