
Many teams treat release notes as the last required box before submitting, dash off "Fixed some known issues and improved stability" and hit submit. But for existing users who already have your app, release notes are almost the only store copy you can use to talk to them regularly; and for new users on the fence, your version history shows whether anyone is still seriously maintaining the app.
This article is about one thing: how to actually write release notes.
| Item | App Store (App Store Connect) | Google Play (Play Console) |
|---|---|---|
| Field name | What's New in This Version | Release notes |
| Length limit | 4,000 characters | 500 characters per language |
| First version | Can't be filled in; required from the second version on | Can be filled in |
| How to edit | Must be submitted and reviewed with a new version | Filled in with each release |
| Localizable? | Yes, separately for each language | Yes, using language tags |
A few easily overlooked details:
Chinese Android stores generally have a "version notes / release notes" field too, with different length requirements per store (some have a minimum, some a maximum). Go by each store's live prompts in its developer console, and don't paste one 4,000-character essay into every channel.
Good release notes let users know at a glance:
So the writing order should be: changes users can feel first, technical fixes after, pleasantries deleted.
New "Monthly Spending Report": automatically sums up last month's income and spending on the 1st of each month, and exports as an image to share in one tap. Improved: choose a category right after entering an amount on the logging screen, saving a tap. Fixed: chart text that was hard to read in night mode on some devices.
Key points: one change per line, start with a verb, say clearly what users can do.
Fixed the occasional white screen when opening the app from a widget on iOS 26. Thanks to everyone who reported it in the reviews; your screenshots helped us find the cause quickly.
Key points: be specific about the scenario; don't just write "fixed known issues". If users reported the problem, thanking them by name works better than any marketing line.
In version 3.0 we redesigned the home screen:
- Frequently used features moved from the bottom to the first screen of home
- Settings in "Me" are reordered by how often they're used
- Your old favorites migrate automatically, no action needed If you prefer the old layout, switch back to Classic mode under Settings → Home style.
Key points: with redesigns, the biggest fear is users not finding things. Say what changed first, then how to get back.
The Chinese New Year limited theme is live and free to use from New Year's Eve through the Lantern Festival.
Key points: campaign information is time-sensitive, and release notes can't be changed once live. After the campaign ends, this note still sits in your version history, so word it to hold up when read "after it's expired". For promotional information you need to change anytime, the App Store's Promotional Text (170 characters), which can be edited at any time, is a better fit.
This update focuses on performance: faster cold starts and smoother scrolling in image lists.
Key points: if it really is routine maintenance, just say what was improved in a sentence or two; no need to pad it.
The same version often ships to the App Store, Google Play and several Chinese Android stores at once. Prepare one "master release note" and trim it per channel:
| Channel | Suggested approach |
|---|---|
| App Store | You can write it all, but put the 2–3 most important items first, because the updates list is collapsed by default |
| Google Play | Within 500 characters, keep only the 3 most important items |
| Chinese Android stores | Trim to each store's field requirements; avoid mentioning other platforms, external links or descriptions inconsistent with your review materials |
Also keep things consistent: if your screenshots, subtitle or promotional text promote a new feature, your release notes should match. Screenshots saying "New: AI photo editing" while the release notes say only "Fixed known issues" looks unprofessional. For screenshot update cadence, see screenshot update rhythm.
Release notes don't directly decide search rankings, but they shape existing users' first impression of an update and influence new users' judgment of "is this app still alive?". Spending ten minutes writing them well every release is a small ASO move with a great return.