How to Publish an App to the App Store in 2026: Full Guide

How to Publish an App to the App Store in 2026: Full Guide

How to Publish an App to the App Store: The Short Answer

Last updated: September 17, 2026. Published: September 17, 2026. Apple's fees, review times, listing limits, and store rules in this guide were re-checked against Apple's own documentation on that date.

Publishing to the App Store is the same process whether you wrote the app by hand or built it with AI: enroll in the Apple Developer Program, create the app in App Store Connect, prepare the listing, upload a build, submit it for review, and release it. Apple controls distribution, so there are steps nobody skips, whatever tool made the app.

Quick answer: To publish an app to the App Store, enroll in the Apple Developer Program for $99 a year, create your app in App Store Connect, add the listing details, screenshots, and privacy answers, upload your build, and submit for review. Apple says "On average, 90% of submissions are reviewed in less than 24 hours." You can reach this point without coding by using an AI app builder such as Superapp, which generates the native Swift build, compiles it on Macs in the cloud so you do not need one, and prepares the submission details, or a visual builder such as FlutterFlow, Adalo, or Bubble (disclosure: Superapp is our product). The Apple account and the review are yours either way.

What Apple requires, whatever tool you used: a paid Apple Developer Program membership ($99 a year), an app record in App Store Connect under your own account, a complete listing with screenshots, accurate App Privacy answers, an uploaded build, and a pass through App Review. Superapp, FlutterFlow, Adalo, Bubble, and hand-written Xcode projects all arrive at the same five requirements.

What You Need Before You Start

A free Apple Account is enough to test on your own device but not to publish. Apple's limits on a free account are specific: "You can register up to 3 devices, which expire after 7 days," and the provisioning profiles that let an app run "will expire 7 days from issuance."

How Long Does Publishing Take, Start to Finish?

A realistic first-timer schedule is one week: build finished on day one, enrollment approved by day two, listing and privacy answers on day three, TestFlight on days four and five, submission on day six, live on day seven. Rejections add a day or two each.

Step 1: How Do You Enroll in the Apple Developer Program?

Apple's membership is the entry fee for distribution. It is "99 USD per membership year, or in local currency where available," it covers unlimited apps, and Apple states that it lets you "reach customers around the world on all Apple platforms," with the App Store making it "easy for users in 175 regions to discover and download your apps," plus "unlimited hosting and bandwidth, even for free apps."

Individual or organization? This choice is permanent in practice, and it changes the name buyers see.

Apple is blunt about the paperwork: "Your organization must have a D-U-N-S Number so that we can verify your organization's identity and legal entity status," those numbers are "free in most jurisdictions," and "If you're enrolling as an individual, you don't need a D-U-N-S Number." Apple does not accept "DBAs, fictitious businesses, trade names, or branches" as organizations, and sole proprietors are told to enroll as individuals. Enrollment is open in "more than 220 countries or regions."

Time it right. Individual enrollment can finish the same day. Organization enrollment waits on Dun & Bradstreet: Apple says to "allow up to 5 business days to receive your number from D&B" and up to two more business days for Apple to receive the information. Start this before you finish the app, not after.

Enrollment rule: Enroll as an individual unless the app belongs to a company that already exists as a legal entity. The build route, Superapp, FlutterFlow, Adalo, or Xcode, does not change the enrollment, and the $99 covers every app you publish that year.

Step 2: How Do You Get a Build to Upload?

App Store Connect accepts a compiled build, not source code, not a website. How you produce one depends on your route.

Three details decide whether the upload works the first time:

1. Bundle ID. A reverse-domain identifier such as com.yourname.runclub. It must match between the build and the App Store Connect record, and you cannot change it after the app is created.
2. Version and build numbers. The version is what users see (1.0). The build number must increase with every upload, even for the same version.
3. Signing. Distribution certificates and provisioning profiles sign the build. Xcode's automatic signing handles most cases, and tools that build for you handle it on their side.

AI Founder Kit's teardown of a Superapp export makes the point that a generated project is a normal Xcode project: "We opened this in Xcode 15 and it compiled without any syntax errors or missing dependencies." That is what matters at this step: a build Apple's pipeline will accept, from whichever tool produced it.

Step 3: How Do You Create the App Record in App Store Connect?

App Store Connect is Apple's portal for submitting and managing apps. Creating the record takes minutes:

1. Sign in at App Store Connect with the Apple Account tied to your membership. Superapp, FlutterFlow, and Xcode all deliver builds into this same record, so create it before you upload anything.
2. Go to Apps, then the add button, then New App.
3. Choose the platforms, enter the app name, pick the primary language, select the bundle ID you registered, and set an SKU (any internal reference string).
4. Choose user access, usually Full Access for a solo developer.

The app name here is the one users see, and Apple's limit applies: "The name must be at least two characters and no more than 30 characters." You can edit it until you submit, and after that only when a version is editable.

Two mistakes to avoid at this step: registering a bundle ID that does not match your build, which forces you to start the record again, and reserving a name you have not checked in App Store search, which risks a duplicate-name rejection.

Step 4: How Do You Prepare the App Store Listing?

The listing is what decides whether approved turns into downloaded, and Apple gives exact limits.

Apple's own guidance for these fields is worth following literally:

• Name: "Choose a simple, memorable name that is easy to spell and hints at what your app does. Be distinctive. Avoid names that use generic terms or are too similar to existing app names."
• Subtitle: "Avoid generic descriptions such as 'world's best app.' Instead, highlight features or typical uses of your app that resonate with your audience."
• Description: "The first sentence of your description is the most important", because it is what people read before tapping to expand.
• Keywords: "Consider the trade-off between ranking well for less common keywords versus ranking lower for popular terms." Apple also notes your app is already searchable by app name and company name, so do not repeat them in the keyword field.

Listing rule: Write the name, subtitle, and first description line before you submit anything, because 30 characters forces clarity. Superapp prepares these assets alongside the build; in App Store Connect you can edit every one of them before review.

Step 5: How Do You Complete App Privacy and the Age Rating?

Apple will not accept a submission without privacy answers, and wrong answers are a common rejection.

Two rules keep this simple. Declare what the app actually does, including anything a third-party library collects on your behalf. And keep the privacy policy page reachable: both stores require a working link, and Google states its policy must be on "an active, publicly accessible and non-geofenced URL (no PDFs)."

Step 6: How Do You Upload the Build?

The build has to reach App Store Connect before you can attach it to a version.

After the upload, Apple processes the build for a few minutes to an hour. Two things commonly stall here: missing export compliance answers (Apple asks whether your app uses encryption, and most apps answer that they only use standard HTTPS), and an invalid build number, which must be higher than every build you have uploaded before.

Step 7: Should You Run a TestFlight Beta First?

Yes, for anything you plan to charge for or show to strangers. TestFlight is free with the membership, and its rules are fixed.

A useful beta for a first app is small: five to ten people, one week, one instruction. Ask them to complete the app's main task and to tell you where they stopped. Then test the money path yourself, a sandbox purchase, a cancel, and a restore, because broken purchases are a rejection and a refund problem at the same time.

Step 8: How Do You Submit for App Review?

In App Store Connect, attach the build to the version, complete every red field, and press Add for Review, then Submit.

What to include so a reviewer does not send it back:

• A demo account. If your app has sign-in, give a working username and password in App Review Information. Missing credentials is one of the most avoidable rejections.
• Notes for the reviewer. Explain anything unusual in one paragraph: hardware you cannot ship them, a region lock, a feature that needs data.
• Contact details. A real phone and email.
• Accurate screenshots. They must show the app as it is now.
• Working links. Support URL, marketing URL, privacy policy.

Apple's average is fast: "On average, 90% of submissions are reviewed in less than 24 hours." Apple also warns that "If your submission is incomplete, review times may be delayed or your submission may not pass." Around the holidays, Apple publishes a notice each year that reviews "may take a bit longer to complete" for several days in late December.

Submission rule: Submit a small, complete app rather than a large, half-finished one. A four-screen app that works clears review faster than a ten-screen app with a broken sign-in, whether Superapp, FlutterFlow, or Xcode produced the build.

Step 9: How Do You Release the App After Approval?

Approval and release are separate. In App Store Connect you choose one of three:

1. Automatic release. The app goes live as soon as it is approved.
2. Manual release. You press the button, which is how you line a launch up with an announcement.
3. Scheduled release. You set a date and time.

For updates, there is a fourth option, phased release, which Apple describes as releasing "gradually over 7 days" to users with automatic updates on. The schedule is fixed: 1% of users on day 1, then 2%, 5%, 10%, 20%, 50%, and 100% on day 7. Apple adds that "During phased release, you may pause the release for up to 30 days, with no limit on the number of pauses," which is how you stop a bad update from reaching everyone.

First releases do not use phased release. Use manual release for a first launch so nothing goes live while you are asleep, and keep your builder open, Superapp, FlutterFlow, or Xcode, in case day one turns up a fix worth shipping.

How Do You Publish an App to the App Store Without Coding?

You can publish a custom app without writing code. What no tool removes is Apple's side: the $99 membership, your own developer account, and App Review. What tools remove is the code and most of the build-and-upload friction.

The practical difference between these is not whether you can publish, it is what you hand over if the app grows. Superapp and FlutterFlow give you code. Adalo, Glide, and Bubble keep the app on their platform, which is fine until you need a developer.

Can a Tool Handle the Entire App Store Submission for You?

Not the entire thing, and any tool claiming otherwise is overstating it. Apple requires the app to be submitted under a real Apple Developer account and to pass review, and no third party bypasses either.

Here is the honest division of labor:

That last row is what non-developers underestimate and what AI builders genuinely changed. Greg Kowalczyk, a mechanical engineer who shipped two iOS apps with no coding background, was rejected "39 times total, across technical issues, compliance requirements, UI guidelines, privacy policy gaps, and incomplete feature requirements." His loop: "copy the rejection message → paste it into Cursor or ChatGPT → get a specific explanation of what Apple requires → implement the fix → rebuild → resubmit." His verdict: "Every rejection was a solvable problem. The emotional challenge was harder than the technical one."

Can You Publish to the App Store Without a Mac?

Yes, if the build is produced somewhere other than your desk. Xcode is Mac-only, so the traditional route needs one, but three alternatives do not:

You still need an iPhone or iPad to test properly, and you still need the $99 membership. What you avoid is buying a Mac to compile a first app.

How Do You Publish an App Built With Lovable, Bolt, Base44, or Another Web Tool?

This is the most common publishing dead end, and it is worth naming plainly. Lovable, Bolt, v0, and Base44 build web apps. A web app can be wrapped in a shell and submitted, and that is exactly what guideline 4.2 targets: App Review's own wording in a published rejection is that "Including iOS features such as push notifications, Core Location, and sharing do not provide a robust enough experience to be appropriate for the App Store."

Three ways out, in order of how well they survive review:

1. Rebuild it natively. Use the web app as the reference and generate a native version. Superapp can take a Figma file, a website, or a Lovable or Replit project as a reference and rebuild it natively rather than wrapping it, which removes the 4.2 problem at the root.
2. Rebuild it cross-platform. FlutterFlow, Adalo, Thunkable, or a React Native project through Replit or Expo produce real store apps for both stores.
3. Keep it a web app. Ship it as a website people add to the home screen, and skip the store entirely. No fee, no review, no store distribution either.

Wrapping a website is the fourth option and the one that keeps getting rejected, so treat it as a last resort and expect to argue guideline 4.2.

What Happens in the First Week After You Publish?

Approval is not distribution. Nobody knows the app exists yet, and the store's own search is where the first users come from. Apple Ads reports that "70% of App Store visitors use search to discover apps" and that "Almost 65% of downloads happen directly after a search," with more than 850 million people visiting the App Store weekly.

Superapp runs App Store optimization and Apple Ads in the same place you built the app, so keyword changes and campaigns sit next to the build; with FlutterFlow, Adalo, or Xcode, use App Store Connect, an ASO tool, and the Apple Ads dashboard directly. Our guide to getting users for your app covers this week in more detail.

Why Do Apps Get Rejected, and What Do You Do Next?

Rejection is normal. Apple's 2025 transparency report lists 9,100,620 app submissions reviewed and 2,093,244 rejections, so roughly one in four submissions comes back. Almost all of them are fixable the same week.

How to respond. Apple replies in Resolution Center inside App Store Connect, naming the guideline. Read that guideline, fix the one thing, reply in the same thread describing the change, upload a new build if the code changed, and resubmit. Do not argue first and fix later; a short reply plus a fixed build is faster than a long appeal. Bryce Rattner Keithley, who shipped the fitness app Daily Hundred with no coding background, had "some pretty low hanging fruit from my first submission that was mostly user error" and was live "on the second try."

Rejection rule: Treat each rejection as one specific problem, not a verdict. Paste the exact message into your builder, Superapp, Claude, Cursor, or your developer's inbox, fix that one guideline, and resubmit the same day.

The Pre-Submission Checklist

Run this before you press submit. It catches most first-time rejections.

• The app opens and completes its main task on a real device, not just a simulator
• Sign-in works with a fresh account, and a demo account is in App Review Information
• Purchases start, cancel, and restore in the sandbox, if you sell anything
• The app does something useful without a website behind it (guideline 4.2)
• Name is 30 characters or fewer, subtitle is 30 or fewer, keywords are within 100 characters
• Description's first sentence says what the app does
• Screenshots come from the current build and show the core task first
• App icon is uploaded and readable at small sizes
• App Privacy answers cover every data type, including SDKs
• Privacy policy and support URLs load, and are not PDFs
• Age rating questionnaire is complete and honest
• Build number is higher than the last upload, and export compliance is answered
• Release option chosen: manual for a first launch

Superapp prepares the build, metadata, screenshots, and privacy details for its own output, so on that route the checklist is mostly verification; with FlutterFlow, Adalo, or Xcode you assemble each item yourself.

What Does It Cost to Publish an App on the App Store?

Most first apps pay $99 and nothing else to Apple, because Apple's commission applies to digital sales, and physical goods and services sold through an app carry no Apple commission. For a full cost comparison across build routes, see our guide to how much it costs to make an app.

How Do You Publish an Update?

Updates use the same pipeline, with three differences.

1. Version numbers. 1.0.1 for fixes, 1.1 for features, 2.0 for a rewrite. The build number still has to increase every upload, whether Superapp, FlutterFlow, or Xcode produced it.
2. Release notes. One or two lines saying what changed. People do read them, and reviewers check that they match.
3. Phased release. Available for updates only: 1% of users on day 1, rising to 100% on day 7, pausable for up to 30 days.

Metadata-only changes, such as a new description or screenshots, still go through review, but you do not need a new build. Promotional text is the exception you can change at any time.

What About Google Play?

If the same app is going to Android, the shape is similar and the gates differ.

The practical consequence: an iPhone-first launch can be live in a week, while a first Android launch on a new personal account has a 14-day clock before production is even available.

Which Route Should You Pick?

Whichever route you pick, the nine steps above do not change, because they belong to Apple rather than to your tool.

For the building side, see how to make an app and how to create an app, and for the no-code iPhone route in detail, how to build an iPhone app without code.

App Store Publishing Terms, Defined

• App Store Connect: Apple's portal for creating app records, uploading builds, and submitting for review. Every route ends here, including Superapp, FlutterFlow, Adalo, and Xcode.
• Bundle ID: the unique reverse-domain identifier for your app, fixed once the app record exists.
• Build number: an always-increasing number attached to each upload.
• Provisioning profile and certificate: the files that sign your build so Apple accepts it.
• TestFlight: Apple's beta distribution service, up to 100 internal and 10,000 external testers.
• App Review: Apple's check against the App Review Guidelines before an app goes live.
• Resolution Center: the thread in App Store Connect where Apple explains a rejection and you reply.
• App Privacy: the data declarations that appear on your product page.
• Phased release: a 7-day gradual rollout for updates.
• Small Business Program: Apple's 15% commission tier for developers earning up to $1 million in the prior year.

Disclosure

As a disclosure, Superapp is our product, so weigh this accordingly. We recommend it for publishing a native iPhone app without code, because it writes Swift you own, compiles on cloud Macs so no Mac is needed, and prepares the build, screenshots, metadata, and privacy details for App Store Connect. The Apple account, the submission, and the review are still yours, exactly as they are on every other route in this guide. If you need Android from the same project, prefer a visual editor, or want to learn to code, FlutterFlow, Adalo, and Xcode are the better fits.

Frequently Asked Questions

How do I publish an app to the App Store?
Enroll in the Apple Developer Program for $99 a year, create the app in App Store Connect, prepare the listing and App Privacy answers, upload a build, submit for review, and choose how it releases. Apple says 90% of submissions are reviewed in less than 24 hours.

How do I publish an app to the App Store without coding?
Use a builder that produces a real build. Superapp writes native Swift, compiles it on Macs in the cloud, and prepares the submission details; FlutterFlow, Adalo, Thunkable, and Bubble publish from their dashboards. You still need your own $99 Apple account, and the app still passes App Review.

Is there a tool that handles the entire App Store submission for me?
No. Apple requires the app to be submitted under your own developer account and to pass review. A tool can build the app, produce the icon, screenshots, and metadata, and prepare the privacy answers, which is what Superapp does, but you hold the account and press submit.

How much does it cost to publish an app on the App Store?
$99 a year for the Apple Developer Program, which covers unlimited apps, TestFlight, hosting, and distribution in 175 regions. Apple takes 30% of digital sales, or 15% under the Small Business Program and for qualifying subscriptions. The Enterprise Program is $299 a year and is only for private internal apps.

Can I publish to the App Store with a free Apple account?
No. A free account lets you test on up to 3 devices with profiles that expire after 7 days. Distribution requires the paid Apple Developer Program.

Do I need a Mac to publish an app to the App Store?
Not if the build is made elsewhere. Superapp compiles Swift on Macs in the cloud, and FlutterFlow, Adalo, and Expo-based services build on their own infrastructure. Xcode itself is Mac-only.

How long does App Store review take in 2026?
Apple states: "On average, 90% of submissions are reviewed in less than 24 hours." Incomplete submissions take longer, and Apple warns reviews may run longer for a few days in late December.

How long does the whole publishing process take?
About a week for a first app: enrollment in a day or two, the listing in a few hours, an optional TestFlight round of a few days, review usually inside a day, then release. Organization enrollment can add up to a week because of D-U-N-S verification.

Do I need a company to publish an app?
No. You can enroll as an individual, and Apple then lists your personal legal name as the seller. Organizations must provide a legal entity name and a D-U-N-S Number, and Apple does not accept DBAs or trade names.

What do I need before I submit?
A paid membership, a signed build with an increasing build number, an App Store Connect record, a listing with screenshots and an icon, App Privacy answers, a working privacy policy and support URL, and a demo account if the app has sign-in.

Why do apps get rejected from the App Store?
Most often for crashes, incomplete information such as a missing demo account, privacy answers that do not match the app, payment mistakes, or doing too little under guideline 4.2. Apple's 2025 transparency report lists 2,093,244 rejections out of 9,100,620 submissions reviewed.

What do I do after a rejection?
Read the guideline Apple names, fix that one thing, reply in Resolution Center describing the change, upload a new build if the code changed, and resubmit. Most rejections are resolved the same week.

Can I publish an app made with Lovable, Bolt, or Base44 to the App Store?
Not as a wrapped web app without risking guideline 4.2, which rejects apps that are mostly a repackaged website. Rebuild it natively, for example with Superapp, which can use a Lovable or Replit project as a reference and rebuild it in Swift, or rebuild cross-platform with FlutterFlow or React Native.

How many apps can I publish with one Apple Developer account?
There is no per-app fee. One $99-a-year membership covers unlimited apps, and the same account holds all of them.

What are the App Store listing limits?
The app name and the subtitle are each capped at 30 characters, keywords at 100 characters total separated by commas with no spaces, and the description at 4000 characters.

How many testers can I have on TestFlight?
Up to 100 internal testers and up to 10,000 external testers per app. Builds are testable for up to 90 days, and the first build sent to an external group goes through a beta review.

Should I release the app immediately after approval?
Use manual release for a first launch so you control the timing. For updates, phased release rolls out over 7 days starting at 1% of users, and can be paused for up to 30 days.

How do I publish an app update?
Change the app, raise the version and build numbers, write release notes, and submit again. Metadata-only changes still go through review, but do not need a new build; promotional text can be changed at any time.

Do I have to publish to Google Play too?
No, they are separate stores. Google Play costs $25 once, and personal accounts created after November 13, 2023 must run a closed test with at least 12 testers for 14 continuous days before they can publish to production.

What should I do the week after publishing?
Fix crashes, watch where users stop, tighten the app name, subtitle, keywords, and first two screenshots, ask for ratings after a user's first success, and test a small Apple Ads budget. Apple reports that almost 65% of downloads happen directly after a search.

References

• Apple Developer Program
• Apple Developer Program: membership details
• Apple Developer: enrollment help
• Apple Developer: D-U-N-S Number
• Apple Developer: choosing a membership
• App Store Connect Help
• App Store Connect: app information reference
• App Store Connect: platform version information
• Apple: creating your product page
• Apple Developer: App Review
• Apple: App Review Guidelines
• Apple Developer Forums: guideline 4.2 rejection wording
• Apple: 2025 App Store Transparency Report
• App Store Connect: TestFlight overview
• App Store Connect: invite external testers
• App Store Connect: release a version update in phases
• Apple Ads: ads on the App Store
• Google Play: testing requirements for new personal developer accounts
• Google Play: Data safety section
• AI Founder Kit: Superapp review
• Greg Kowalczyk: I built 2 iOS apps at 55 without writing a line of code
• How I AI: Bryce Rattner Keithley builds an iPhone app with no technical skills
• Superapp
• Superapp pricing
• Our guide to how much it costs to make an app
• Our guide to making an app
• Our guide to creating an app and an app business
• Our no-code iPhone app guide