Staged rollout monitoring for iOS & Android
Know early whether your new release is safe to roll out further. Appelium spots App Store phased releases and Google Play staged rollouts from live sessions, typically within minutes when your user base gives a clear signal, tracks adoption and compares crash health with your previous release, with statistical confidence instead of guesswork. For apps with only a few users, Appelium falls back to App Store and Google Play release data.
Available in PRO and ENTERPRISE · iOS, tvOS & Android · Hosted in Switzerland
Store dashboards are the slowest signal you have
By the time a store page shows your new version, thousands of users may already be running it.
Store metadata lags behind
Store pages update with a delay of hours, and Google Play can show the new version only once a staged rollout completes, which can take days.
Rollout % is not adoption
A 10% rollout tells you who is eligible, not who is actually running the new version. Real adoption only shows up in real sessions.
Small numbers mislead
Zero crashes in 40 sessions is not the same as zero crashes in 40,000. A simple percentage comparison cannot tell them apart.
How release rollout health works
From the first sessions of a new version to a clear verdict, without any extra integration.
- 1
Detect the rollout
Appelium recognises the sharp rise in sessions that marks a real rollout and separates it from internal testing. A rollout start is only recorded when the signal is clear; otherwise the store release information is used.
- 2
Track adoption
See how quickly the new version spreads among your reported sessions on application cards, Favorites and List view, side by side with every other app in your workspace. Explore the wider usage picture with sessions & active devices.
- 3
Assess crash health
Foreground sessions that ended with a crash are compared with the previous release over the same period, taking the amount of evidence into account before reaching a verdict.
Four levels. One clear answer.
Every current release gets one of four health levels, each with a clear next step.
Not enough clear evidence yet for a verdict, for example when too few sessions or devices have reported.
Next step: let more data arrive and review any reported crashes.
The evidence supports a crash-free session rate of 99.9% or higher across enough reporting devices.
Next step: a reassuring signal. Keep monitoring as adoption grows.
Crash health is below 99.9% across several devices, but no clear deterioration from the previous release is established.
Next step: review the crashes of this release.
The release crashes convincingly more often than the previous release, by a meaningful margin.
Next step: prioritise the investigation and consider pausing the rollout.
Confidence, not just percentages
Two releases can show similar numbers and deserve very different answers. Appelium weighs how much evidence stands behind every number.
| Current release | Previous release | Evidence | Verdict |
|---|---|---|---|
| 100% crash-free | 99.95% | 60 sessions, 25 devices | Gathering evidence |
| 99.96% crash-free | 99.94% | 48,000 sessions, 9,000 devices | Healthy so far |
| 99.7% crash-free | 99.6% | 30,000 sessions, 6,000 devices | Investigate |
| 99.2% crash-free | 99.9% | 25,000 sessions, 5,000 devices | Regression detected |
Illustrative examples. Learn how each level is assessed in the release rollout health documentation.
Built for teams that ship often
Faster than the stores
When the session signal is clear, rollout starts are recognised from live sessions, not from store pages that may lag by hours or days.
Confident, not noisy
No false alarms from a tester installing a build. When the signal is weak, Appelium waits instead of guessing.
Fair comparison
The current release is compared with the previous release over the same period, not with its lifetime crash rate.
Device-aware
Repeated crashes on a single device do not raise an alarm. Problems must affect several distinct devices.
One click to the crashes
Every health badge links straight to the crash-free sessions of that release, ready for investigation.
Private by default
No advertising identifiers and no IP address processing. Your data is hosted and processed in Zürich, Switzerland.
Frequently asked questions
What is staged rollout monitoring?
Staged rollout monitoring means watching a new app version while it reaches a growing share of users, through App Store phased releases or Google Play staged rollouts, so you can spot crash regressions early and decide whether to continue, pause or halt the rollout.
How can Appelium detect a rollout before the store shows the new version?
Appelium watches the sessions reported by each app version. When a real rollout starts, sessions from the new version rise sharply in a way internal testing does not. When the jump is clear, Appelium marks the start of the rollout, typically within minutes; for apps with only a few users it relies on store release data instead. Store pages can lag by hours, and Google Play sometimes shows the new version only after a staged rollout completes.
What if my app has only a few users?
Appelium only marks a rollout start when the signal is clear. If a handful of sessions cannot be reliably told apart from internal testing, Appelium does not guess and relies on the App Store and Google Play release information instead.
Why does a release show "Gathering evidence" even though it has no crashes?
Zero crashes in a handful of sessions is not proof of a stable release. Appelium takes the amount of evidence into account and only reports "Healthy so far" once enough sessions and devices clearly support it.
Does Appelium pause or advance my store rollout automatically?
No. Release rollout health is guidance for your team. You stay in control of your App Store and Google Play rollouts, and one click on the health badge takes you to the crash data of that release.
Which platforms and plans include release rollout health?
Release adoption and rollout health are available for iOS, tvOS and Android apps on the PRO and ENTERPRISE plans, with a 30-day free trial.
Roll out with confidence
Catch crash regressions while your rollout is still small, before they reach all of your users.
You are in a good company - Join over 150 apps!
Over 150 apps in Switzerland choose to use Appelium.
👨💻 Latest content from our Engineering blog:
XPCService
Strongly typed bidirectional communication channel between UIApplication and XCUIApplication with powerful APIs and super fast performance.
More about XPCService
Screen Flow Pattern in UI tests
Robust and scaleable pattern for structuring UI tests. Highly reusable screen verification code with human readable test case code. All flows and interactions statically typed 🙌.
More about the Screen Flow Pattern
SnapshotQuery™
Learn about SnapshotQuery - our latest addition to AppeliumTests which radically improves the performance of your XCUITests while making them more stable and reliable at the same time.
More about SnapshotQuery
Early access and news
Be the fist one to know about all the exciting engineering posts and product announcements.