Guide · 8 min read
App Store Release Notes Strategy: Turn "What's New" Into an ASO and Re-Engagement Asset (2026)
Every time you ship an app update, you get one field most developers treat as a chore: the "What's New" text visible to anyone who opens your App Store listing. It appears before users trigger the update, before lapsed users decide to reinstall, and in AI assistant crawls of your product page. Most apps waste it on "bug fixes and improvements." Here is the strategy that treats it as a conversion and retention asset.
What the "What's New" field actually is — and where it appears
The "What's New" field is a 4,000-character text area in App Store Connect — one per locale, supporting the same localization structure as your description field. It publishes with every new version submission and replaces the previous version's copy the moment your update goes live. Unlike the description, it cannot be updated without submitting a new binary; it is version-locked to the release it ships with.
The field surfaces in three distinct places. First, on your app's product page in the App Store, beneath the latest version number — visible to anyone who taps your listing, including users evaluating whether to reinstall a previously deleted app. Second, in the Updates tab on iOS 26 when a user has a pending update: they see the What's New text before choosing to install. Third, on the web App Store listing indexed by search engines and crawled by AI assistants including Apple Intelligence, ChatGPT, and Perplexity. Each surface serves a different user intent.
The critical distinguishing fact: this is the only App Store field that reaches existing users. Every other indexed field — title, subtitle, keyword field, description — targets users who have not installed your app yet. The What's New field is your only official channel to users who already have it, plus a second-chance pitch to users who deleted it. Treating it as release engineering overhead misses what it actually is: a re-engagement surface that updates itself every time you ship.
"Bug fixes and improvements" is an install-rate problem, not just a lazy habit
"Bug fixes and improvements" is a conversion loss. Users in the update-pending state have a brief but real decision to make: install now, or let it auto-install in the background. For lapsed users evaluating re-installation, the question is starker: has anything changed? Both users are scanning the What's New field for the answer. Generic copy gives them nothing — and nothing reads as "I should not bother updating" or "nothing changed, so there's no reason to come back."
The same update that qualifies as a major release to your team reads as invisible to users who don't follow your roadmap. A fitness app shipping heart rate zone customization ships a substantial feature. If the release notes say "bug fixes and performance improvements," no existing user knows this feature landed, and no lapsed user has a reason to come back. The feature earned zero re-engagement value because the What's New copy didn't describe it.
The practical floor is a single specific sentence. Even a small release benefits from one honest, concrete description of what changed: "Shortcuts now sync across devices via iCloud." That sentence does work for three audiences simultaneously — it surfaces the feature to unaware users, it confirms the fix to users who reported the bug, and it signals active maintenance to any lapsed user evaluating whether the app is still alive.
The lapsed-user re-engagement angle — who reads release notes and why it matters
Lapsed users who deleted your app and are considering reinstalling read the What's New field more carefully than active users. Their bar for re-engagement is a concrete change — something that wasn't there when they left. Generic update copy fails exactly this user at exactly the moment they're most available to convert. Apps that describe real improvements in their release notes give lapsed users the reason to reinstall that the original listing may have failed to provide.
Apple's own data places redownloads at roughly 1.9 billion per week globally, versus approximately 839 million new downloads — meaning redownloads outpace new installs by more than 2:1 across the App Store. Most apps do nothing specific to capture this traffic. The What's New field is the lightest available intervention: 100 words describing what changed in the last version is the difference between a lapsed user thinking "nothing changed" and thinking "oh, they finally fixed that." For a fuller treatment of the win-back channel, the app redownload optimization guide covers listing updates, push sequences, and re-engagement campaigns that work in combination.
The re-engagement value concentrates in the update or two immediately following a user's deletion. Within 90 days of churning, lapsed users are still likely to check on an app they previously used. After six months, most won't see recent release notes unless they actively search for the app. This means the What's New copy on your most recent 2–3 versions is doing re-engagement work right now — and the copy on older versions is effectively archived. Update copy has a half-life: the most recent release deserves the most deliberate writing.
Keyword discipline in release notes: what to write regardless of the indexing debate
ASO practitioners disagree on whether Apple's App Store search algorithm directly indexes the What's New field for keyword rankings. Apple has not confirmed it officially, and controlled tests have produced mixed results — some practitioners observe ranking movement after adding target keywords to release notes, others see no signal. What is confirmed as indexed: title, subtitle, keyword field, long description, in-app event descriptions, and screenshot caption text. The What's New field's indexation status remains unconfirmed, so treating it as a confirmed ranking lever would overstate the evidence.
What is not debatable: AI assistants — Apple Intelligence, ChatGPT, Perplexity, Google's AI Overviews — crawl public App Store product pages including the What's New section when surfacing app recommendations. The field is part of the web-accessible listing that feeds AI app discovery pipelines. Natural language feature descriptions in release notes become citation material, particularly for queries like "does [app] support [feature]" or "what's new in [app]." Applying the same keyword discipline described in the long-tail ASO keyword guide to your release notes — specific, natural-language feature descriptions rather than marketing slogans — has non-zero discovery value regardless of whether Apple Search picks it up directly.
The practical move: write What's New copy with the language a user would type into App Store Search to find an app with that feature. "Offline playback now works without a subscription" outperforms "Enhanced offline experience" on every dimension — specific, benefit-first, and mirrors a real search query. This same keyword-first framing is what the App Store subtitle guide recommends for indexed fields — the discipline transfers directly to release notes even when the indexing signal is weaker.
Format patterns that drive update adoption: short hook, benefit-first bullets
The highest-converting release notes format for most apps is a one-sentence hook followed by a bulleted list of 3–5 items, each written benefit-first. The hook sets context — especially important for a major release: "Version 4.0 redesigns the daily check-in around your most-used habits." The bullets then enumerate the specific improvements. Combined, the format works at both skim speed (bullets only) and full read (hook + bullets). This same brevity principle — lead with the outcome, not the feature — is the first rule of screenshot narrative flow.
Each bullet should lead with the user outcome, not the technical mechanism. "Track workouts directly from the Lock Screen (new Live Activity)" converts better than "Live Activity widget added." "PDFs export at twice the previous resolution" converts better than "Export performance improvements." The rule is consistent: outcome first, mechanic or surface in parentheses if the user needs it. For genuinely minor releases — a bug fix, a crash recovery, a dependency update — "Stability improvements and bug fixes" at the end of a list is acceptable. The problem arises when it is the only copy. Even a maintenance release typically has one specific sentence: "Fixes a sync issue on devices running iOS 26.3" tells users something concrete and signals that the team is listening.
Localizing release notes — the gap most translated apps leave open
The majority of apps that localize their App Store listing into 5–8 languages ship English-only What's New text. App Store Connect supports full per-locale What's New copy — the same localization workflow as the description field — but it is the most commonly skipped localization target because it requires effort on every release, not just on the initial listing setup. For users in Japan, Germany, or Brazil reading update notes in English, the implicit message is that the app's support for their market extends only as far as the initial listing. English release notes in a Japanese listing undercut the credibility the localized title and description worked to build.
The localization effort for release notes is lighter than for the full description: 100–200 words per release, refreshed on each update cycle rather than once at setup. Apps that have already localized their title, subtitle, and description should include release notes localization in their standard release workflow — a one-off template takes about 90 minutes to set up, then roughly 20 minutes per release to adapt. For apps in markets where your ASO metadata work is closest to ranking on page 1, translated release notes are a low-cost freshness signal worth including. The ASO quarterly audit guide has a checklist structure where localized What's New fits naturally as a per-release task alongside quarterly metadata reviews.
The What's New field is a 4,000-character asset you ship with every update
Most apps treat release notes as documentation for the engineering team. The users reading them are deciding whether to update, whether to stay, or whether to come back. The same effort that goes into a screenshot caption — specific, benefit-first, keyword-aware — applied to your What's New field turns a chore into a re-engagement touchpoint that improves automatically every time you ship.
Before those users update and open the app, they are evaluating your listing. AppsTemple's editor lets you preview and iterate on screenshots and device frames at every App Store size — so when re-engaged users arrive through better release notes, the listing is ready to close the install.
Build your App Store listing in the editor →
Frequently asked questions
is the what's new field indexed for app store search keywords?
Apple has not confirmed that the What's New field is directly indexed for App Store keyword rankings, and ASO practitioners report mixed test results. What is confirmed as indexed: title, subtitle, keyword field, long description, in-app event descriptions, and screenshot caption text. The What's New field is indexed by web search engines and crawled by AI assistants (Apple Intelligence, ChatGPT, Perplexity) that surface app recommendations — so keyword-aware copy has non-zero value regardless of whether Apple Search indexes it directly.
how many characters can the app store what's new field have?
The What's New field supports up to 4,000 characters per locale — the same limit as the App Store description field. It supports full per-locale localization through App Store Connect. Unlike the description, it cannot be updated without submitting a new app binary — it is version-locked and publishes with each new version submission.
does the app store release notes field affect aso ranking?
The direct ranking evidence is disputed. The What's New field is not confirmed as a primary App Store search signal the way title, subtitle, and keyword field are. Its documented value is conversion-side: lapsed users evaluating reinstallation read it, users with pending updates read it before installing, and AI assistants crawl it when surfacing recommendations. Write it for these readers first; any secondary ranking signal is a bonus.
should i localize my app store release notes?
Yes, for any locale where you have already localized your title, subtitle, and description. English-only release notes in a localized listing signal that your support for that market is incomplete. App Store Connect supports per-locale What's New text using the same workflow as the description field. The localization overhead for release notes is relatively light — 100 to 200 words per release, as opposed to the full 4,000-character description that you localize once.
what should i write in what's new if i only fixed bugs?
Even a maintenance release typically has one specific, honest sentence: "Fixes a sync issue affecting devices running iOS 26.3" or "Resolves a crash when exporting to PDF on iPad." That specificity tells users who reported the bug that it was heard and fixed — a small trust signal that generic copy destroys. If truly nothing changed except build infrastructure, a brief "Stability and performance improvements" is acceptable, but treat it as a backlog prompt to have something concrete to say next time.