Home/Blog/How To Write App Store Whats New From Release Notes
Blog

How To Write App Store Whats New From Release Notes

P
promptstudio
How To Write App Store Whats New From Release Notes

What's New invents 5-star lines. Bullets only from the changelog.

The matching generator is the App Store What's New from Release Notes (No Invented Ratings) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Lock the version string

Write App Store Connect What's New text from pasted release notes. Never invent ratings, download counts, or unlisted features. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

Pasted release notes / changelog bullets: [Notes]
Version string I lock: [Version]
Character cap: [Cap or 4000]
Locale: [Locale]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Max bullets: [Max]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

Map each bullet to a notes line

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

  1. Honesty ledger: Notes count, Version, Cap, Locale, Lang, Max. Forbidden: invented ratings, invented features.
  2. Change map: each bullet categorized fix/feature/chore from Notes only.
  3. What's New text: up to Max bullets under Cap. Version line optional if Version present.
  4. Provenance: each output bullet mapped to a Notes line.
  5. Refuse list: invented 4.8 stars, invented download milestones, invented widgets not in Notes.
  6. Diff notes: Banned/Never cuts.
  7. Locale note: Locale locked; do not invent other localizations.
  8. Compliance pass: Banned/Never hits. Char count vs Cap. Gaps list of five. Format as Format.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

Honor the character cap

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

  • What's New from Notes only. Not Play Store full description and not a press release.
  • Never invent ratings, downloads, or unlisted features.
  • Honor Cap and Max.
  • No emojis.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

Refuse download milestones

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (app store whats new, no invented ratings, release notes to whats new) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.