Listing guidelines
What makes a listing that passes review and converts browsers into users.
What makes a strong listing#
- A tagline that says exactly what the app does — avoid vague marketing language.
- A cover image that shows the app's actual interface or output, not a generic graphic.
- A link that goes directly to the running app or the download — not a landing page in between.
- A description that sets accurate expectations, including known limitations.
Write for someone deciding in ten seconds#
Users compare several similar apps in one sitting. Lead with the concrete job your app does, not with what it is built on. "Turns a meeting recording into a decision list" beats "AI-powered productivity assistant".
Cover, in this order:
- The specific problem it solves.
- What the user gives it and what they get back.
- Limits — file sizes, languages, formats it can't handle.
- Roughly what a typical run costs.
Things that get a listing rejected#
- The link is broken, requires a separate account, or leads somewhere unrelated.
- The description promises capabilities the app does not have.
- Screenshots are mockups rather than the real interface.
- The app collects credentials or payment outside PortModels.
- The listing impersonates another developer or product.
Naming#
Your app name is namespaced under your publisher handle, so you don't need to add your own prefix. Pick a name that describes the app rather than one that apes an existing product.