How to Ship an App in 2026
Shipping an app in 2026 is a fixed sequence, not a mystery: register your developer accounts, produce a signed release build, add the legal pieces the stores now require (a privacy policy, in-app account deletion, and an AI consent notice if you send user data to a model), upload your store assets, then clear each store's review gate. Apple's App Review is usually one to two days. A new Google personal account must also pass closed testing, 12 testers for 14 straight days, before production. Do these in order and you go live on both stores.
This is the capstone guide for the whole journey. If you have an idea and a build, this page is the map from "it works on my phone" to "it is live and people can download it." Every stage below links to a deeper guide, because each one has its own traps. We shipped a real app through this exact path, SparkQuest, an AI idea generator, and we got rejected once on the way. The scars are in here on purpose. They are the parts nobody writes down.
The Ship-It Path (the whole journey, in order)
Here is the spine. Walk it top to bottom. Each link goes to the guide that covers that stage in full.
- Validate before you build. How to validate an app idea and idea to App Store in 30 days cover the front half. Do not ship a thing nobody asked for.
- Build it. Build an app with AI in 2026 covers the tools and the flow.
- Wire the money. RevenueCat and Expo setup, start to finish, and if you are choosing a processor, Stripe vs RevenueCat vs Lemon Squeezy.
- Cut the release build. Ship an Expo app with EAS Build and Submit is the cloud-build pipeline with no Xcode.
- Pass review (APPROVE). Why apps get rejected in 2026, add account deletion to pass App Review, get an AI app approved by Apple, and for Android, Google Play closed testing: 12 testers, 14 days.
- Make the listing assets. App Store screenshots that convert, screenshot sizes and specs for 2026, and app preview videos that convert.
- Beta and launch. TestFlight beta testing, step by step and the Product Hunt launch playbook.
- Grow. App Store Optimization in 2026, app analytics for indie developers, and how to get your first 100 app users.
That is one stop. The rest of this page walks the same path with the detail you need to actually move.
Step 1: Register your developer accounts
You cannot ship without them, and one of them has a hidden clock, so start here on day one.
Apple Developer Program: 99 dollars a year. This is a recurring annual fee. If it lapses, Apple can pull your live app until you renew, so treat it as a standing cost, not a one-time purchase. Enrollment can take a day or two for identity verification, longer if you enroll as an organization with a D-U-N-S number.
Google Play Console: 25 dollars, once. No annual renewal. But if your personal account was created after November 13, 2023, you inherit the closed-testing requirement (Step 6 below), and that costs you 14 calendar days you cannot compress. Organization accounts are exempt. This single fact should change your order of operations: create the Google account and start its testing clock before you think you need it.
Both stores take a commission on in-app purchases, 15 percent for developers under one million dollars a year in the small-business tiers, 30 percent above. Verified July 2026.
Step 2: Produce a signed release build
A debug build off your laptop will not pass review and often will not even upload. You need a signed, production-configured binary: an .ipa for Apple, an .aab for Google.
If you are on React Native and Expo, do not fight Xcode and Android Studio locally. Use EAS Build, which compiles in the cloud and hands you both binaries, then EAS Submit to push them to the stores. Our full pipeline, including the version-pinning that stops the build from breaking, is in ship an Expo app with EAS Build and Submit. The short version: define your eas.json profiles, keep your native versions pinned, and let the cloud do the compiling.
One hard-won note from our own build log: version drift between your React Native renderer, Reanimated, and your Gradle pin will fail a build in ways the error message will not explain. We froze a known-good set of versions and called it the gospel. Do not upgrade native dependencies the week you are trying to ship.
Step 3: Add the legal pieces review now demands
This is where 2026 differs from 2022, and where most first-timers get rejected. Three items are effectively mandatory before you submit.
A privacy policy and a support URL. Both stores require a reachable privacy policy. If you collect anything, say what and why.
In-app account deletion. If your app supports account creation, Apple requires that a user can start deleting their account from inside the app, under guideline 5.1.1(v). This has been enforced since June 30, 2022, and it is still one of the most common rejection lines in 2026. It is not enough to let people deactivate or email support. The full requirement, and the code, is in add account deletion to pass App Review. We know this one first-hand: it is half of why we got rejected.
An AI consent notice, if you send user data to a model. As of the June 8, 2026 guideline update, if your app shares personal data with a third-party AI provider you must disclose it and get explicit permission first, naming the provider. If your app touches a model, read how to get an AI app approved by Apple before you submit.
Step 4: Wire and test your monetization
If you charge money, the payment path is part of what review checks, so it has to actually work in the review build.
For a mobile app, RevenueCat is the common source of truth for in-app purchases across both stores. Our complete setup, including the platform-specific keys and the bug that cost us days (packages coming back empty because the products were not yet approved in App Store Connect), is in RevenueCat and Expo setup, start to finish. If you are still choosing a processor, Stripe vs RevenueCat vs Lemon Squeezy lays out which one fits mobile, which fits web SaaS, and which handles tax as merchant of record.
Set your prices deliberately, not by gut. Weekly plans convert far better than annual for most indie apps, and a clean three-tier structure earns more than a single price. We priced our own tiers around that data, and the reasoning is in how to price your app.
Step 5: Build your store assets
Your screenshots do more selling than your description. The first three screenshots drive most of the install decision, and their caption text is now indexed by search, so they are ranking surface as well as sales surface. The narrative order and the caption rules are in App Store screenshots that convert, the exact 2026 dimensions are in screenshot sizes and specs for 2026, and if you want a preview video, app preview videos that convert has the cut that lifts installs.
One honest warning we learned building our own listing: overlay captions that make a money claim, like a big "10K a month" promise stamped on a screenshot, are a review risk. Descriptive captions that show what the app does are safer and convert about as well.
Set up the store listings themselves
Assets are the images. The listing is everything around them, and both stores make you fill it in before review. Budget about an hour per store.
On Apple, in App Store Connect: app name and subtitle, the keyword field, description, promotional text, category, age rating, privacy policy URL, support URL, and the App Privacy questions that describe what data you collect and share. Those privacy answers have to match what your app actually does, and a mismatch is its own rejection line under 5.1.2.
On Google, in Play Console: title, short and full descriptions, the feature graphic, the content rating questionnaire, and the Data safety form, which now includes the account and data deletion questions covered in add account deletion to pass App Review. Fill the Data safety form honestly and completely, because an incomplete or contradictory form stalls the whole submission.
Keep the two listings consistent with each other and with the build. Your name, your core promise, and your data disclosures should read the same on both stores and match what a reviewer sees when the app opens.
Step 6: Clear the review gates
This is the wall. Both stores have one, and they are not the same shape.
Apple, App Review. After you submit, a reviewer opens your app and checks it against the guidelines. Turnaround is usually 24 to 48 hours. The rejections that actually recur are guideline 2.1 (the app was incomplete, crashed, or the reviewer could not get in), 4.3 (spam or a thin wrapper with no real value), and 5.1.1 (data and privacy, most often the missing account deletion). Each one, with the exact fix, is in why apps get rejected in 2026.
We got rejected under 5.1.1 for two things at once: no in-app account deletion, and an OAuth login that opened in an external browser instead of an in-app authentication sheet. We fixed both, resubmitted, and went live. That whole story, told straight, is in the rejection guide.
Google, closed testing then production. For a new personal account, this is the slow gate. You must run a closed test with at least 12 opted-in testers for 14 consecutive days before you can request production access. The number dropped from 20 to 12 on December 11, 2024, but a lot of the internet still says 20. The current rule, who it applies to, and how to actually pass it (real engagement, not just a headcount) is in Google Play closed testing: 12 testers, 14 days. This is why we shipped Android first: start the 14-day clock as early as you can.
Step 7: Beta, then launch
Before the public build, put it in front of real testers. On iOS that is TestFlight, up to 10,000 external testers, with a lighter Beta App Review on the first build. The setup, the 90-day build expiry, and public links are in TestFlight beta testing, step by step.
When you go live, launch on purpose, not by accident. A launch playbook, honest about what a top finish actually takes, is in the Product Hunt launch playbook. We wrote our own launch plan before we shipped; having the assets and the sequence ready made launch day calm instead of frantic.
Step 8: Grow
Live is the start, not the finish. The store's own search is your biggest free channel, and in 2026 it ranks on more than keywords: your screenshot caption text is OCR-indexed, intent matching is smarter, and retention and stability now feed your ranking. The full playbook is in App Store Optimization in 2026. To know what is actually working, wire free-tier analytics that answer the only early questions that matter, activation, retention, and which channel converts, covered in app analytics for indie developers. And for the cold-start problem every new app has, how to get your first 100 app users covers where real early users come from.
How long each stage actually takes
The biggest planning mistake is treating "ship" as a single day on the calendar. It is a sequence, and the stages have very different clocks. Here is the honest spread for a solo builder.
- Developer accounts: a few minutes to sign up, then up to a day or two for identity verification. Do this first.
- Release build: minutes to hours once your config is stable. A cloud build with EAS finishes in the tens of minutes. The time sink is not the build, it is fixing version mismatches the first time.
- Legal pieces: an afternoon. Privacy policy, account deletion, and an AI consent notice are small, bounded jobs if you do them on purpose instead of discovering them at rejection.
- Store assets: a day or two to do screenshots and copy well, since they carry most of the selling.
- Apple App Review: usually 24 to 48 hours per submission. Add one more round if you get rejected.
- Google closed testing: 14 consecutive days, non-negotiable, for a new personal account. This is the long pole.
Read that list and the strategy writes itself: the two things you cannot compress are Apple's review rounds and Google's 14-day test, so start both as early as you can and do everything else in parallel while those clocks run.
What it costs, all in
The store fees are the small part, and worth stating plainly so you can budget honestly.
- Apple Developer Program: 99 dollars a year, recurring. Let it lapse and your live app can be pulled until you renew.
- Google Play Console: 25 dollars, one time, no renewal.
- Store commission on in-app sales: 15 percent for most small developers under one million dollars a year, 30 percent above that, on both stores.
Everything else is optional and situational: a domain for your privacy policy and support pages, a backend if your app needs one, and any paid tools you choose for analytics or testing. But the hard floor to have a live app on both stores is 99 dollars plus 25 dollars. Verified July 2026.
iOS and Android are not the same shape
People assume the two stores are mirror images. They are not, and knowing the difference saves you a week.
iOS is fast to review, strict on rules. App Review is a human opening your app, usually within a day or two, checking it against the guidelines. The friction is qualitative: account deletion, no thin wrappers, AI consent, no crashes. Clear the rules and you are through quickly.
Android is slow to first release, then loose. For a new personal account, the 14-day closed test stands between you and production no matter how good your app is. But once you clear it, future updates ship without that gate. The friction is a clock, not a checklist.
That asymmetry is exactly why our launch order was Android first, then iOS. Start the Android clock, use those two weeks to finish and submit iOS, and both go live near the same time instead of one waiting a fortnight on the other.
What actually goes wrong (from shipping our own)
Three things, in order of how much time they cost us.
First, native version drift broke builds that had nothing wrong with the app code. We solved it by freezing a known-good version set and refusing to touch it near a ship date.
Second, review rejected us on 5.1.1 for the account-deletion and external-browser issues. Both were a day of work to fix once we understood the exact requirement, and zero days if we had known before submitting. That is the entire reason the APPROVE guides above exist.
Third, the slow lane is Android's testing gate, not iOS review. The 14-day clock is real calendar time you cannot buy back. Start it early.
Start with something worth shipping
The fastest way to waste all of the above is to ship an idea nobody wanted. Before you build, it is worth a few minutes to pressure-test the concept against real demand. Our generator scores an idea against market signals and hands back a build-ready blueprint, so the thing you carry through this whole path is at least worth carrying. Generate and grade an idea free, then come back here and ship it.
The path does not change. Accounts, build, legal, money, assets, review, launch, grow. Follow it in order, respect the two gates that actually cost time (App Review and the Android 14-day test), and you will be live on both stores.
Questions from the field
- How do you publish an app in 2026?
- Register your developer accounts (Apple 99 dollars a year, Google 25 dollars once), produce a signed release build, add the required legal pieces (privacy policy, in-app account deletion, and an AI consent notice if you send data to a model), upload store assets, then clear each store's review gate. On iOS that is App Review, usually one to two days. On Android a new personal account must also pass closed testing with 12 testers for 14 straight days before production. Do those in order and you go live.
- How much does it cost to publish an app?
- The store fees are small: Apple charges 99 dollars a year for the Apple Developer Program, and Google charges a one-time 25 dollars for a Play Console account. Both take a commission on in-app sales, 15 percent for most small developers and 30 percent above one million dollars a year. Verified July 2026.
- Is it faster to ship on iOS or Android?
- iOS review is faster in raw hours, typically 24 to 48 hours. But a new Android personal account carries a 14-day closed-testing gate before you can even request production, so Android is slower to first release for most solo builders. We shipped Android first for that reason: start the 14-day clock early while you finish iOS.
- What gets an app rejected the most?
- The rejections that actually recur are guideline 2.1 (incomplete or crashing on review), 4.3 (spam or a thin wrapper with no real value), and 5.1.1 (data and privacy, most often a missing in-app account deletion). All three are fixable before you submit. We hit 5.1.1 on our own app and cleared it on resubmission.