Long description

Where it renders

The About section follows the hero, trailer and screenshot strip. Under the prose it renders four fact tiles: category, platform, install count and the age badge. Those tiles are computed from your listing fields, not written by you — which means the prose and the tiles must agree.

If the description and short description are both empty, the listing falls back to Discover <name> on Appsinity Store.

A structure that works

1. Open with the verb. What the player or user does: "Build a city, then defend it turn by turn." Not what the game is "about".
2. List the actual content. Track count, level count, offline capability, supported input. Numbers are verifiable; adjectives are not.
3. State the platform behaviour. Which devices it runs on, whether progress syncs, and whether it needs an account.
4. Name what is monetised. Ads inside your build, optional purchases, or neither. This is where Contains advertisements needs to be consistent with the declaration.
5. Close with support. Where to report problems, especially if you have not published a support email anywhere else.

Length and formatting

The field is a plain text block. The store rewrites visible strings at runtime, and there is no markup or link formatting available to you in the About prose.

There is a payload ceiling that matters: Studio's API accepts bodies up to 5 MB, so a description thousands of lines long can fail for reasons unrelated to the text itself. Beyond a few hundred words, the block should be split — put specifics in the declarations and screenshots instead.

• Write for a scanner: short paragraphs, one idea each.
• Do not paste a changelog into the description; it dates the listing.
• Do not repeat the short description verbatim as the first sentence.

What must not be in it