What to know

Apple lists What’s New as version information for app updates. Use it to explain the changes in this release, not to repeat the full app description or fill the field with search terms.

Lead with the user-visible result. Group related fixes or improvements, use plain verbs, and name a feature only when the update really changes it. If a change needs a setting, account, or device requirement, say so clearly.

Use a small release-note structure: new, improved, fixed, and important setup notes. Remove internal ticket names and vague claims. If a fix changes a failure state, describe the user outcome without promising that every issue is solved.

Before publishing, compare the notes with the submitted build, check each supported locale, remove claims the build does not support, and keep a copy of the approved text with the release record.

Keep What’s New separate from promotional text and the description. Promotional text can highlight a timely message, while the description explains the product more broadly. Release notes should stay tied to the version under review and should not become a second keyword field.

A reliable draft can use three questions: What changed for the user? Where will they notice it? Is there anything they must do? Answer those questions in that order. “Improved performance” is weak on its own. “Saved searches now open faster on the results screen” gives the reader a concrete change to recognize.

Write the notes from the approved build brief, then test every named path on the release candidate. If the change depends on a server flag, account state, device capability, or region, include that condition or leave the claim out. Release notes should reduce uncertainty, not create a second support queue.

For localization, translate the user outcome rather than the internal ticket. Keep feature names consistent with the product, check text expansion, and ask a native reviewer whether the note sounds like a useful update. Save the final locale text with the version, source, owner, and review date.

Add a release-note evidence pass before approval. For each bullet, record the build or screen that proves the change, the audience that can see it, and any setup condition. Remove implementation details that do not change the user experience, and replace broad words such as “enhanced” with the observable result.

Keep fixes honest and scoped. If a fix covers one flow, device, or account state, say so rather than implying that every related problem is solved. If the update is mainly internal, use the note only when it produces a user-visible effect that a person can recognize after updating.

Store the approved notes with the version, locale, build brief, reviewer, and date. Reopen them when a release candidate changes or a server-side flag moves. That small record helps support answer questions without turning release notes into a promise the current build cannot keep.

Keep a version-level evidence ledger for each bullet: user outcome, build screen or behavior, audience, account or region condition, locale, reviewer, and approval status. If the change exists only behind a flag or for a subset of users, say so or leave it out.

Run a release-note read-back after the candidate is installed. Follow every named path with a clean account and any required setup, then compare the observed result with the approved sentence. A server-side change needs the same check even when the binary did not change.

Reopen the notes when the build, feature flag, server response, supported region, account rule, or locale changes. Preserve the previous text and evidence so support can distinguish a version change from a later product behavior change.

ASOgenic can compare release notes with the approved build brief and highlight unsupported claims before the text is submitted. Your team still reviews the locale, tone, and final wording.