To update an app, increase its version number, build and upload the new binary, add release notes, and submit for review: through App Store Connect on iOS and a new release in Play Console on Android. Use Apple's phased release and Google Play's staged rollout to limit risk, watch crash rates and reviews before expanding, and prompt users to update when necessary. On iOS, most metadata changes ship with a new version; on Google Play, listing changes can be made independently.
Versioning basics
Each update needs a higher version identifier. On iOS, you set a version number visible to users and a build number that must increase with each upload. On Android, you set a versionName shown to users and a versionCode, an integer that must increase with each release.
Use a consistent versioning scheme, such as major.minor.patch, so your team and users can understand what changed. Track versions alongside release notes and analytics annotations.
Updating on the App Store
Create a new version in App Store Connect, upload the build from Xcode or Transporter, choose the build for the version, update What's New text and any metadata or screenshots you want to change, and submit for review. After approval, release automatically, manually, or on a scheduled date.
Remember that on iOS the app name, subtitle, keyword field, and screenshots change only with a new version, while promotional text can change anytime. Our guide to promotional text explains the field you can update between releases.
Updating on Google Play
In Play Console, create a new release on the production track, or test it first on internal, closed, or open testing tracks. Upload the new app bundle, add release notes, choose a rollout percentage, and submit for review.
Store listing text and graphics on Google Play can be changed without a new app release, though changes are reviewed. This lets you test metadata independently, as covered in our store listing experiments guide.
Phased and staged rollouts
Apple's phased release gradually delivers an update to users with automatic updates turned on over seven days, and you can pause it if problems appear. Google Play's staged rollout lets you release to a percentage of users and increase the percentage over time, or halt the rollout.
Start small, monitor crash rates, ANRs, and reviews, then expand. Our staged rollouts and ratings protection guide explains how to use these tools safely.
Testing before release
Test updates with TestFlight on iOS and testing tracks on Google Play before production. Check upgrade paths from older versions, data migrations, and behaviour on older OS versions and low-end devices.
Our TestFlight beta testing guide and Google Play closed testing guide explain testing tracks.
Prompting users to update
Not all users update promptly. On Android, the Play In-App Updates API supports flexible updates, which download in the background, and immediate updates, which require users to update before continuing. On iOS, there is no equivalent system API, so apps typically check the current version against a minimum supported version from their server and show a prompt.
Use forced updates sparingly, for critical security or compatibility issues. Frequent forced updates frustrate users.
Writing release notes
Release notes tell users what changed and show that the app is actively maintained. Be specific about new features and important fixes, and keep notes short. Generic notes such as bug fixes and improvements waste the opportunity.
Our release notes and What's New guide explains how to write notes that support retention and trust.
Updating metadata and creative with releases
Plan ASO changes alongside app releases, especially on iOS. A release can include a new subtitle test, updated screenshots showing new features, or a refreshed preview video. Change a few elements at a time so you can attribute results.
Our guide on whether updates improve rankings explains how releases affect ASO, and the ASO experimentation roadmap explains planning tests.
Store requirements that force updates
Stores periodically raise technical requirements, such as Google Play's target API level requirement and Apple's minimum Xcode and SDK versions for uploads. Apps that fall behind may be unable to publish updates or may lose visibility on newer devices.
Track these requirements and plan updates ahead of deadlines. Our guides to publishing on Google Play and publishing on the App Store mention where to check current requirements.
Monitoring after release
After each release, monitor crash-free users, ANR rate, ratings, reviews, conversion, and key product metrics. Compare with the previous version. Respond quickly to new issues, and reply to reviews about bugs once fixes are available.
Our Android vitals thresholds guide explains Google Play's quality thresholds, and how app ratings are calculated explains why a bad release can quickly affect your rating.
Common update mistakes
Releasing to everyone at once without a staged rollout, skipping upgrade testing, writing generic release notes, and forcing updates too often are the most common mistakes.
Teams also change many metadata elements at once with an app update, making it impossible to tell what improved or hurt performance.
A worked example: a safe major update
A notes app ships a redesigned editor. It tests with TestFlight and an internal track, then releases with a 5% staged rollout on Google Play and phased release on iOS. Crash rates stay low, but reviews mention a missing shortcut, which the team restores in a quick patch.
The team expands the rollout, updates screenshots to show the new editor in the next iOS version, and writes specific release notes. Ratings stay stable, and conversion improves as screenshots reflect the better design.
How to do it, step by step
- Increment version identifiersRaise version and build numbers on iOS, and versionName and versionCode on Android.
- Test the updateUse TestFlight and testing tracks to check upgrades, migrations, and older devices.
- Submit with release notesUpload builds, write specific notes, and update metadata or screenshots if planned.
- Roll out graduallyUse phased release and staged rollout, monitoring crashes and reviews before expanding.
- Monitor and follow upTrack stability, ratings, and conversion, fix issues quickly, and reply to affected reviewers.
Before and after examples
Illustrative examples written for a generic app in this category, not client results. Swap in your own product, audience, and data.
Release version 5.0 to 100% immediately.
Start at 5% on Google Play and phased release on iOS, then expand.
Why it works: Gradual rollouts limit damage from bugs.
Bug fixes and improvements.
New editor with faster formatting; fixed sync delays on tablets.
Why it works: Specific notes build trust.
Force every update.
Force updates only for critical security or compatibility fixes.
Why it works: Rare forced updates reduce frustration.
Action plan
- Use consistent versioning
- Test upgrades before release
- Roll out gradually
- Write specific release notes
- Plan ASO changes with releases
- Monitor stability and reviews after every release
Metrics to monitor
- Crash-free users by version
- ANR rate by version
- Rating trend after releases
- Adoption rate of new versions
- Conversion after metadata updates
Record the baseline, release date, audience, markets, and external changes before interpreting movement. Rankings and conversion are useful signals, but a decision is stronger when activation, retention, and business value confirm that the page attracted the right users.
Frequently asked questions
How do I update an app on the App Store?
Create a new version in App Store Connect, upload a new build, add release notes, and submit for review.
How do I update an app on Google Play?
Create a new release in Play Console, upload a new app bundle with a higher versionCode, add release notes, and submit.
What is a staged rollout?
A Google Play feature that releases an update to a percentage of users, which you can increase or halt.
Can I force users to update?
On Android, the In-App Updates API supports immediate updates. On iOS, apps typically implement their own minimum version check.
Do updates need review?
Yes. Both stores review app updates, and Google Play also reviews store listing changes.
Can I change my App Store keywords without an update?
No. The name, subtitle, and keyword field change with a new version; promotional text can change anytime.
Keep reading
Go deeper on this topic
More in Platform Guides
Browse all 12 Platform Guides guides
Work with ASOWin
Primary sources
Platform capabilities and limits can change. Verify current requirements in these official resources:
