import { Callout } from '@/components/ui/callout';
The screens were finished and the publish button was right there. Then Rork Max asked for an Apple developer account, and all I had was a regular Apple ID.
Everything between that moment and an app actually appearing on the App Store happens outside Rork. I ship six wallpaper apps under an individual account, and this Apple-side setup is still the part that catches me out, even now that the app side is largely handled for me.
So this is a map of the boundary: what Rork genuinely takes off your plate, and what you will be filling in yourself. Not how to build the app — what surrounds it.
Two-click publishing starts after Apple is ready
Rork Max writes Swift, compiles it on a cloud Mac, issues the signing certificates, and pushes the build to App Store Connect. No Mac, no Xcode. That part works as advertised, and it removes work I spent years doing by hand.
What it automates, though, is getting a binary to Apple. The account it arrives in, and the contracts that account has signed, sit outside the tool.
| Step | Rork handles it | You handle it |
|---|---|---|
| Apple Developer Program enrollment | — | ✔ |
| Identity verification and two-factor auth | — | ✔ |
| Agreements, tax, and banking | — | ✔ |
| Signing certificates and provisioning | ✔ | — |
| Build and upload to App Store Connect | ✔ | — |
| Age rating questionnaire | — | ✔ |
| App Privacy declarations | — | ✔ |
| Responding to a rejection | — | ✔ |
Automating certificates is a real gift. The side effect is that the remaining work becomes easy to overlook, and if you start enrolling only once the app is done, the waiting turns directly into a later launch date.
If you want the app-side sequence first, publishing to the App Store with Rork Max covers that path, and this article picks up where it assumes an account already exists.
Three forks in the enrollment process
Distribution on the App Store requires membership in the Apple Developer Program. It costs 99 USD per year, billed in your local currency, and the price is the same for individuals and organizations (as of August 2026).
The cost was never the hard part. These three decisions were.
Individual or organization decides the name buyers see
Enroll as an individual and the seller name on your App Store listing is your own legal name. Enroll as an organization and it is your company name — but that path requires a real legal entity and a D-U-N-S Number, the nine-digit business identifier issued by Dun & Bradstreet. Trade names and sole-proprietor business names do not qualify.
I enrolled as an individual, so my name appears on all six apps. I did not think hard about it at the time, and it is not a field you casually change later. If shipping under a brand name matters to you, settle that before you enrol rather than after.
Apple's own program enrollment help page has the current requirements. The details shift over time, so it is worth a read the week you sign up.
Do not assume verification finishes the same day
After you submit the application, Apple reviews it. Sometimes it clears quickly. Sometimes you are asked for identification or a phone call and it takes days. Mine sat untouched for about two days.
Because that window is unpredictable, put enrollment first when you work backwards from a launch date. There is no reason to wait for a finished app. Even while you are still poking at Rork's free tier, if you know you intend to publish, start the paperwork.
Two-factor authentication is required, and awkward to undo
The Apple ID you enroll with must have two-factor authentication enabled, tied to a phone number you can actually receive messages on and a device you keep using. Attach it to a spare handset you rarely open and you will regret it the first time a review response needs your attention.
If you are still weighing when to start paying at all, how far Rork Companion's free device testing goes digs into what you can verify before the annual fee becomes unavoidable.
Why agreements, tax, and banking should come early
App Store Connect has a section called Agreements, Tax, and Banking. If you only ever ship free apps, accepting the free applications agreement is enough. If you plan to charge for the app or offer in-app purchases, you also need the paid applications agreement, tax forms, and bank details on file.
I skipped this once and paid for it. I built an in-app purchase product, sandbox purchases refused to behave, and I spent half a day suspecting my own code. The agreement simply had not been signed. The implementation was fine.
The section is long, and the tax forms vary by country of residence. It takes time, and none of that time depends on the app being finished — which is exactly why it belongs immediately after enrollment clears.
| What you ship | Agreement needed | Tax and banking |
|---|---|---|
| Free only, no purchases | Free applications | Not required |
| Paid app or in-app purchases | Paid applications | Required |
| Ad revenue only (AdMob and similar) | Free applications | Registered with the ad network instead |
Ad money arrives from the ad network, not from Apple, and that means a separate set of payment details somewhere else entirely. Knowing that up front saves a confusing afternoon.
Two questionnaires nobody can answer for you
Once the build reaches App Store Connect, two things stand between it and review. Both depend on knowledge only the person who built the app has, which is precisely why they resist automation.
The first is the age rating questionnaire. You work through questions about violence, user-generated content, and similar categories. When Apple revises the questions, existing apps have to answer again — I wrote up what actually changed across several live apps in answering the new App Store age ratings.
The second is the App Privacy declaration: what data your app collects and why. Add an advertising SDK or a subscription layer and the list of things you must declare expands sharply. Answering accurately means knowing what Rork's generated project actually pulls in, which in practice means reading the documentation for each dependency you added. The App Privacy section that grows the moment you add ads and subscriptions walks through what each addition cost me in checkboxes.
You can revise both later, but a contradiction spotted during review sends the build back. Sitting down once with a list of your SDKs beats guessing quickly and re-submitting.
An order that keeps the waiting off the critical path
Some of this work involves waiting on someone else, and some of it is entirely in your hands. Start the waiting early and you can build during it. If I were shipping a new app from scratch today, this is the sequence I would follow.
- Check two-factor authentication on your Apple ID and attach a phone number you actually use
- Apply to the Apple Developer Program — this is where the waiting lives
- Build the app in Rork while the application is under review
- The day enrollment clears, fill in agreements, tax, and banking
- Create the app record in App Store Connect and answer the age rating questionnaire
- List the SDKs you added and complete the App Privacy declaration
- Submit from Rork Max and send it to review
You can reorder this and still ship. But push steps 2 and 4 to the end and you create a stretch of days where the app is finished and cannot go anywhere. That is the exact mistake I made the first time.
Now that Rork handles the build and the submission, the thing most likely to delay your launch lives outside the app entirely. Starting the paperwork on the same day you start building makes most of this article irrelevant to you, which is the outcome I would want.
Checking the two-factor status on your Apple ID takes a minute. That is the one to do first.