Create an app or game

What the wizard asks for

The create form states plainly: This creates a draft dashboard. You can complete store listing, build upload, content rating, and publishing after this step. The submit button reads Create draft.

• A name, which becomes the listing title and is editable afterwards.
• Whether the product is a game or an app. This is the type that decides which store it appears in.
• Nothing else is mandatory at creation. Icon, description and build all come later.
• Long descriptions and metadata can be saved as a draft at any point with Save as draft.

The record it writes

A new project starts as status: "draft" with no pre-registration block. Pre-registration is opt-in and, when enabled, stores enabled, releaseDate, autoPublishAt, autoPublishDays (default 90), ctaLabel (default "Pre register"), note, startedAt and updatedAt.

Why the game/app choice matters

The type selects the listing URL prefix and the rails you can appear in. It is not a cosmetic tag.

The slug

The listing slug is derived from the product and is what users type and what you advertise. Slugs are 64 characters in the desktop client's library manifest, and the browser's history is keyed on them, so treat the slug as permanent.

If you must rename after launch, tell your players: the old URL will not redirect.

• Use lowercase letters, digits and hyphens — the clean documentation URLs and store slugs follow that shape.
• Do not put the year or a version in the slug.
• Check the listing loads before you print it anywhere.

Right after creating it

1. Open the Listing tab. It shows 0 / 7. Work the checklist rather than jumping to the build.
2. Upload the icon first. Every rail and search result uses it, so nothing else is worth polishing until the tile looks right.
3. Write the short description. It is the line under the title in the store grids — see Short description.
4. Pick the category carefully. It drives the breadcrumb and the category page — see Store categories.