Test and publish your iPhone app with x1
x1 helps you move from generated app to real device testing and launch.
Paid users can test quickly with Expo Go, publish to TestFlight for real-user testing, or submit to the App Store directly from x1 using their own Apple Developer account.
Apple still reviews apps before they go live. x1 helps with testing, launch preparation, and submission flow, but Apple controls final review and approval.
Three ways to test and ship your app
Publishing features are available on paid plans. See x1 pricing for plan details.
Why publishing matters
A generated app is not enough.
You need to test it on a real phone, share it with testers, fix issues, prepare launch materials, and submit through Apple's review process.
x1 is built to help app builders move beyond a demo and toward an actual release path.
Step 1: Test quickly with Expo Go
Expo Go is useful for early testing and quick previews.
With x1, you can test your app on a real phone before treating it like a finished product. This helps you catch obvious issues early: layout problems, broken navigation, confusing flows, and screens that look different on device than they did in your head.
Step 2: Publish to TestFlight
TestFlight lets you share your app with real testers before launching publicly.
Use TestFlight when you want feedback from friends, early users, investors, customers, or your own team.
This is where your app starts to feel real. It is no longer just a canvas or preview. People can install it, use it, and tell you what breaks or feels wrong.
Step 3: Submit to the App Store from x1
When your app is ready, x1 can help you submit it to the App Store directly from x1 using your Apple Developer account.
This helps reduce the gap between “I built something” and “I can actually launch this.”
Apple still reviews apps before they go live. x1 can help with the build, submission flow, and launch preparation, but Apple controls final review and approval.
Apple Developer account requirement
To publish through Apple, you need your own Apple Developer account.
x1 connects to your Apple Developer account for publishing. This keeps the app tied to your developer identity and gives you ownership of the release path.
What x1 helps prepare
x1 helps with the pieces builders usually forget until the end:
What x1 does not guarantee
x1 helps builders move from app project to testing and submission, but some parts of the publishing process are outside x1's control.
x1 does not guarantee:
- App Store approval
- Apple review timeline
- Legal or compliance approval
- Monetization approval
- Third-party API approval
- That Apple will accept every app concept
Apple reviews apps before they go live, so builders should treat x1 as a publishing workflow and submission support system, not an approval guarantee.
QA before launch
After each built milestone, x1 runs UI tests, checks that the app compiles, verifies that the milestone works as expected, and updates the app plan when the user's changes require it.
When the plan needs to change, x1 revises it before the project moves forward.
This helps keep the app coherent as it gets closer to testing and launch.
Source export
You own your app project and can export the React Native source code.
That means x1 is not just a closed preview environment. Builders can keep control of the app project as it becomes more serious.
Who this page is for
This page is for builders who want to know:
- Can I test the app on my phone?
- Can I share the app with testers?
- Can I publish to TestFlight?
- Can I submit to the App Store?
- Do I need my own Apple Developer account?
- Will I own the app project?
- Can I export the code?
Build the app. Test it on your phone.
Publish to TestFlight. Submit to the App Store when ready.
Start Building