How to Soft Launch an iOS App
A soft launch limits App Store Availability to a few storefronts so you can watch crashes and the real install funnel, then add countries. It does not game search.
Quick answer
How do you soft launch an iOS app?
Soft launch an iOS app by limiting Availability to a few App Store storefronts after review, watching crashes and the acquisition funnel, then adding storefronts. It is a public listing in those countries, not a private beta and not a way to manipulate search. Metadata in another language is not the same as turning that country on. The page in each live storefront still has to be finished.
On this page
Phrasebook is a language app: a short lesson, a speaking prompt, a streak. You want it on the App Store, but not in every country on day one, because the speech recognizer falls over on older phones and you have only finished English and Spanish metadata. A soft launch is how you do that on purpose. You pass review, you set Availability to a few storefronts, you watch what real installs do, and you add storefronts when the lesson survives.
Availability is the control in App Store Connect for where the app can be downloaded. It is not the keyword field, and it is not a localization. A Spanish keyword set does not put the app on the Spain storefront. Turning Spain on does not translate the screenshots. The launch checklist is still the listing work. This post is only the decision to start narrow. TestFlight, if you still need private cooks, is the external testing guide.
What you are actually limiting
After the app is approved, people in a storefront you left off cannot download it there. People in a storefront you turned on see a normal product page: icon, subtitle, screenshots, price, ratings. They can find it in that store’s search. You are not invisible. You are absent from the countries you did not enable. That is why the page in the countries you did enable has to be finished. A soft launch is a small public launch, not a hidden one.
Pick storefronts where you can read support mail and where the lesson content is honest. For Phrasebook, that might be the country you live in plus one where you already have a teacher who will try the speaking prompt. Do not pick a storefront because a chart looks empty. You will not learn from installs you cannot understand, and you will not learn from a country whose language you have not put on the page.
What you watch before you add countries
Crashes first. A speaking prompt that dies on launch in the one storefront you enabled will die in the next ten. Acquisition second: product page views, installs, and whether people finish the first lesson. If views are healthy and installs are not, the subtitle or the first screenshot is wrong in that language. If installs happen and the first lesson is abandoned, the listing may be fine and the lesson is not. Do not “fix” both in one afternoon and then open twenty countries.
Support mail is part of the funnel. If every note says the microphone permission text scared them, change that string before you expand. If nobody writes because the support URL 404s, you do not have a quiet success. You have a broken required URL. The privacy policy still has to match whatever audio you upload. A narrow Availability setting does not shrink those obligations.
Localization is a different switch
| Control | What it changes | What it does not change |
|---|---|---|
| Availability | Which storefronts can download the app. | The language of the metadata. A country can be on while the page is still English. |
| Localization | Name, subtitle, keywords, description, and screenshots for a language. | Whether that language’s countries are for sale. You can translate and still leave the storefront off. |
| TestFlight | Who can install a beta. | Search, rankings, and App Store Availability. A beta is not a soft launch. |
Soft launch limits storefront Availability. Translating metadata does not turn a country on, and turning a country on does not translate the page.
It is not a search trick
People sometimes soft launch because they think a small storefront is easier to rank in, then flip the rest of the world on and inherit that rank. Apple does not document Availability as a ranking hack, and you should not run Phrasebook that way. Search in a storefront uses the metadata for that storefront. If you have not filled the Spanish keyword field, Spain is not ranking you for English phrases you only entered on the US localization. Read which countries to localize when you choose languages, and ASO with zero downloads when the narrow launch’s problem is the listing. Adding countries multiplies whatever the page already does.
The page in the small set still has to convert
Phrasebook’s first screenshot in each live storefront should be a lesson in progress, in the language that storefront’s metadata uses. If you only have English screenshots, do not turn on a storefront where you are pretending the app is fully localized. AppGrowthKit can frame the lesson UI once the strings exist. Empty speech bubbles and a “coming soon” caption are how a small launch teaches you nothing except that people bounce.
Keywords, subtitle, description, and screenshots still ship with a version. You cannot quietly translate the Spanish subtitle without submitting. Promotional text can change without a binary, and it will not carry the keyword field. If the soft launch is also a pre-order in one region, use the pre-order guide for that region’s dates. Do not mix the date math into Availability and hope they are the same form.
When to add the next storefront
Add a storefront when three things are true: the crash rate on the lesson is something you can stand, a new user can finish lesson one without you in the chat, and the metadata for that storefront is actually written. Add one or a few. Read the same funnel again. A language app that opens forty countries on a Friday because the first country “felt fine” for two days has not soft launched. It has launched, with a delay.
Tell your own audience which countries are live. Apple will not explain your rollout. If a learner in a country you skipped emails that the app will not download, that is Availability working. Point them at the storefronts you support, or turn theirs on when the lesson is ready. Do not turn it on to stop one email and then discover the speech prompt crashes on the devices that country actually uses.
Soft launch Phrasebook
Review first, then a short Availability list, then evidence, then more countries. Do not expand because a calendar said launch week is over.
Finish the page for the storefronts you will enable
Write the name, subtitle, keywords, description, and screenshots in the languages those storefronts will show. Click the support URL and the privacy policy. Capture the lesson from the build you are submitting. If Spanish metadata is not done, Spain stays off even if you like the idea of a Spanish soft launch. A live English page in a country you cannot support is not a test. It is a support queue.
Submit and set a short Availability list
Get through App Review with the real binary. In Availability, enable only the storefronts on your list. Confirm a phone whose App Store is set to a disabled country cannot see a download, and a phone in an enabled country can. That check takes ten minutes and prevents the “we thought it was global” surprise. Pricing should be something you are willing to charge in those countries, not a placeholder you meant to edit later.
Watch crashes and the first lesson
For the next stretch of real use, read crashes on the speaking prompt and whether installs finish lesson one. Keep a note of support mail in the language of that storefront. If the page gets views and almost no installs, change the first screenshot or the subtitle in a version, not the country list. If installs finish the lesson and crashes stay quiet, you have a reason to add a storefront. Two quiet hours are not that reason.
Localize before you expand into that language
Prepare the next storefront’s metadata and screenshots before you flip Availability. Shipping English keywords into a storefront and calling it localized will not tell you how that market searches. The country decision and the language decision are two edits. Do both, in that order: strings first, then the storefront. Leave promotional text for news. It will not translate the keyword field for you.
Add storefronts in small batches
Turn on the next few countries only after the lesson and the page for them are ready. Watch the same crash and funnel signals. Stop expanding if the new storefront’s mail says the lesson assumes a different language than the one you shipped. Phrasebook is done soft launching when you are willing to support every storefront that is on, not when a spreadsheet of countries is full. The public app in those countries is the product. Treat it that way.
Key takeaways
- A soft launch limits Availability to a few storefronts, then adds more after you read crashes and the install funnel.
- Those storefronts are public. The product page there has to be finished.
- Localization does not turn a country on. Availability does not translate the metadata.
- It is not a search-ranking trick, a TestFlight group, or a pre-order.
- Expand when the lesson survives, not when the calendar looks empty.
Frequently asked questions
Does a soft launch hide the app from search?
Only in storefronts you did not enable. In a storefront you turned on, Phrasebook is a normal listing and can appear in that store’s search. Availability is not a stealth mode and not a documented way to manipulate rank. If you wanted private users, use TestFlight. If you wanted the page public before release day, that is a pre-order, with its own date window. Soft launch starts after the app is approved and on sale in a short list of countries.
If I localize Spanish, is Spain included?
Not by itself. A localization fills Spanish fields: name, subtitle, keywords, description, screenshots. Availability decides whether the Spain storefront can sell the app. You can translate and keep Spain off. You can also turn Spain on while the page is still English, which is usually a mistake for a language app. Do both steps on purpose. The guide to which countries to localize is about the language work. This guide is about the storefront switch.
Can I soft launch to learn keywords with no competition?
You can learn how your real page converts in a storefront you support. You should not pick a country because you hope its search is empty and that rank will follow you worldwide. Metadata is per localization. A keyword you never entered for that storefront will not be why you got installs. If downloads are zero, fix the listing in the countries you already have. Opening more countries copies the same page to more people.
How many countries should the first wave include?
Apple does not publish a required count for a soft launch, and this guide will not invent one. Use as many as you can support with a finished page, crash watching, and support mail you can read. For Phrasebook that is often your home storefront plus one where the lesson language is real. Add more when lesson one completes and crashes are understandable. A single storefront is a valid soft launch. Forty storefronts on day one is a full launch.
Do I still need TestFlight if I am soft launching?
Use TestFlight before review if cooks or learners who are not on your team should try a broken build in private. Soft launch cannot do that, because the storefronts you enable are public. Many language apps do both: external TestFlight until the speaking prompt works, then a short Availability list on the store, then more countries. Neither step fills in the privacy label, the support URL, or the screenshots. Those still have to match the lesson you ship.
Keep reading
ASO When Your App Has Zero Downloads
With no download history, the name, the keyword field, and the first three screenshots do all the work. Pick a query you can deserve. Do not buy the rest.
TestFlight External Testing Before Launch
External TestFlight is how people who are not on your App Store Connect team install a recipe app before it is public. The first build still goes through Beta App Review.
App Store Pre-Orders Before Launch Day
A pre-order publishes a limited product page before the binary is public. The screenshots and metadata have to be ready, because that page is what people order from.
Which Countries to Localize an App First
Do not translate every storefront on day one. Start where you can support people and where search is not already in your language.
App Store Launch Checklist: From Screenshots to First Users
A practical launch plan for indie app developers: get your listing compliant, make screenshots convert, recruit useful early feedback, then improve with evidence instead of post-launch guesswork.
Free tools that help here
Top App Store Apps
Track Apple App Store top charts across 30 countries. View top free and paid rankings for ASO research - updated from Apple's public RSS feed.
ASO Character Counter
Count characters for every App Store and Google Play metadata field against exact store limits. Live counts and over-limit warnings - nothing gets truncated at submission.
Screenshot Beautifier
Add polished backgrounds, padding, shadows, and rounded corners to any screenshot in seconds. Perfect for social posts, docs, and portfolios.
The small-country page is still the page
AppGrowthKit builds the language-lesson screenshots for the storefronts you turn on, so a soft launch is not a placeholder listing.
Try AppGrowthKit for Free