App Release Operations Product: From Build Status to Phased Release

On November 21, 2026, from 00:15 to 00:23 Singapore time (16:15 to 16:23 UTC on November 20), we read the US store pages of 8 popular apps with app_store/profile and google_play/profile. The App Store gave an exact version number for all 8 apps. Google Play gave the value "VARY" for 6 of them. Only Notion and Slack showed a number on Google Play, and neither app had the same number in both stores. Notion uses two different schemes: 1.7.355 on iOS and 0.6.4324 on Android. Slack showed 26.11.30 on iOS and 26.11.20.0 on Android.
The App Store also returns a "current version rating count". We read 8 apps in the US and 5 more apps in China and Mexico. For all 13 apps, this number was equal to the all-time rating count. If you use it to judge a new release, your alert will never fire. Of the 8 US release notes, only Slack's note named a change that a user can see.
The main record for a release product must come from your own App Store Connect and Play Console accounts. Public store data is useful for one check: "what does the user see now?" It is also useful to watch competitors. We checked nine platform facts against the Apple and Google documents of October and November 2026. Six are the same, and three need an addition. Public reviews also arrive more than one day late, so they cannot be a stop signal for a phased release.
Key points
- 8 popular US apps: the App Store shows an exact version for 8 of 8; Google Play shows "VARY" for 6 of 8. The last update of one app differs by up to 6.0 days between the two stores.
- The public "current version rating count" on the App Store was equal to the total count for 13 of 13 apps. Group reviews by
app_versioninstead.- Apple phased release always takes 7 days: 1%, 2%, 5%, 10%, 20%, 50%, 100%. You can pause it for 30 days in total. On Google Play, the percentage does not go up unless you change it.
- Apple says that you cannot revert to a previous version. You must submit a new version. Write your stop rules and server-side switches before you submit.
- The store version, review, storefront and cost sections come from 45 live calls on 2026-11-21. The phased release, vitals, permission and webhook sections come from Apple and Google documents. We did not test them on an app of our own.
- Of 45 live calls, 44 were charged, for $0.061116 in total. Daily store pages plus one review page for 20 apps cost about $3.33 per month at catalog prices.
A build, a store version and a phased release are three different objects. The lever is the stop rule that can pause the release at any time. Illustration
One release has three kinds of "version"
A message such as "2.3.1 is out" can mean three different things. The first thing is a build. In the App Store Connect API, the Builds resource is one uploaded build after Apple processes it. On Android, the match is an APK or app bundle that you upload with the Google Play Developer API. Each one has its own version code.
The second thing is a store version. The App Store Versions resource holds the version string, the attached build, the release type and the review state. Before you submit, you can attach a different build to the same version. On Google Play, the match is a release inside a track. The edits.tracks resource gives each release a name, a list of version codes, release notes, a status and a userFraction.
The third thing is the version on the phone of the user. During a phased release, some users have the new version and some users have the old one. The version number on the store page does not tell you which version one specific user has.
If you put all three into one row, such as version = 2.3.1, status = live, you lose the states that release operations need most. Apple's app and submission status reference puts statuses into three colors. Red means that you must act, for example after a rejection. Yellow means that you or Apple are still working, for example Waiting for Review, In Review or Pending Developer Release.
Green has one status only: Ready for Distribution. A Google Play release has four status values: draft, inProgress, halted and completed. The edits.tracks page says that you can set userFraction only when the status is inProgress or halted. The value must be between 0 and 1.
The two state machines do not map one to one. A shared model can put both platforms side by side on one board. For any check, you must go back to the platform's own state and object ID.
| What you mean | Apple object | Google Play object | Visible on the public store page? |
|---|---|---|---|
| Build | Build (processing state, version, build number) | APK or app bundle (version code) | No |
| Store version | App Store Version (review state, build, release type) | Release in a track (name, versionCodes, status) | Only the live version and update time |
| Phased release | App Store Version Phased Release (state, current day) | userFraction and countryTargeting on the release | No percentage |
| Release notes | One "What's New" text per language | releaseNotes per BCP-47 language | App Store shows the local text |
| User feedback | Customer Reviews API (your own app only) | Reply to Reviews API (your own app only) | Public reviews with app_version |
We checked the last column with live calls. The other columns come from Apple and Google documents that we read again on November 21, 2026.
The two feedback APIs work only for your own app. Apple's Customer Reviews endpoint needs an App Store Connect API key. Google's Reply to Reviews API returns only production reviews that have text. It allows 200 read requests per hour and 2,000 replies per day, and each reply can have 350 characters at most. So use these two APIs for the reviews of your own app, and use public reviews for competitors.
Nine platform facts, checked again in November 2026
A release board depends on nine platform facts. On November 21 we opened the Apple and Google source pages again and checked each fact. Six facts are still correct. Three need an addition. They are the API state values of an Apple phased release, the Android version code rule for a fix build, and App Store Connect webhooks.
| Platform fact | Source we read on November 21 | Result |
|---|---|---|
| A build is one uploaded and processed binary | Builds; the Upload builds help page says that the build string identifies one build in the whole system | Still correct |
| An App Store Version holds state, build and release type | App Store Versions | Still correct |
| A phased release has its own state | App Store Version Phased Releases; PhasedReleaseState is INACTIVE, ACTIVE, PAUSED or COMPLETE | Addition: state values |
| A Google Play release goes to a test track or production, with staged rollout | APKs and Tracks: qa, beta and production are the default tracks | Still correct |
| Release notes are part of the release | edits.tracks: releaseNotes per language | Still correct |
| You cannot revert an App Store release | Create a new version | Still correct, same text |
| An Android fix needs a new build | How app updates work: the update version code must be equal to or higher than the installed one | Addition: version code rule |
| Platform state changes must reach the board | App Store Connect webhooks and webhook events | Addition: push, not only polling |
| Keep public competitor data apart from your own release controls | Public profile and review data is read-only (our live calls) | Still correct |
All three additions change the design. PhasedReleaseState has four values only, so the board can read "paused", "active" and "complete" from the API. It does not need to guess from a percentage. The Android version code rule means that Google Play also has no "revert".
To fix users who installed a bad build, you ship a new build with a higher version code through the Play Developer API edits. The edits page also gives a warning that matters for sync. Suppose that a person changes the app in the Play Console web page while an edit is open. Then the API discards the edit. Your team must agree who changes what, and when. Webhooks can send build and version state changes to your server, so the board does not need to poll all the time.
What users see in the store: 16 live profile calls
We wanted to know what public data can check for a release board. On November 21, 2026, from 00:15 to 00:23 Singapore time, we read the App Store and Google Play profiles of 8 popular US apps. We made two calls per app, 12 seconds to a little more than 2 minutes apart. Each request body was {"platform": …, "action": "profile", "params": {"app_id": …, "country": "us"}}. The App Store needs a numeric ID. Google Play needs a package name.
We compared the returned fields with the catalog's response_fields for app_store/profile and google_play/profile. The App Store capability has 29 fields, which include version, updated_at, release_notes and current_version_rating_count. The Google Play capability has no release notes field. It has version, updated_at, installs and a rating histogram.
One app, two stores, two different version signals (real responses at 00:15 Singapore time on 2026-11-21). EveryInfra API response screenshot
| App | App Store version | App Store update (UTC) | Google Play version | Google Play update (UTC) | Gap |
|---|---|---|---|---|---|
| 26.45.75 | 2026-11-15 12:50 | VARY | 2026-11-18 23:16 | 3.4 d | |
| Spotify | 9.2.0 | 2026-11-13 13:54 | VARY | 2026-11-17 09:35 | 3.8 d |
| Duolingo | 7.149.1 | 2026-11-18 16:14 | VARY | 2026-11-17 20:12 | 0.8 d |
| Uber | 3.748.10002 | 2026-11-19 17:39 | VARY | 2026-11-13 18:00 | 6.0 d |
| Notion | 1.7.355 | 2026-11-18 21:44 | 0.6.4324 | 2026-11-18 20:56 | 0.0 d |
| Telegram | 13.2.2 | 2026-11-16 08:10 | VARY | 2026-11-18 23:50 | 2.7 d |
| Netflix | 26.6.0 | 2026-11-16 17:15 | VARY | 2026-11-16 22:41 | 0.2 d |
| Slack | 26.11.30 | 2026-11-18 20:01 | 26.11.20.0 | 2026-11-18 01:26 | 0.8 d |
The first result is about version numbers. The App Store gave an exact version for all 8 apps. Google Play returned VARY for 6 of 8. On the Play web page this shows as "Varies with device", and the android_version field shows the same text.
The reason is on the Android side. One app can send different builds to different devices and Android versions. So no single number is true for all users.
The two apps with a number did not match across stores. Notion shows 1.7.355 on iOS and 0.6.4324 on Android, which are two different schemes. Slack shows 26.11.30 and 26.11.20.0, one minor step apart. We also read Mercado Libre in Mexico: 10.592.3 on the App Store and 10.591.5 on Google Play. So all 3 apps that we can compare had different numbers. Do not assume the same number on both platforms. To know which Android version is live, read the track and release in Play Console. The public page cannot give you that answer.
The second result is about update times. For the 8 apps, the last App Store update was 1.3 to 7.4 days before 00:00 UTC on November 21. The Google Play updates fell between November 13 and November 18. All 16 update times were in the last 8 days. For the same app, the gap between the two stores was 0.0 to 6.0 days.
Notion and Netflix updated both stores at almost the same time. Uber's App Store update came 6.0 days after its Google Play update. WhatsApp, Spotify and Telegram updated Google Play 2.7 to 3.8 days after the App Store. You can compare this with your own release log. Suppose that the board says "both platforms on November 18" and the store page shows an iOS update on November 15. Then the two platforms do not move together, and the retrospective should ask why.
The third result is about ratings. The field name current_version_rating_count means "number of ratings for the current version". We read 13 App Store apps: 8 in the US, 4 in China and 1 in Mexico. For all 13, this field had the same value as rating_count. For WhatsApp, both fields were 18,992,389.
So the public "current version" rating is the full rating history, and it almost does not move after a release. A rule such as "alert when the current version rating drops" will never fire. To see how users react to a new version, group the reviews by their app_version field. One page of newest reviews had 1 version on the App Store and 7 to 10 versions on Google Play.
How much the release notes say: 8 US notes under a fixed rule
Do release notes name real changes, or only stock phrases? We counted with real data. Before we read the notes, we wrote a rule and saved it in scripts/notes_rules.json at 00:17. A note is "generic" when three conditions are true.
It is shorter than 200 characters. It contains a stock phrase such as "bug fixes", "performance" or "improvements". It contains no change marker such as "new:", "you can now" or "added". All other notes are "specific".
The rule marked 5 notes as generic and 3 as specific. We then read each note. The manual result was different. Of the three "specific" notes, Uber's note says "updates to improve localization" and "various bug fixes and improvements".
Duolingo uses 274 characters for a joke about the mascot owl eating bugs. Netflix says only that it improved the player. None of the three names a change that a user can see. They are only long.
Slack's note has 163 characters and starts with "Bug Fixes", so the rule marked it generic. But it names one change in behavior. A tap on a name in a message from another workspace now opens the author's profile. It does not send you to a browser. By manual reading, only 1 note of 8 names a concrete change.
| App | Characters | Rule result | Manual read |
|---|---|---|---|
| Uber | 382 | specific | Localization updates and "various bug fixes" |
| Duolingo | 274 | specific | A joke about the mascot; no change named |
| Netflix | 202 | specific | "Player improvements"; no detail |
| Slack | 163 | generic | Names one change: a tap on a name now opens the profile |
| Spotify | 127 | generic | Asks users to keep updates on |
| 116 | generic | Stock text about bugs and performance | |
| Telegram | 40 | generic | Stock text |
| Notion | 39 | generic | Stock text |
A rule that uses length and keywords is wrong in both directions. A better check for a release product is a link: does each line of the note match an approved, user-visible change in the change list? Users also complain about stock notes.
One thread on r/apple asks Apple to ban generic release notes, and one thread on r/ios discusses "bug fixes and performance improvements". These threads show that some users read the notes. They do not show that stock notes reduce downloads.
How fast a new version appears in reviews: 8 apps
The current version rating is not useful, so we read the reviews. On November 21, 2026, from 00:25 to 00:29 Singapore time, we read the newest US reviews of 4 apps with app_store/reviews (sort=newest). We also read the newest English reviews of 4 apps with google_play/reviews. Both capabilities return app_version on each review, so you can group the reviews by version.
On the App Store, each page of 30 reviews had one version only. For WhatsApp, Spotify and Duolingo, all 30 reviews were on the version that the store showed (26.45.75, 9.2.0 and 7.149.1). For Uber, all 30 reviews were on 3.748.10001, but the store showed 3.748.10002. The four pages covered 5.3 to 14.8 hours each. The newest review on each page was 30 to 33 hours older than our read. On Google Play, the newest review on each of the 4 pages was 24.0 to 24.4 hours older than our read.
Uber's version 3.748.10002 went live on November 19 at 17:39 UTC. The newest review on the Uber page was from 10:01 UTC on the same day. The hours after the release were not yet in the public reviews that came back. So the page had no review for 3.748.10002.
On Google Play, each page had 40 English reviews. Spotify's 40 reviews came from 10 different versions. Duolingo, Uber and Notion each had 7 versions on the page. The most common version had 16 to 23 reviews, and 4 to 8 reviews had no version at all. The response does not show why.
Spotify's 40 reviews covered only 1.6 hours, Uber's 1.9 hours and Duolingo's 0.5 hours. In that short time, users on 7 to 10 versions wrote reviews. Notion gets fewer reviews, and its 40 reviews covered 99.4 hours. Notion is the one case where we can compare with the store. The Google Play profile showed 0.6.4324, but only 3 of 40 reviews were on that version. The most common version, with 18 reviews, was 0.6.4304.
Real google_play/reviews response (00:27 Singapore time, 2026-11-21): 40 reviews on one page from 10 versions. We removed the author fields. EveryInfra API response screenshot
When you group by version, you can also split the share of low ratings (1 or 2 stars) on Google Play:
| App | Main version | Low ratings on the main version | Low ratings on other versions |
|---|---|---|---|
| Uber | 4.657.10000 | 7 of 23 (30%) | 3 of 17 (18%) |
| Spotify | 9.2.0.2053 | 6 of 18 (33%) | 6 of 22 (27%) |
| Duolingo | 6.106.5 | 2 of 16 (13%) | 3 of 24 (13%) |
Each group has fewer than 25 reviews. These gaps do not show that one version is worse. The numbers show the method that a release board should use. Group the reviews by app_version first. Then look at the low-rating share and keywords for the new version. When the sample is too small, show "not enough data" and do not show a precise-looking percentage.
Many Android versions are live at the same time, because staged rollouts, users who turn off auto-update and builds for different devices add up. Stop rules must use the version, not "the current version".
Public reviews come back more than one day late: 30 to 33 hours on the App Store and about 24 hours on Google Play. On release day, you get almost no reviews of the new version. So reviews cannot be a stop rule for a phased release. They are good for a daily review. For alerts within the hour, use crash rates and your own analytics.
One app in six storefronts: same version, different notes
The App Store works per storefront, which is one country or region. The country parameter of app_store/profile in our catalog says that profile and review data come from the storefront that you choose. An app that is live in one storefront may not be live in another. On November 21, 2026, from 00:29 to 00:30 Singapore time, we read Duolingo in Japan, Germany, Brazil, Singapore and Mexico. With the US read at 00:16, we have 6 storefronts.
| Storefront | Version | Updated (UTC) | Release notes | Ratings (average) |
|---|---|---|---|---|
| United States | 7.149.1 | 2026-11-18 16:14 | 274 characters, English | 5,606,940 (4.72) |
| Japan | 7.149.1 | 2026-11-18 16:14 | 136 characters, Japanese | 782,197 (4.54) |
| Germany | 7.149.1 | 2026-11-18 16:14 | 413 characters, German | 888,394 (4.59) |
| Brazil | 7.149.1 | 2026-11-18 16:14 | 341 characters, Portuguese | 1,182,663 (4.86) |
| Singapore | 7.149.1 | 2026-11-18 16:14 | 274 characters, English, same as US | 53,546 (4.69) |
| Mexico | 7.149.1 | 2026-11-18 16:14 | 329 characters, Spanish | 752,604 (4.83) |
All 6 storefronts showed version 7.149.1 and the same update time, November 18 at 16:14 UTC. In these 6 storefronts at least, one version went live at the same time. So for an app that is already in these storefronts, you usually do not need to track "which countries have this version". Which storefronts list the app at all is a different question, so record it apart. Apple's phased release does not split by country either. The help page has no country option.
The differences are in the notes and the ratings. The same joke about the mascot has 413 characters in Germany, 341 in Brazil and 329 in Mexico. The US and Singapore share one English text of 274 characters. Japan has 136 characters. The Brazilian text starts with a different idea from the US text, so someone rewrote it and did not translate it line by line.
The average rating goes from 4.54 in Japan to 4.86 in Brazil. The rating count goes from 53,546 in Singapore to 5,606,940 in the US, more than 100 times larger. For release notes, a release product must store which text each storefront showed. For ratings, it must keep each storefront apart. A global average is not the feedback of one market.
Did anything change in 50 minutes? The same apps, read twice
A release board must answer one question: which version is live now? We wanted to see how fast the public data changes. So we read the 8 US App Store profiles again at 01:08 to 01:09 Singapore time. That is 48 to 53 minutes after the first read at 00:15 to 00:21.
All 8 apps returned the same version and updated_at both times. No new version went live in that window. The rating counts are the more useful result. WhatsApp showed 18,992,389 both times, Spotify 43,204,131 and Uber 17,314,837. None of the 8 rating_count values changed in 48 to 53 minutes.
WhatsApp has 18.99 million ratings, so it is unlikely that it got zero new ratings in 50 minutes. So the public rating count looks like a snapshot that did not refresh in these 50 minutes. Our data cannot tell how often it refreshes. An hourly read in release week is frequent enough. More frequent reads return the same data and cost more.
Also, "the rating count did not change" does not mean "users did not react". The board must show the snapshot time and our read time. For fast signals, use crash rates and your own analytics. Public reviews and ratings fit a daily review.
| App | First read | Second read | version | rating_count (same both times) |
|---|---|---|---|---|
| 00:15 | 01:08 | 26.45.75 | 18,992,389 | |
| Spotify | 00:15 | 01:08 | 9.2.0 | 43,204,131 |
| Duolingo | 00:16 | 01:08 | 7.149.1 | 5,606,940 |
| Uber | 00:16 | 01:08 | 3.748.10002 | 17,314,837 |
| Notion | 00:17 | 01:09 | 1.7.355 | 90,743 |
| Telegram | 00:17 | 01:09 | 13.2.2 | 286,864 |
| Netflix | 00:20 | 01:09 | 26.6.0 | 7,643,207 |
| Slack | 00:21 | 01:09 | 26.11.30 | 55,765 |
Phased release: Apple's 7-day curve and Google's manual percentage
Apple's rules are on the App Store Connect help page Release a version update in phases. When you choose a phased release, the update goes to users with automatic updates over 7 days: 1%, 2%, 5%, 10%, 20%, 50% and 100%. Users get no notice. You can pause the release for up to 30 days in total, as many times as you want. When you resume, the release continues from the day where it stopped.
The same page gives three limits. First, anyone can download the version by hand from the App Store at any time, so the phases control only automatic updates. Second, if you remove the app from sale, or your developer membership ends, the phased release stops. When the app returns, the version is available to all users at once. Third, to control the pace again, you must make the version unavailable and submit a new version with phased release on.
A third-party comparison gives the same summary. Apple's phased release moves forward by itself over 7 days, and a Google Play staged rollout waits for you (Safeguard comparison, 2026-10-19). The help pages of both platforms say the same.
Google's rules are on the Play Console help page Release app updates with staged rollouts. You can use a staged rollout for updates only, not for the first release. The percentage does not go up by itself. When you halt the rollout, no new users get the version, and users who have it keep it.
When you resume, the same users are in the group. If you start a new staged rollout before the last one reaches 100%, the new one uses the same group of users. When you limit a rollout to some countries, you can add countries later but you cannot remove them. The APKs and Tracks page adds that a committed edit can take several hours to go live.
The page Prepare and roll out a release adds two limits. Internal testing allows 100 testers at most. You cannot create a new release while another release is still in progress, so you must roll it out to 100% or discard it first. If you want a change to go live at a set time after review, turn on managed publishing. Approved changes then wait in "Ready to publish" until you publish them. Personal developer accounts created after November 13, 2023 must also meet the closed testing requirement before they can release to production.
| Control | Apple phased release | Google Play staged rollout |
|---|---|---|
| How the share grows | Fixed 7 days: 1%, 2%, 5%, 10%, 20%, 50%, 100% | You set it; it does not grow by itself |
| Who gets it | Users with automatic updates; manual downloads are open to all | Random new and existing users |
| Pause | Up to 30 days in total, no limit on count | Halt, no time limit in the help page |
| Users who already updated | Stay on the new version | Stay on the new version |
| By country | No country option | Yes; after start, you can only add countries |
| Revert | No; submit a new version | No revert for installed users; ship a higher version code |
| API field | phasedReleaseState on the phased release | status, userFraction, countryTargeting on the release |
One "percentage slider" cannot show both platforms. On Apple, the day sets the share, so the board must show the day, the pause state and the pause days that remain. On Google, a person sets the share. So the board must show the current share, who changed it last and when, and the next planned step.
Automatic increase rules work only on Google. On Apple, you can only pause, resume, or release to all users.
Write stop rules before you submit
Before a phased release starts, write down the watch window, the health metrics, the user segments and the stop rules. Google gives thresholds that you can use directly. The Android vitals page lists user-perceived crash rate and user-perceived ANR rate as core vitals. The overall bad-behavior thresholds are 1.09% and 0.47%. The per-phone-model threshold is 8% for both.
Above a threshold, Play can make the app less visible in the store and can show a warning to users. You can see these numbers on the Android vitals page in Play Console or read them from the Play Developer Reporting API. They work well in automatic stop rules.
iOS has no public threshold of the same kind. Teams often count crashes per version with a tool such as Firebase Crashlytics and set their own limits. If you have no baseline yet, you can start from the Android vitals limits of 1.09% and 0.47%. Then adjust them with the data of your first releases.
| Metric | Overall threshold | Per-model threshold | Source | Use on the release board |
|---|---|---|---|---|
| User-perceived crash rate | 1.09% | 8% | Android vitals | Stop the increase when the new-version group is above it |
| User-perceived ANR rate | 0.47% | 8% | Android vitals | Same as above |
| Excessive partial wake locks | 5% | — | Android vitals | Warning only |
| 1–2 star share in new-version reviews | Team sets it | — | Public reviews grouped by app_version | Warning only; no decision on small samples |
| Key business conversion (sign-in, payment) | Team sets it | — | Your own analytics | The first metric to check |
Keep automatic rules conservative. When there is no data, show "not enough data" and do not read it as zero. When monitoring stops, show "outage" and do not read it as zero errors. If you check only the overall crash rate, you can miss many problems. Examples are a sign-in problem for new users, a start-up crash on old devices, a subscription restore bug or a payment problem in one region.
The board must link the share of users on each version with key business metrics, split by platform, version, region and user group. It must also show how late each metric arrives. Android vitals data appears only when users allow diagnostic data, so the first hours are often empty.
When a serious problem appears, you can pause the phased release, stop further increases, turn off a server-side switch or prepare a fix build. Firebase Remote Config rollouts can turn a feature on for a share of users and roll it back for all or some users. A server-side switch is one of the few rollbacks on mobile that work in minutes, and Remote Config rollouts is one example. Google Play also supports in-app updates with an immediate flow and a flexible flow. A release can carry an inAppUpdatePriority from 0 to 5, so a fix build can ask users of the bad build to update soon.
Neither platform can move installed users back to an old version. So your checklist must have a "server compatibility" item. The API fields, database migrations and settings that the new version needs must also work for the old version while many users still have it. As an example, suppose that you find a problem on day 3 of an Apple phased release and you pause it. At that point, 5% of auto-update users and every user who downloaded by hand already have the new version. If the server already removed an old field, users of the old version will also break.
Tie the checklist to one exact release candidate
"Tests passed" without a build number can point to a different build at release time. Each release candidate needs a fixed snapshot: code revision, build ID, signature or artifact hash, environment, test evidence, store version and key settings. When any key field changes, the old approval becomes invalid or needs a new check. Before submission, you can attach a different build to an App Store Version. So "tie the approval to the build number" is a requirement, not only a good habit. The board must show the build at approval time and the build that is attached now.
The checklist does not need dozens of permanent checkboxes. Keep the items that stop real failures. Check crashes and key flows, permission and privacy statements, and billing or account changes. Check migration compatibility, release notes and support readiness. Check the watch metrics and stop rules for the phased release.
In November 2026, add one more item. Apple's App Store Connect release notes of November 19 add two declarations to the age rating questionnaire. They are Shared Location, and Dating and Relationships. You must answer them when you submit an update, and all apps must answer them by January 12, 2027.
Upload rules are similar. Apple's Upcoming Requirements page says that since April 28, 2026, uploads must use Xcode 26 or later. Since September 9, 2026, iOS and iPadOS apps must target iOS 13 or later. Google Play's target API level requirement also gets stricter each year. These rules can block a submission, so make them automatic checks. You can also list the sections of the App Review Guidelines that your change touches.
Evidence needs an owner and a time. A link to a chat thread that keeps changing does not prove that one fixed candidate passed. The system can collect CI results, build processing state and review state. App Store Connect webhooks can tell your server when a build upload state, a beta build state or an app version state changes. Each app can have up to 10 webhooks. But a person with the right role must still decide whether to accept the remaining risk.
Release notes in many languages need a source and a reviewer
Write release notes from the approved changes, then let the product owner and the localization owner confirm them. Technical commits, user-visible changes and marketing text are three different sets of facts. A database index fix may need no public note. "We improved the experience" cannot replace a clear note about a security fix or a change in behavior.
Keep the source text, the translated version, the reviewer and the character limit for each language. Apple's Platform version information page says that promotional text can have 170 characters and you can change it without a new submission. The description can have 4,000 characters, and keywords can have 100 bytes. A Google Play release holds releaseNotes as a list of texts with BCP-47 language tags.
When a language is missing, follow a team rule. Block the release, use the default language, or exclude the region. Do not copy a machine translation and mark the item as done. After release, store the text that the ...

