How to Get an AI-Built App Into the App Store
You need Apple's Developer Program (99 USD a year), an iPhone build, TestFlight, a store listing and App Review. Here is each step, and who does what.
To get an app built with AI into the App Store, you need a membership in Apple's Developer Program (99 USD a year as of November 2026), an iPhone build of the app, a round of testing in TestFlight, a store listing in App Store Connect, and approval from Apple's App Review. If you built the app with Firevibe, the order is: on the Pro plan you publish the app, connect your own Expo account, and Firevibe hands the app to Expo's build service under that account. You finish there with your own Apple account: Expo builds the iPhone app, the build arrives in your TestFlight, and you submit it for review yourself.
We make Firevibe, so the Firevibe parts below are first-hand, including where Firevibe stops. Every outside fact links to Apple's, Expo's or Google's own page.
What accounts do you need, and what do they cost?
You need two outside accounts, an Apple developer account and an Expo account, plus the Firevibe Pro plan if your app was built in Firevibe. The prices below are as of November 2026.
| Account | What it is for | Price |
|---|---|---|
| Apple Developer Program | TestFlight, App Store Connect and App Review | 99 USD per membership year |
| Expo, Free plan | Building the iPhone app on Expo's servers | $0 a month, 15 iOS builds |
| Firevibe Pro | Publishing the app and handing it to Expo | from $50 a month |
Apple Developer Program. Apple's enrollment page states that "The Apple Developer Program is 99 USD per membership year" and that prices "are listed in local currency during the enrollment process." To enroll as an individual you need an Apple Account with two-factor authentication turned on, and you must use your legal name, because Apple says an alias or company name "will cause a delay in the approval of your enrollment." To enroll a company, the company must be a legal entity and, unless it is a government entity, needs a D-U-N-S Number. Nonprofits, accredited schools and government entities can request a fee waiver.
Expo account. Expo's pricing page lists the Free plan at $0 a month with "15 Android and 15 iOS builds", a "Low-priority queue", a 45-minute build timeout and "Submit to app stores". Expo's plans documentation says the Free plan's build limits "reset monthly". If you need more, Expo's Starter plan is $19 a month plus usage, with $45 of build credit and a high-priority queue.
Firevibe Pro. Reading the code needs a paid plan, and publishing and the App Store step need Pro. Pro starts at $50 a month for 3,000 credits, or from $500 a year with yearly billing. The full plan list is on the pricing page. For a full budget, including your time, see how much it costs to build an app with AI.
What are the steps from a finished app to the App Store?
The path has five steps, in this order:
- Publish the app. In Firevibe, publishing puts the app's backend on its own permanent address.
- Make a build. A build is the installable iPhone app file, what Expo calls an app binary. Expo's build documentation describes its service as "a hosted service for building app binaries for your Expo and React Native projects." Expo's docs now call it Expo Build; the command is still
eas build. - Test it in TestFlight. The build lands in TestFlight, Apple's beta testing service, where you and your testers install it on real phones.
- Fill in the App Store listing. In App Store Connect you add the app's metadata, screenshots, privacy policy link and data practices, and choose the build to submit.
- Submit for App Review. Apple checks the app against its App Store Review Guidelines and approves or rejects it.
What does Firevibe do, and what do you do?
On the Pro plan, Firevibe hands the app to your own Expo account, and Firevibe's part ends there. The store build is Expo's, and the submission is yours.
| What Firevibe does | What you do |
|---|---|
| Writes the app in React Native with Expo, with its backend, and shows it on your phone in Expo Go | Describe the app, try it in Expo Go, change it by chat |
| Publishing puts the app's backend on its own permanent address | Choose to publish the app, on the Pro plan |
| Hands the app to Expo's build service under your Expo account | Create your own Expo account, connect it, and sign in with Apple on Expo so Expo can build the iPhone app |
| Nothing at this step: the build arrives in your TestFlight | Install the build in TestFlight and test it |
| Nothing at this step: App Store Connect is your account | Write the listing, add screenshots and the privacy policy link |
| Nothing at this step: App Review is between you and Apple | Submit for App Review and answer Apple's messages |
You need your own Apple developer account for every step after the hand-off. Firevibe does not submit the app to Apple; you do. The mobile app page shows the same steps as pictures. If you have not built the app yet, start with how to build an iOS and Android app with AI.
What is TestFlight, and how many testers can you invite?
TestFlight is Apple's beta testing service: it lets people install a build of your app on their own iPhone before the app is in the App Store. Per Apple's TestFlight page and the TestFlight overview in App Store Connect Help, as of November 2026:
- Internal testers: up to 100 App Store Connect users on your team.
- External testers: up to 10,000 people, invited by email or a public link.
- Review for external testing: when you add the first build to an external group, "the build gets sent to App Review", and Apple says "A review is required only for the first build."
- How long a build lasts: "You can test a build for up to 90 days."
- Devices: each tester can use a build on up to 30 devices.
For a Firevibe app, TestFlight is also the first real test of some features. Sign in with Apple, Google sign-in and in-app purchases through RevenueCat work in the installed app, not in the Expo Go preview. A TestFlight build is an installed app, so test each of them there before you submit.
What does App Review check that AI-built apps often miss?
App Review checks your app against Apple's App Store Review Guidelines. The guidelines below cover things a description of an app rarely mentions, so check each one yourself instead of assuming the builder added it. The numbers are as Apple's page shows them in November 2026.
2.1 App Completeness
Guideline 2.1(a) says submissions "should be final versions with all necessary metadata and fully functional URLs included" and that "placeholder text, empty websites, and other temporary content should be scrubbed before submission." It also asks you to include demo account info if your app has a login, and to turn on your back-end service. A Firevibe app has email and password sign-in from the first build, so create a test account and put its email and password in the App Review information section. Guideline 2.1(b) adds that in-app purchases must be "complete, up-to-date, visible to the reviewer and functional."
What to check: tap every screen for sample text you never replaced, make sure the app is published so its backend is on its permanent address, and give Apple a working login.
4.2 Minimum Functionality
Guideline 4.2 asks for "features, content, and UI" that take the app beyond a repackaged website, and says: "If your app is not particularly useful, unique, or 'app-like,' it doesn't belong on the App Store." Guideline 4.2.2 adds that apps "shouldn't primarily be marketing materials, advertisements, web clippings, content aggregators, or a collection of links."
What to check: the app should do one useful thing well on the phone. A Firevibe mobile app is a native React Native app, not a web page in a frame, but the guideline is about usefulness, and only you can judge that.
5.1.1(i) Privacy Policies
Guideline 5.1.1(i) says: "All apps must include a link to their privacy policy in the App Store Connect metadata field and within the app in an easily accessible manner." App Store Connect Help on app privacy also says "A privacy policy URL is required for all apps" and that apps on the App Store must explain their data handling practices in App Store Connect.
What to check: you need a privacy policy page at a public address, a link to it inside the app (a settings or account screen is the usual place), and the same link in App Store Connect.
5.1.1(v) Account Sign-In
Guideline 5.1.1(v) says: "If your app supports account creation, you must also offer account deletion within the app." A Firevibe app has email and password sign-in from the first build, so if people can create an account, this applies to you.
What to check: a signed-in user can find a way to delete their account inside the app. If it is missing, describe it in the chat like any other change, for example a delete account button on the account screen that removes the user and their data, then test it in TestFlight.
4.8 Login Services
Guideline 4.8 says that apps that use "a third-party or social login service" (Apple's examples include Google Sign-In and Facebook Login) for the user's main account "must also offer as an equivalent option another login service" that limits data collection to the user's name and email address, lets users keep their email address private, and does not collect interactions with the app for advertising without consent. Apple lists exceptions, the first being an app that "exclusively uses your company's own account setup and sign-in systems."
What to check: an app that signs people in only with its own email and password, which is how a Firevibe app starts, fits that first exception. If you ask Firevibe for Google sign-in, also plan the second option. Firevibe adds Sign in with Apple on request, and Apple's support page says that with Sign in with Apple, apps "can ask only for your name and email address", that Hide My Email lets people avoid sharing their personal address, and that it "won't track or profile you."
How long does App Review take?
Apple's App Review page says App Review "works around the clock, typically reviewing at least 50% of submissions in less than 24 hours and 90% in less than 48 hours." The same page warns: "If your submission is incomplete, review times may be delayed or your submission may not pass."
Apple accepts requests for an expedited review in two cases it names: fixing a critical bug in your app, and releasing an app to coincide with an event you are directly associated with.
Two other Apple steps come before App Review. Apple's enrollment support page says to contact Apple if you have not received a membership confirmation "within 24 hours of your purchase," and that a wrongly entered legal name delays the approval of your enrollment, so enroll first. The first TestFlight build you share with external testers also goes through review. If you want a schedule that fits all of this into two days, see from app idea to App Store in a weekend.
What about Google Play?
Google Play needs its own Play Console developer account. Google's Play Console help says "There is a US$25 one-time registration fee," and you complete identity verification, which may ask for a government ID and a credit card in your legal name. Google's testing requirements page says personal accounts created after November 13, 2023 "must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days" before applying for production access.
A Firevibe app runs on Android and opens on an Android phone today. Sending it to Google Play from Firevibe is not available yet. The App Store path above is the one Firevibe supports.
Start on your own phone
If you have an app idea and no app yet, you can build it in Firevibe and open it on your own phone with Expo Go before you pay for anything or enroll with Apple. Sign up is free, with no credit card: try Firevibe. When the app is ready for the store, the Pro plan adds the hand-off to your Expo account, and the steps above take it from there.
Frequently asked questions
How much does it cost to put an AI-built app in the App Store? As of November 2026, Apple's Developer Program costs 99 USD per membership year, shown in local currency where available. Expo's Free plan costs $0 a month and includes 15 iOS builds. For a Firevibe app, the App Store step needs the Pro plan, which starts at $50 a month.
Does Firevibe submit my app to the App Store? No. On the Pro plan, Firevibe hands the app to Expo's build service under your own Expo account, Expo builds the iPhone app, and the build arrives in your TestFlight. You submit it for App Review yourself, with your own Apple developer account.
How long does Apple take to review an app? Apple says App Review typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours. Apple also says an incomplete submission can be delayed or may not pass.
How many people can test my app on TestFlight? TestFlight allows up to 100 internal testers from your App Store Connect team and up to 10,000 external testers. The first build you add to an external group goes to App Review, and each build can be tested for up to 90 days.
Do I need Sign in with Apple to pass App Review? Not always. Apple's guideline 4.8 applies when an app uses a third-party or social login, such as Google Sign-In, for the main account. Such an app must also offer an equivalent login option that limits data to name and email, lets people keep their email private, and does not collect app interactions for advertising without consent.
Can I publish a Firevibe app to Google Play? Not from Firevibe yet. A Firevibe app runs on Android and opens on an Android phone today, but sending it to Google Play from Firevibe is not available. Google charges a one-time US$25 fee to register a Play Console developer account.
