Skip to main content
A public extension needs a listing. Some of it is in your manifest and ships in the bundle; the rest is editable in the developer portal without publishing.

​
The fields

A public manifest is invalid without all five listing fields, so the publish that would put you in the store is the publish that fails first if one is missing.

​
Editing without publishing

The Listing page in the developer portal writes the long description, the three URLs and visibility onto the release the store is already serving — the draft, if nothing is live yet. It does not create a release, does not change your bundle or your version, and does not go to review. The save lands on the review timeline as a note, so the change is on the record. Screenshots and the icon come from your bundle. Change them in your project and publish.

​
The store card

Owners see five things in the Tap Store’s grid: your icon, your name, your one-line description, your vendor name and your category. The Listing page draws that card above the form, next to the screenshots your bundle carries, so you are editing the long description and the URLs with the card an owner sees in front of you. The five fields on the card are manifest fields, so changing one of those is a publish. Installing shows every scope you asked for with its label, its description and the justification you wrote, a line stating what data the extension receives and what it never receives, and a link to your privacy policy. Write the justification for the person deciding, not for the reviewer — it is the sentence that decides whether they install. The listing carries uptime, response time and approval rate once Tappify computes them. See Reporting and quality.