The three terms are often mixed up. They answer different questions and sit at different points of a release.
What each one is
Closed test. A test with a limited, invited audience. On Google Play, closed testing is one of several test tracks. According to the Play Console Help page (retrieved 2026-10-23), testers need a Google or Google Workspace account, and test feedback does not affect your public rating. The page also states that you must test your app before releasing it to production.
Staged rollout. A production release that reaches only part of your users first, then more over time. This is a release control, not a test audience you invite. Per the Play Console Help on staged rollouts, you choose the percentage and can increase it over time, it does not increase automatically, and you can halt the rollout so no further users receive that version (users who already have it keep it).
Soft launch. A public release limited to one country or a small market, to see real behaviour before a wide launch. It is a business decision, not a store feature in itself.
Comparison
| Closed test | Staged rollout | Soft launch (one country) | |
|---|---|---|---|
| Audience | Invited testers | A share of your real users | Real users in one market |
| Public? | No | Yes, it is the production release | Yes |
| Main question | Does it work for people other than me? | Is this release safe for everyone? | How does it perform in a real market? |
| Typical signal | Written feedback, crash reports | Crash and error rates as the share grows | Retention, conversion, reviews |
| Your control | Who is invited | The percentage | The country selection |
| Can ratings be affected | Test feedback does not affect your public rating (per the page) | Yes | Yes |
Which fits when
- Before your first public release: closed test.
- Every later update: a staged rollout limits the damage if something slipped through.
- You need market data, not bug reports: soft launch.
- They combine: closed test, then a limited production release.
Closed test requirements on Google Play
Google's Help page says developers with personal accounts created after November 13, 2023 need a closed test with at least 12 testers opted in continuously for 14 days before applying for production access. A tester who opts out and back in does not carry over earlier time. AppReviewX test groups cover this for Android apps. Policies change, so check the current Play Console Help yourself.
Related: all testing options, QA freelancer vs peer testers, in-app feedback vs email vs survey, and the article Google Play internal, closed and open testing.