Mobile app creation requires a Replit Core or Replit Teams plan.
What you’ll do
In this tutorial, you’ll:- Create a mobile app from a prompt with Agent
- Preview it on your phone with Expo Go
- Publish an iOS build to TestFlight
- Submit that build to the App Store
Apple sets the requirements for TestFlight and App Store submissions. You’ll use App Store Connect to manage testing and releases.
What you’ll need
- A Replit account with access to mobile apps
- A phone with Expo Go installed
- An Apple Developer Program membership (required by Apple for TestFlight and the App Store)
Part 1: Build your app with Agent
1
Create a mobile app
On the Replit home screen, describe what you want to build, then select Mobile app as the app type.
2
Let Agent build
Agent scaffolds your project and builds your first version. Keep the chat open to follow progress and request changes.
Part 2: Test on your phone with Expo Go
Expo Go runs a native preview of your app on your device.1
Install Expo Go
Install Expo Go on your iPhone or Android device.
2
Open the QR code
In your Workspace, select Preview on mobile device to display a QR code.
3
Scan and preview
Scan the QR code with your phone to open a native preview in Expo Go.
Part 3: Publish to TestFlight
Publishing to the App Store starts with TestFlight. Use it to test on real devices, gather feedback, and fix issues before you release publicly.Apple publishing prerequisites
Join the Apple Developer Program
You need an Apple Developer Program membership to publish to TestFlight and submit to the App Store.Apple requires two-factor authentication on your Apple Account.
Individual vs. organization enrollment
- Individual accounts: Publish under your legal name as the seller.
- Organization accounts: Publish under the organization name as the seller. Apple requires a D‑U‑N‑S Number for organizations, which can take time to obtain.
Typical enrollment steps
- Sign in at
https://developer.apple.com/programs/enroll/ - Complete identity verification
- Accept the Apple Developer Program license agreement
- Pay the annual fee set by Apple
- Wait for Apple approval (time varies by account type)
Understand TestFlight vs. the App Store
TestFlight is Apple’s beta testing system. The App Store is the public marketplace where anyone can download your app.| Aspect | TestFlight | App Store |
|---|---|---|
| Audience | Invited testers (up to 10,000 external testers) | Public |
| Purpose | Beta testing and feedback | Public release |
| Review | First build of a version goes through beta review | Every submission goes through App Review |
| Build lifetime | Expires after 90 days | Permanent until you remove it |
1
Publish from your Workspace
Open the publishing pane and select Publish to prepare your app and backend for distribution.
2
Select App Store publishing
In the publishing pane, select Publish to App Store.
3
Connect Apple and submit
Sign in with your Apple Developer account when prompted. The native build runs in the cloud and submits to TestFlight.
The first build of a version typically requires a TestFlight beta review. After approval, you can usually push additional builds to testers faster.
Enable external testing
To share your TestFlight build with other people, configure external testing in App Store Connect:- In App Store Connect, open your app.
- Go to TestFlight, then External Testing.
- Create a testing group and add your build.
- Submit for Beta App Review (required by Apple for external testers).
- Share the public TestFlight link after approval.
Part 4: Submit to the App Store
When your build is ready for release, submit it through App Store Connect:- In App Store Connect, open your app.
- Go to the App Store tab.
- Fill out required metadata (description, screenshots, category, pricing, and privacy details).
- Select your TestFlight build to promote.
- Submit for review.
Complete your App Store Connect listing
Replit creates your app listing in App Store Connect, but you still need to complete required metadata before Apple will accept a submission.Common required fields
- App name and subtitle
- Category (primary, optional secondary)
- Pricing and availability (free or paid, and regions)
- Privacy policy URL (publicly accessible)
- App Privacy details (data collection “nutrition labels”)
- Screenshots (required)
- Support URL (required)
- App Review contact information (required)
If your app requires sign-in, add demo credentials for App Review in App Store Connect so Apple can test your app.
Privacy requirements
Apple requires you to:- Provide a public privacy policy URL
- Declare your App Privacy data practices (including third-party SDKs and services you use)
Screenshots
Screenshots are required and strongly influence conversion on the App Store.Common rejection reasons
| Issue | How to avoid it |
|---|---|
| Crashes or obvious bugs | Test on TestFlight first and fix issues before submission |
| Missing privacy policy | Add a public privacy policy URL before submission |
| Screenshots don’t match the app | Upload screenshots from the current build |
| Reviewers can’t access the app | Provide demo credentials and instructions in review notes |
| Incomplete or placeholder content | Remove “coming soon” flows and incomplete screens |
| Permission prompts lack context | Explain why you need camera, location, or other permissions |
Timelines to expect
| Stage | Typical duration |
|---|---|
| Apple Developer Program approval | Varies (often 1–2 days for individuals; longer for organizations) |
| Build processing in App Store Connect | Often 10–15 minutes |
| TestFlight beta review (first build of a version) | Often about a day |
| App Store review | Often 1–2 days |
Updating your app after launch
- UI and content updates: Publish again to ship updates quickly.
- Native changes (for example, app icons or permissions): Submit a new App Store build.
Checklist
Before you publish
- You can run the app on a real device
- Your app has no obvious crashes or broken flows
- You know whether your Apple account is individual or organization
Before you submit to the App Store
- App Store Connect metadata is complete (name, category, regions, and support URL)
- Privacy policy URL is public and accurate
- App Privacy details are complete (including third-party services)
- Screenshots are uploaded and match the submitted build
- App Review contact info is set
- Demo credentials are provided (if your app requires sign-in)
Next steps
- Learn how mobile apps work on Replit: Native Mobile Apps
- Learn how Agent works: Agent
- Build on your phone: Replit Mobile App
- Learn more about Expo: Expo docs