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.
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.
Use this in your next ASO review
Turn the advice above into one small, traceable change. A simple review keeps your listing accurate and makes it easier to learn what helped.
- Open the current App Store Connect entry for your app and copy the App Store What’s New text material you want to check.
- Compare it with the current product behavior, supported locales, and the source linked below.
- Draft one improvement, record the reason, and validate every field limit or submission rule that applies.
- Ask a person to approve the draft before it changes a live listing.