Creator Hub
Build a public identity around your boot packs.
CRYA Creator Hub gives makers profile space, showcase paths, submission rules, trust levels, badges, and clear review expectations.
Creator profile
A storefront for makers
Creator pages should show evidence users care about: previews, compatibility, pack history, ratings, support links, and clean ownership notes.
Public creator name, avatar, trusted links, and style tags.
Featured packs with preview images and compatibility labels.
Ownership notes and source declarations for review confidence.
Badges, trust level, submission history, and community conduct signals.
| Preview set | Static cover, motion note, and minimum screenshot set. |
|---|---|
| Compatibility | Device family, resolution, fps, boot/shutdown path, and known limits. |
| Ownership | Creator declaration, source notes, licenses, and attribution. |
| Quality | Package report, frame count, desc.txt, export type, and review notes. |
Creator surfaces
Everything a maker needs before publishing
Creator Hub should make the public path feel complete while review, payouts, moderation, and private notes stay protected.
A public creator identity with avatar, bio, links, style tags, showcase packs, trust badges, and support-safe contact paths.
Preview images, motion notes, device compatibility, package reports, release notes, and app handoff expectations.
Clear requirements before review: screenshots, ZIP/QMG context, ownership notes, compatibility labels, and known limits.
Badges and ranking signals should reward reliable metadata, clean reports, conduct, support quality, and maintained packs.
Seasonal drops, AMOLED themes, brand-safe packs, creator bundles, and future premium collections keep discovery alive.
Creator activity should connect to showcase topics without exposing private admin notes or account data.
Submission lifecycle
From first draft to trusted pack
The public workflow should help creators prepare the right material before review starts.
Create or import a boot package, then make sure the preview, timing, and dimensions are understandable.
Add device notes, known limits, source declaration, screenshots, and creator credit.
Run Package Doctor and keep the report with the submission evidence.
Send the pack through the store workflow with clear category, compatibility, and access labels.
Update packs when users report device issues, metadata gaps, or visual problems.
CRYA should keep ownership, attribution, license notes, and takedown paths understandable before paid packs arrive.
A pack can look good and still fail review if evidence, compatibility, metadata, or source notes are weak.
Future paid packs, creator bundles, and premium discovery should stay separate from app Premium so users know what they are buying.
Warnings, private notes, payouts, account actions, and dispute handling stay inside Mission Control with audit trails.
Creator routes
Where the public creator system expands next
These routes already exist as guarded depth pages and should become the visible creator operating model.
Creator identity, showcase, trust, and support-safe public details.
OpenTrustBadgesTrust levels, achievements, quality signals, and review-safe recognition.
OpenDiscoveryRankingsDiscovery signals based on quality, support, activity, and maintained packs.
OpenCommunityCompetitionsSeasonal prompts, community showcases, launch windows, and featured drops.
Open