How to Launch a Mobile App for Free: Choosing a Store and Sequencing Both
Launching a mobile app for free is possible only in part: your promotion costs nothing, but both major stores charge or verify you before you can publish. Choose one store first based on where your users are, use its test track as a rehearsal, publish a web version or page for everyone else, and add the second store once the first one retains people.
What does free actually cover on mobile?
Be honest about this on day one, because it shapes the plan. The two big stores are not free to publish on. Apple’s developer program page, read on 13 November 2026, lists a $99 annual membership, and says a free Apple developer account gives you tools such as Xcode betas while the membership is what opens distribution. Google’s Play Console help page, read the same day, describes a one-time registration fee and an identity check, with extra testing steps for personal accounts.
What is free is everything around the store: a landing page, a launch board listing, outreach, a beta with friends, a web version. Treat the store fee as the one unavoidable cost, not as a reason to skip planning. If it is out of reach this month, the web-first section below covers a route that costs nothing.
Which store should you ship first?
| If your users are... | Start with | Why |
|---|---|---|
| Mostly in a market or industry where iPhones dominate, or you sell to designers and professionals | iOS | The people you can reach in your first month are on it; see the iOS playbook |
| Broad, price-sensitive or in regions where Android dominates | Android | Reach is the point; see the Android playbook |
| Unknown | Whichever you can test on a phone you own | A device in hand shortens every bug fix |
| Using the app on a desktop too | A web app first | One build serves everyone; see the web app playbook |
If your own friends are your first twenty users, pick the platform they carry. Nothing about launching is faster than watching someone you know install it on a phone you can see.
How can the test tracks double as a launch rehearsal?
Each store runs a staged path before the public release, and both are worth using on purpose. Apple’s TestFlight page says you can invite up to 10,000 external testers, after your first build has been approved by App Review for TestFlight. Google’s Play Console help says a personal developer account created after 13 November 2023 must run a closed test with at least 12 testers opted in for 14 days before applying for production access. Whether or not a rule forces you, treat the test period as your soft launch.
- Recruit testers from the same groups you plan to launch to, so the feedback matches your market.
- Release a build every few days during the test and write the changes in plain language, as the changelog template shows.
- Watch where testers stop: onboarding, a permission prompt or a paywall.
- Keep testers informed, since they become your first reviews and your first word of mouth.
What if you cannot pay a store fee yet?
Ship the product as a web app that works well on a phone, and let people add it to their home screen if the browser supports it. You lose store discovery and some device features, and you keep a free launch, instant updates and a way to learn whether anyone wants the product before you pay for distribution. When people use it every week, the store fee becomes an easy decision.
The same applies if your app is mostly a wrapper around a website. Apple’s review guidelines tell developers an app should include features beyond a repackaged website (guideline 4.2), so a thin wrapper may be turned down. Better to launch the web version and add native features that genuinely need the phone.
What does a six-week sequence look like?
- Weeks 1 to 2: build the first-run flow and the one feature that makes the app worth keeping. Create the developer account for your first store now, since verification can take time.
- Weeks 3 to 4: run the store’s test track with people from your market. Prepare the listing text, icon and screenshots using the app store launch checklist.
- Week 5: submit for review, and put a page for the app on the free launch board with the web or store link, so there is a public address on day one.
- Week 6: release, answer every review and message, and decide from retention whether to do the second store.
Read each store’s policy pages before you submit, because review outcomes depend on details that change. The guide to publishing on the App Store and the one for Google Play go further.
What should you measure in the first month?
Installs flatter you; opens on day seven tell the truth. Count people who installed, people who completed the first task, and people who opened the app a week later. A low first-task rate points at onboarding. A good first-task rate and weak return points at a product that does its job once and gives no reason to come back. The launch metrics checklist has a layout for the numbers, and the mobile app ideas guide and the board’s productivity ideas offer starting points.
Frequently asked questions
Can I publish a mobile app without paying anything?
Not on the two major stores. Apple lists an annual developer membership and Google describes a one-time registration fee, both read on their own pages on 13 November 2026. A web version or an installable web app costs nothing to publish and is a sensible way to learn whether people want the product first.
Should I build for iOS or Android first?
Choose the platform your first users carry, and test on a phone you own. If you are unsure, build a web app first and see which devices visitors use. Starting with one store lets you finish and learn; starting with two doubles the review, testing and support work.
Do I need a beta before I launch a mobile app?
You need a test of some kind, and a store may require one: Google asks personal accounts created after November 2023 for a closed test with at least 12 testers over 14 days. Apple’s TestFlight is optional but useful. Treat the test period as a rehearsal with real people from your market.
How do I promote a mobile app for free?
Give it a public page on a free launch board, post in communities where the problem comes up, ask beta testers to review it and share short clips of the app in use. Tag each link. Paid ads are optional, and nothing free promises installs, so measure what each place sends.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.