What's New screens: how to announce app updates people actually read

You spent three weeks on a feature. You shipped it. And most of your users will never find it. Automatic updates mean nobody reads your App Store release notes, and the feature sits behind a menu until someone writes in asking for exactly what you built.

A good "What's New" screen fixes that. It's also one of the best moments to win back a lapsed user or earn a review, if you handle it carefully. This guide covers when to show one, how to design and write it, the Apple and Google rules that apply, and how to follow up after the screen is closed.

Hailbell is our product, built and run by one developer, Vidur Saini. A later section says where it helps. Everything before that works with any stack.

Why release notes aren't enough

App Store release notes still matter. Apple's guideline 2.3.12 says apps must clearly describe new features and product changes in their What's New text, and you get up to 4,000 characters for it (App Store Connect reference). But release notes are written for the store, and they're read by people browsing the store, not by your users mid-task.

Your users find out about features in three places:

  1. Inside the app, at launch or when they reach the relevant screen.
  2. On their lock screen, through a push notification.
  3. In the store, through promotional text, In-App Events or the product page.

A good launch uses all three, in that order of importance.

When to show a What's New screen

Show one when:

Don't show one when:

Apple's onboarding guidance applies here too: it recommends a collection of context-specific tips instead of a single onboarding flow and placing instructions near the part of the interface they refer to. For a small change, a contextual tip on the relevant screen is better than a sheet at launch.

The anatomy of a good What's New sheet

A layout that works on iOS, Android and the web:

┌──────────────────────────────┐
│          What's new          │  ← short title, version optional
│                              │
│  [icon]  Feature one         │  ← benefit in 5–8 words
│          One line on why     │  ← what it does for them
│                              │
│  [icon]  Feature two         │
│          One line on why     │
│                              │
│  [ Try it now ]              │  ← primary: opens feature one
│    Not now                   │  ← always present, one tap
└──────────────────────────────┘

Design rules:

Copy templates

Use one of these for each item:

PatternExample
"Now you can [action]""Now you can split a bill with people who don't have the app"
"[Thing] is [better] now""Search is twice as fast" (only if you measured it)
"You asked for [thing]. It's here.""You asked for dark mode. It's here."
"[Old pain]? Not anymore.""Lost your streak on holiday? Not anymore. Streaks now pause while you travel."
"New: [feature] — [one-line benefit]""New: weekly summary — see what you spent, every Sunday"

For changes people might not like (a moved button, a removed feature), be direct: "Sharing moved to the top right. Tap ⋯ to find export." Explaining a change up front saves you support messages later.

Implementation notes

iOS

Store the last version that showed the sheet (for example in UserDefaults) and compare it with the current version on launch. Show the sheet only if the major or minor version changed and the user isn't on their first launch.

For smaller features, Apple's TipKit framework (iOS 17 and later) shows contextual tips that "highlight new, interesting, or unused features." Apple's own guidance is to use tips sparingly, avoid showing them each time someone uses the app, and not use them "for advertising and promotion purposes."

Android

The same version check works with SharedPreferences or DataStore. If you need users to actually be on the new version, Google Play's in-app updates API offers a flexible update (downloads in the background while the user keeps working) and an immediate update (a full-screen flow for critical updates). Use flexible for feature releases; save immediate for fixes users can't do without.

Web

Store the last seen version in local storage or on the user's account, and show a small panel or banner rather than a modal. Web users are more likely to be mid-task when they arrive.

Turning the update into reviews, the right way

A big update is a natural moment to ask for a review, because the people who use the new feature are often your most engaged users. But there are rules, and the timing matters.

Don't ask on the What's New sheet itself. The user hasn't tried the feature yet. Apple's ratings guidance says to ask only after people have demonstrated engagement and to avoid interrupting a task.

Ask after they've used the new feature successfully. For example, after their first export with the new editor, or the first time the new search finds what they typed. Call the system prompt there:

Don't filter. A "Do you like the new feature? Yes / No" step that sends only the "Yes" people to the store is review gating. Google names that question as something not to ask, and Apple's guidelines treat filtered feedback as manipulation.

A permanent "Rate the app" link is fine. Put it in settings, linked to your App Store write-review URL or your Play listing, so fans can find it any time. We covered the details in how to get more App Store reviews without asking unhappy users.

Consider whether to reset your rating summary. On the App Store, you can reset your summary rating when you release a new version. Apple's HIG warns that resetting "tends to result in having fewer ratings overall." It makes sense when an update fixes the thing most low ratings were about, and rarely otherwise.

Telling people who haven't opened the app

The What's New sheet only reaches people who open the app. For everyone else, there's push, and the store. Opt-in, timing and caps are covered in push notification strategy for indie apps.

Push: only with opt-in

A notification about a new feature is promotional. Apple's guideline 4.5.4 says push shouldn't be used for promotions or direct marketing unless customers have explicitly opted in through consent language in your app, with a way to opt out. Apple's notification guidance lists new features as an example of what people can opt in to, and says never to use the Time Sensitive level for marketing.

A good feature push:

The store: promotional text and In-App Events

Launch checklist for a big update

Before release

Release day

One week after

Measuring whether it worked

Track these events:

EventWhy
whats_new_shownDenominator
whats_new_cta_tappedDid the sheet make people curious?
whats_new_dismissedIf this is most people, the copy or timing is off
feature_first_use (with source: sheet / tip / organic)Did the sheet drive real use?
Support messages mentioning the featureConfusion or excitement

A useful benchmark is your own: compare first-use rates for this feature with the last feature you shipped without a sheet.

Where Hailbell helps

Hailbell is in-app support chat and push notifications for iOS, Android and the web. For a feature launch:

It doesn't build the What's New sheet for you; that stays in your app's code. Pro is $29 a month for 10,000 monthly active users, with a 14-day free trial, no card needed, and a 14-day money-back guarantee on the first payment if AI replies used less than 20% of the monthly allowance. Try Hailbell.

Questions

What is a What's New screen?

It's a short in-app sheet shown after an update that highlights one to three new features, with a button that takes the user to them. It's different from App Store release notes, which are shown in the store.

Should every update have a What's New screen?

No. Show one only for updates that add something users can see or that change how they use the app. Bug-fix releases don't need one, and new users shouldn't see one at all.

Can I put a "Rate us" button on the What's New screen?

You can link to your store page for reviews, but it's better to wait until the user has actually tried the new feature and then use the system review prompt. Don't ask "Do you like it?" first and only send the "yes" people to the store; that's review gating.

Can I send a push notification about a new feature?

Only to people who opted in to promotional notifications. Apple's guideline 4.5.4 requires explicit consent for marketing pushes, and feature announcements count. Send it once, at a reasonable local time, and deep-link to the feature.

What should I write in App Store release notes?

List the significant changes clearly, as Apple's guideline 2.3.12 requires. Lead with the benefit to the user, keep it scannable, and save "bug fixes and improvements" for releases that really are only that.

Ship your next update with a launch plan. Hailbell gives you in-app chat and push for iOS, Android and web, so you can announce features to the right users and hear what they think. Try it free for 14 days.

Questions about announcing an update from the app? Start a chat with us.