Boot Store
Store Workflow
The Boot Store workflow connects creator uploads, review, quality evidence, access labels, app handoff, and support without duplicating protected backend state.
Public surface
Store Workflow
A good store flow makes every pack understandable: what it is, who made it, what it supports, how it was reviewed, and where the app takes over.
Creator submits package, preview media, metadata, ownership notes, and compatibility evidence.
Admin checks package report, rights, previews, safety wording, and access type.
Approved packs appear in public shelves with clear labels and app handoff.
Updates, removals, refunds/support, and compatibility changes stay auditable.
| States | Draft, submitted, pending review, approved, rejected, edit requested, paused, removed. |
|---|---|
| Evidence | Package report, hash, previews, ownership note, creator profile, compatibility labels, and reviewer notes. |
| Access | Free, Premium-related, clean-export related, or future paid pack labels must be clear. |
| Protected data | Purchase tokens, private user records, and admin review notes stay out of public pages. |
Workflow
How this should work
A public page should explain the user path while protected state, permissions, and audit trails stay in CRYA Mission Control.
Creator builds and validates the pack.
Metadata, previews, package, and ownership evidence are sent.
Admin approves, rejects, or requests edits.
Users browse public shelves and open app handoff.
Related surfaces
Continue the journey
Move between public discovery, creator guidance, store trust, and support evidence without exposing private admin systems.