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:
- Inside the app, at launch or when they reach the relevant screen.
- On their lock screen, through a push notification.
- 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:
- The update adds something the user can see or use: a new feature, a redesigned screen they rely on, a long-requested fix.
- The change affects their workflow: something moved, a default changed, a feature was removed.
- You've fixed a problem many users complained about. "You asked, we fixed it" is a strong message.
Don't show one when:
- The release is bug fixes and performance. Nobody wants a modal that says "improvements."
- The user is brand new. Someone on their first launch doesn't care what changed; they never saw the old version. Skip the sheet for anyone whose first launch was this version.
- You already showed it on another device for a signed-in user, if you can tell.
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:
- One to three items. If you have more, you have a changelog, not a highlight. Link to the full changelog in settings.
- Lead with the benefit, not the name. "Find any photo by typing what's in it" beats "Introducing Smart Search."
- One primary action that deep-links to the feature. A What's New screen that only says "Got it" wastes the user's interest.
- Visual over text. A short looping clip or a screenshot of the feature beats a paragraph.
- Easy to dismiss. A visible close or "Not now." Swiping down should close it.
- Matches your app. Use your fonts and colors. It should look like part of the product, not an ad.
Copy templates
Use one of these for each item:
| Pattern | Example |
|---|---|
| "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:
- On iOS, use the system review API. Guideline 5.6.1 says Apple will disallow custom review prompts, and the system shows its prompt at most three times per app in a 365-day period (Apple HIG).
- On Android, use the In-App Review API. Google enforces a quota it doesn't publish, and says your app shouldn't ask any question before or while showing the card, such as "Do you like the app?"
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:
- goes once, to people who opted in to updates and haven't opened the app since the release
- arrives at a reasonable hour in their time zone
- names the benefit, not the version: "Your streak now pauses while you travel" rather than "Version 3.2 is here"
- opens the feature directly when tapped, not the home screen
The store: promotional text and In-App Events
- Promotional text sits above your App Store description, can be up to 170 characters, and can be changed without submitting a new version (App Store Connect reference). Update it for every big release.
- In-App Events appear as event cards on the App Store. An event can last up to 31 days and be promoted up to 14 days before it starts, and people can opt in to a notification when it begins (Apple). A major feature launch, a seasonal challenge or a new content drop can qualify, if it's framed as something to take part in rather than a changelog.
Launch checklist for a big update
Before release
- Write the App Store "What's New" text with the significant changes listed
- Update promotional text
- Build the What's New sheet: 1 to 3 items, deep link, "Not now"
- Add the version check, skipping first-launch users
- Decide the review moment: which action, after how many uses
- Draft the push for opted-in users who haven't opened the app
- Update help articles and the answers your support team (or AI) gives
Release day
- Ship to a small percentage first if you can (phased release on iOS, staged rollout on Play)
- Watch support messages for confusion about the change
One week after
- Send the push to opted-in users who still haven't opened the app
- Reply to reviews that mention the old problem, saying it's fixed
- Count how many users tried the feature from the sheet vs found it on their own
Measuring whether it worked
Track these events:
| Event | Why |
|---|---|
whats_new_shown | Denominator |
whats_new_cta_tapped | Did the sheet make people curious? |
whats_new_dismissed | If 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 feature | Confusion 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:
- Push to the right people at their local time. Send the announcement to a segment you define, for example by tag, at a set hour in each person's time zone, with quiet hours and a daily cap. Promotional pushes go only to people who opted in.
- Answers that know about the update. The AI answers support questions from your notes and help articles, so update them once and "how do I use the new X?" gets answered in seconds.
- Feedback in context. Users can reply in the chat or send a bug report with a screenshot, so problems with the new feature reach you instead of the review box.
- A review request after you've helped. You can send a review card once a problem is solved. With Ask automatically on, closing a chat that ended with the customer's thanks sends it once. On iOS the button opens the App Store write-review page; on Android it opens your Play listing.
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.