Home Articles ASO How to Write App Release Notes: A Guide to the App Store's 'What's New' and Android Release Notes

Table of contents

  • Quick nav

Was this helpful?

Share it with someone who needs it.

How to Write App Release Notes: A Guide to the App Store's 'What's New' and Android Release Notes

A
AppShot Maker
10/20/2026
How to Write App Release Notes: A Guide to the App Store's 'What's New' and Android Release Notes

Why release notes deserve real effort

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.

1. Know the official rules first

ItemApp Store (App Store Connect)Google Play (Play Console)
Field nameWhat's New in This VersionRelease notes
Length limit4,000 characters500 characters per language
First versionCan't be filled in; required from the second version onCan be filled in
How to editMust be submitted and reviewed with a new versionFilled in with each release
Localizable?Yes, separately for each languageYes, using language tags

A few easily overlooked details:

  • App Store release notes can't be "hotfixed". They're tied to the version; once it's live, you can only change the copy with the next version. So finalize before you write it in.
  • It's not a keyword field. The App Store's official search metadata is the app name, subtitle and keyword field; stuffing keywords into release notes won't help rankings and just makes them unreadable.
  • It appears in two places: the "Version History" on the product page and the updates list on users' devices. The latter is where existing users see it most, so the first few lines matter most.

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.

2. Three questions release notes should answer

Good release notes let users know at a glance:

  1. What does this mean for me? New features, experience changes, which annoying problem got fixed.
  2. Do I need to do anything? Whether to log in again, whether an entry point moved, whether old data will be migrated.
  3. Are you still serious about this? Tone, detail and consistency tell people whether the app is worth keeping.

So the writing order should be: changes users can feel first, technical fixes after, pleasantries deleted.

3. Five templates you can use directly

Template 1: Feature update

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.

Template 2: Bug-fix update

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.

Template 3: Major redesign

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.

Template 4: Campaign / seasonal update

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.

Template 5: Minor maintenance release

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.

4. Tailoring for different channels

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:

ChannelSuggested approach
App StoreYou can write it all, but put the 2–3 most important items first, because the updates list is collapsed by default
Google PlayWithin 500 characters, keep only the 3 most important items
Chinese Android storesTrim 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.

5. Common mistakes

  • The eternal "Fixed known issues, improved stability": users can't tell whether to update, and can't see the team's investment.
  • Keyword stuffing: release notes aren't part of App Store keyword indexing; stuffing only hurts readability.
  • Technical jargon: "refactored the network layer" or "upgraded the SDK" means nothing to users; say "loads faster" or "more reliable login".
  • Exaggerating or promising what you can't deliver: claims like "fastest anywhere" or "free forever" may run into review rules and invite bad reviews.
  • Mentioning other platforms: writing "Android version updated too" in App Store release notes tends to attract review attention.
  • Expired time-sensitive info: campaign text can't be removed once it's in release notes; think about how it reads after it expires.

6. Pre-submission checklist

  • The first 2–3 lines are changes users can feel
  • Each item starts with a verb, one change per line
  • Where entry points changed, you explain how to find them
  • No keyword stuffing, no other platform names, no unverifiable claims
  • Each language written separately, not machine-translated
  • Consistent with this version's screenshots and promotional text
  • Google Play version kept within 500 characters

Final thoughts

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.

Ready to design your store screenshots?

Try AppShotMaker and turn raw captures into store-ready screenshots in minutes.

On this page

About 19 min read0%

AppShot Maker

App screenshot design tools

  • Ready-made layout templates
  • App Store, Google Play & Android sizes
  • Fast, simple PNG zip export