Push notifications
Send messages to everyone who installed the app from the Notifications panel; permissions and tokens handled by the kit.
iPhone · App Store · TestFlight
Describe the iPhone app you want. Sorvel builds it, shows it on your own iPhone while it builds, and walks you through Apple's side: the developer account, the build, TestFlight, the store listing and the review. No Mac needed for store builds.
Five steps. Sorvel does the building; Apple's account and review stay yours.
"A meal planner with a weekly calendar and a shopping list." Pick the features and a design direction.
Scan the QR code with the camera. Changes arrive on the phone as you ask for them.
Connect Expo once, enter your Apple developer details, press Build app (EAS) and watch the status in the panel.
Send the store-signed build to testers from the Releases panel before going public.
Store assets, framed screenshots, listing texts and the privacy page are generated; the submission guide says who submits what, in order.
| Step | You | Sorvel |
|---|---|---|
| Developer account | Join the Apple Developer Program ($99/year) | Explains what to enter and where |
| Signing and build | Approve the account details once | Runs the EAS build and shows its progress |
| Testing | Invite testers | Puts the TestFlight route on every store-signed build |
| Listing | Review and submit in App Store Connect | Generates icons, screenshots, texts and the privacy page |
| Updates | Nothing for most fixes | Over-the-air updates from the Releases panel; tells you when a new build is needed |
Send messages to everyone who installed the app from the Notifications panel; permissions and tokens handled by the kit.
Subscriptions and one-time products through RevenueCat, with a paywall component and the right keys in the right place.
E-mail code sign-in on your own Supabase project, and Sign in with Google from its own panel.
Native modules from the kit, used only when the app needs them, with the permission texts Apple requires.
Make an https address open a screen in the app; the Deep links panel writes the association files.
Sentry error reporting on your own account, so you hear about a crash before the review does.
No. Store builds for iOS run on Expo's cloud build service (EAS), so a Windows or Linux computer, or just the browser, is enough. A Mac is only needed for the optional local iOS build in the desktop app.
An Apple Developer Program membership ($99 a year) to publish on the App Store. The Publish panel collects your developer account details and EAS produces the iOS build against them. A free Apple ID is enough for a local build on your own iPhone, but that signature expires after 7 days.
Press Start in the Open on phone panel and scan the QR code with the iPhone camera: the app opens in Safari right away. For native features such as notifications or purchases, install a development build once; after that every change arrives on the phone without a rebuild. Expo Go from the App Store only carries the newest SDK, so the panel steers iPhone users to the browser or a dev build.
Yes. Every store-signed build in the Releases panel carries the TestFlight route, so you can send it to testers before submitting for review.
Most fixes are JavaScript changes that ship as an over-the-air update from the Releases panel; installed iPhones pick them up on the next launch, without another App Store review. The panel tells you when a change touches the native side and needs a new build instead.
Yes. The project is an Expo (React Native) app, so the same code builds for Google Play. See the AI Android app builder page for what Google asks of you.