How to publish an app to the App Store
The part where most AI-built apps stall
Certificates, provisioning profiles, bundle identifiers, TestFlight, review guidelines. Appifex handles the mechanics of App Store and Google Play submission that stop most first-time developers, and the app it submits is one you own.
How to publish an app to the App Store, step by step
Every iOS app reaches the store the same way, whoever built it: a signed build, an App Store Connect listing, and a review. What differs is how much of the signing you do by hand. These are the steps as they run in Appifex; the same seven exist in any toolchain.
Join the Apple Developer Program
Apple requires the publisher of record to be a real, enrolled developer, so this account has to be yours — $99 a year, and no tool can do it on your behalf. Sign the outstanding agreements in App Store Connect while you are there; an unsigned agreement blocks submission later with a confusing error.
Create an App Store Connect API key
In App Store Connect, go to Users and Access, then Integrations, then App Store Connect API, and create a key with Admin access. Download the .p8 file — it is only offered once — and copy the Key ID and Issuer ID. Your Team ID is on your Apple developer account membership page. These four values are what let a build be uploaded without you touching Xcode.
Connect the build service
iOS builds have to be compiled and signed on Apple hardware. Appifex uses Expo Application Services for this, so you create a free Expo account, generate a full-access token, and paste it in. This is also the step that produces Android builds, so it covers both stores.
Set the bundle identifier and version
The bundle identifier is permanent — it is how Apple identifies your app forever, and it cannot be changed after the first submission. Use reverse-DNS form, like com.yourcompany.yourapp. Build numbers must increase with every upload; Appifex increments them for you, which removes the most common cause of a rejected upload.
Build and upload to App Store Connect
Appifex compiles the app, signs it with your certificates, and uploads it. A build takes roughly 15 to 20 minutes and runs in the background, so you can close the page. Apple then processes the binary on its side, which usually adds another 10 to 30 minutes before the build appears in App Store Connect.
Test it through TestFlight
Once Apple finishes processing, the build shows up in TestFlight and you can install it on your own phone and invite testers by email. Do this before submitting for review. Installing your own build is the cheapest way to catch the failures that are embarrassing to be told about — a crash on launch, a screen that renders differently on a real device than in the simulator, a permission prompt you forgot to write a reason for.
Submit for review
In App Store Connect, open the app, select the build, and add the listing: screenshots at the required sizes, a description, keywords, a support URL and a privacy policy. Then click Add for Review. Apple does not publish a guaranteed turnaround, and in practice it ranges from under a day to the better part of a week. If it comes back rejected, Apple names the specific guideline it failed, which makes the fix concrete — and a good share of first rejections are about the listing rather than the app, so read the guideline before you change code.
What you get
Frequently asked questions
How do I publish an app to the App Store?
Seven steps: enrol in the Apple Developer Program ($99/year, and the account must be yours), create an App Store Connect API key, connect a build service that can compile and sign on Apple hardware, set a permanent bundle identifier, build and upload, test the build through TestFlight, then add your listing and submit for review. The mechanics in the middle — certificates, provisioning profiles, build numbers — are where most first-time developers lose days. Appifex does those steps for you and publishes under your own developer account, so the listing, the reviews and the users stay yours.
Will Apple reject an app built with AI?
Apple does not reject apps for being AI-generated; it reviews what the app does. The common rejection reasons are apps that are simply a website in a wrapper, apps with too little functionality, and missing privacy disclosures. Appifex generates genuinely native apps with real backends, which addresses the first two directly.
Do I need my own Apple Developer account?
Yes. Apple requires the developer of record to be the publisher, so the $99/year account must be yours. That is also what keeps the listing, the reviews and the users yours rather than a platform's.
Can I update the app without going through review again?
Often, yes. Appifex apps support over-the-air updates, so changes to your JavaScript and assets reach users without a new App Store review. Changes to native code or app metadata still require a normal submission.
How long does it take to publish an app to the App Store?
Plan for a few days rather than an afternoon, and treat the review itself as the least predictable part. The build takes 15 to 20 minutes, Apple's processing adds another 10 to 30 before the build is testable, and review turnaround is not guaranteed by Apple — it can be under a day or it can be most of a week. The part that reliably consumes time is the listing: screenshots at every required size, a description, a privacy policy and a support URL. Later releases are much faster, and JavaScript-only changes can skip review entirely through an over-the-air update.
How much does it cost to publish an app to the App Store?
Apple charges $99 a year for the Developer Program, and Google charges a one-time $25 for a Play Console account. Those are unavoidable and go directly to the platforms. On top of that you need something that can build and sign the app; Expo's free tier covers most projects. Appifex has a free plan that generates real apps, so the $99 is often the only cost of getting a first app live.
Start from a template instead
Start building now
Turn your idea into a production app in minutes. Free to start.