App Store Details
App Store details are the product metadata layer between the shell runtime
Purpose
App Store details are the product metadata layer between the shell runtime registry and the future marketplace. The detail panel is not an installer, permission grant, or backend source of truth. It explains what an app is, where it opens, which permissions it previews, what data boundary it claims, and what the roadmap says.
Phase 1
- Add
AppDetailsModalinsidepackages/apps/system-apps/src/apps/core/app-store. - Let App Store cards open a global
WindowDialogdetail modal before users chooseOpen in OS. - Add detail records for Games Hub, Snake, Subscription Tracker, AI Question Tracker, Market Watch, and Prox Wallet.
- Provide a fallback detail record for catalog-only concepts so every App Store card has a details view.
- Keep install, pin, folder, docs, and permission actions as mock controls.
Data Shape
The Phase 1 detail shape includes:
id,name,route,icon,category,status- version and changelog metadata
- developer, short and long descriptions
- screenshot placeholders
- features
- permission previews
- data boundary notes
- roadmap items
- related app ids and tags
The shell runtime registry remains the launch source of truth. Detail metadata may enrich catalog concepts that do not have runtime manifests yet.
Dialog Layering
App Store details are app-owned content, but the modal itself should render in
the global overlay layer through WindowDialog from @prox-os/os-ui. This
prevents detail panels from being clipped by the App Store window and gives the
surface a small OS-window titlebar.
The dialog is not a managed desktop window. It should not create a
WindowInstance, Dock entry, route, saved layout, or z-index record. App Store
still owns the selected catalog item and actions; WindowDialog only owns the
modal presentation.
Non-goals
- No real install or uninstall lifecycle.
- No permission grant dialog.
- No paid purchase flow.
- No screenshot asset pipeline.
- No marketplace review backend.
Future Direction
The detail model should eventually align with app package metadata, marketplace review, permission scopes, version provenance, changelog history, screenshots, owner namespace, and install state. Until those systems exist, details remain a mock presentation layer backed by static fixtures.