App submissions
Prepare your app. Secure intake is not open yet.
This page explains exactly what a future submission will require without displaying a form that discards data or stores private contact details unsafely.
Submission checklist
Information to prepare
- App and developer or publisher name
- Official website and authorized distribution channels
- Contact email for private editorial follow-up
- Primary category, pricing model, and Mac compatibility
- A concise original description of the app and its intended users
- Evidence for important pricing, platform, and purchase claims
What must work first
- Private durable storage with no local JSONL fallback
- Strict body, field, URL, email, and category validation
- Duplicate and replay-safe submission identifiers
- Server-side bot verification and documented rate limits
- Approved contact-data access, retention, deletion, and privacy rules
- An authenticated editorial queue that cannot publish automatically
How review will work
- 1
Stored privately
A stable identifier is returned only after durable storage succeeds.
- 2
Human review
An editor checks identity, evidence, assets, originality, and catalog fit.
- 3
Needs edit or decision
The record can be returned for changes, rejected, or approved for readiness review.
- 4
Separate publication gate
Submission success never makes an app public or bypasses the 25-app cap.