import { Callout } from '@/components/ui/callout';
The screens were finished and the Publish to App Store button was right there. Then Rork asked me to sign in with an Apple Developer account, and all I had was the Apple Account I use for everything else.
Everything between that moment and an app actually appearing on the App Store happens outside Rork. I have been shipping wallpaper and relaxation-sound apps under my own name for a long time, and this Apple-side setup still catches me somewhere almost every time.
Here is the short version up front: what delays a first launch is rarely the app — it is the waiting on Apple's side. So this is a map of the boundary, ordered by how long each step makes you wait. I checked the steps and screen names against Apple's help pages and Rork's documentation in November 2026.
Publishing starts only after Apple is ready
According to Rork's own guide, Publish Your App to the Apple App Store, Rork builds the app on its own machines, so you need no Xcode, no Mac, and no separate build account. You set the project name, bundle identifier, and icon, press Publish to App Store, sign in with your Apple Developer account, and Rork takes it from build to App Store Connect. The signing work I used to do by hand simply disappears.
But the same guide opens by saying you need an Apple Developer account first. What Rork automates is getting a binary to Apple. The account it lands in, and the agreements that account has signed, sit outside the tool. After submission, you still fill in the product page yourself in App Store Connect.
| Step | Rork handles it | You handle it | Typical wait |
|---|---|---|---|
| Developer Program enrollment and identity check | — | ✔ | Hours to days |
| (Organizations) D-U-N-S Number | — | ✔ | Up to 5 business days, then 2 more |
| Two-factor code during submission | — | ✔ | On the spot |
| Paid Apps Agreement, tax forms, banking | — | ✔ | Roughly half a day of forms |
| Signing, build, upload to App Store Connect | ✔ | — | Tens of minutes |
| Product page, age rating, App Privacy | — | ✔ | An hour or two |
| Review and any rejection | — | ✔ | Unpredictable |
Apart from the D-U-N-S figures, which come from Apple, the wait column is my own rough experience. Automated signing is a real gift; the side effect is that what remains becomes easy to overlook. Start enrolling only once the app is done and 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 the parts it assumes are already done.
Three forks in the enrollment process
Distribution on the App Store requires the Apple Developer Program. It is 99 USD per membership year, shown in your local currency during enrollment, and the same for individuals and organizations (checked on Apple's enrollment page in November 2026).
The fee 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 the App Store is your legal name. Enroll as an organization and it is your legal entity's name — but that path requires an entity that can sign contracts and a D-U-N-S Number, the nine-digit identifier from Dun & Bradstreet. Apple states plainly that it does not accept DBAs, fictitious business names, trade names, or branches.
I enrolled as an individual, so my own name sits on every app I ship. I did not think hard about that at the start. Changing legal entity details later means contacting Apple, possibly with business documents, and Apple's help notes that approved changes can take up to two weeks to show in App Store Connect.
| Individual | Organization | |
|---|---|---|
| Seller name on the App Store | Your legal name | The legal entity's name |
| D-U-N-S Number | Not needed | Required (free) |
| Also verified | Name, phone, address (no P.O. boxes) | Work email on the company domain, a live public website, signing authority |
| Trade name / DBA | Not accepted for either | |
| Annual fee | Same (99 USD per year) | |
The decision rule I use fits in one line: if a company already exists and you want to sell under its name, enroll as an organization; otherwise start as an individual. A company you might form someday is not a reason to hold the launch.
Apple's program enrollment help page has the full current requirements. The details shift, so it is worth reading the week you sign up.
Do not assume verification finishes the same day
After you apply, Apple reviews the application. Sometimes it clears quickly; sometimes you are asked for an ID image or more documents and it takes days. Mine sat untouched for about two days, and I spent most of that time recalculating a launch date I had already mentioned to people.
You can now enroll as an individual from the Apple Developer app on iPhone, iPad, or Mac, photographing a government-issued photo ID — passports in most regions, and in some regions other IDs such as a driver's license. Apple's help asks you to use the same device for the whole enrollment and to enter your legal first and last names, not an alias or a company name, because a mismatch delays approval. Checking the name on your Apple Account before you apply is the cheapest fix there is.
Because the window is unpredictable, put enrollment first when you plan backwards from a launch date. Even while you are still trying things on Rork's free tier, if you know you will publish, start the paperwork.
Two-factor authentication comes back during submission
The Apple Account you enroll with must have two-factor authentication on. What is easy to miss is that this is not only an enrollment-day concern. Rork's guide notes that partway through the build and submission, Apple sends a code to one of your signed-in devices, and you need to enter it into Rork.
I once started a submission with that device charging in another room and had to run for it. Tie the account to a device you actually keep with you and a phone number you can receive texts on, and that small scramble never happens.
If you are still weighing when to start paying at all, how far Rork Companion's free device testing goes covers what you can verify before the annual fee becomes unavoidable.
Why the Paid Apps Agreement, tax, and banking should come early
What older guides call "Agreements, Tax, and Banking" now lives under Business at the top of App Store Connect (as of November 2026). Apple's help is direct about it: joining the program lets you distribute free apps, but to sell apps or offer In-App Purchases, the Account Holder must sign the Paid Apps Agreement and provide tax and banking information.
The forms Apple asks for depend on where you are based; you answer a few questions on screen and it points you to the ones that apply (Apple's help on this). What goes into them depends on your country, so I will not go there — only the order matters for this article: get it done early.
I skipped this once and paid for it. I created an in-app purchase, sandbox purchases refused to behave, and I spent half a day suspecting my own code. The agreement was not active. When I reread Apple's help afterwards, the line was right there: the agreement must be Active to test In-App Purchases in the sandbox.
Before doubting the purchase code, open the Business page. That order is one I have kept ever since.
| What you ship | Agreement needed | Tax forms and banking |
|---|---|---|
| Free only, no purchases | Developer Program License Agreement (accepted at enrollment) | Not required |
| Paid app, in-app purchases, or subscriptions | Paid Apps Agreement, signed by the Account Holder | Required |
| Ad revenue only (AdMob and similar) | License Agreement only | Not on Apple's side; set up with the ad network |
The Paid Apps Agreement gets revised from time to time. When a new version is waiting, App Store Connect shows an alert, and Apple's help says you cannot create a new app or In-App Purchase until you accept it. Only the Account Holder can, so if you work with anyone else, agree on who tells whom when that banner appears.
Ad money arrives from the ad network, not from Apple, which 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.
The first is the age rating questionnaire. You declare how often certain kinds of content appear and whether the app has things like user-generated content or in-app controls; your answers become an Apple global rating plus regional ratings where required (Apple's age rating help). When the questions change, existing apps answer again — I wrote up one round of that in answering the new App Store age ratings.
The second is the App Privacy declaration: what data your app collects and why. Add an ad SDK or a subscription layer and the list grows sharply, and you cannot answer accurately without knowing what your Rork project actually pulls in. The App Privacy section that grows the moment you add ads and subscriptions walks through what each addition cost me in checkboxes.
List your dependencies before you declare anything
Before I touch the privacy form, I print the list of libraries the project depends on and read it like a shopping receipt. If you have your Rork project locally (through GitHub, for example), these commands produce that list. The problem they solve: knowing which SDKs a feature you asked Rork for quietly brought along.
# Expo (React Native) projects: list dependencies from package.json
node -e "const p=require('./package.json');console.log(Object.keys(p.dependencies||{}).sort().join('\n'))"
# Swift (Rork Max) projects: list Swift Package Manager pins
# Package.resolved usually sits under .xcworkspace/xcshareddata/swiftpm/ or similar
find . -name Package.resolved -not -path '*/.build/*' -exec python3 -c "import json,sys;d=json.load(open(sys.argv[1]));print('\n'.join(sorted(p.get('identity',p.get('package','')) for p in d.get('pins',d.get('object',{}).get('pins',[])))))" {} \;The output is a plain column of names such as expo-router, react-native-google-mobile-ads, or react-native-purchases. For every ad, purchase, or analytics SDK on that list, open its documentation's App Store privacy section and carry its data types into your declaration. The Python one-liner reads both Package.resolved layouts — the newer one with pins at the top level and the older one nested under object.pins.
You can revise both questionnaires later, but a contradiction spotted during review sends the build back. Sitting down once with the list in front of you is faster than guessing and resubmitting.
When something stalls: a symptom table
When a release stops just short of the finish line, the fastest move is to decide whether the cause is inside the app or in Apple's paperwork. These are the cases I have actually hit, plus ones whose conditions Apple's help spells out.
| Symptom | Likely cause | How to check | Fix |
|---|---|---|---|
| Rork's Publish to App Store flow goes nowhere | Developer Program enrollment not complete | Membership status on your developer.apple.com account page | Wait for approval; correct your Apple Account to your legal name if it differs |
| Submission stalls partway | Two-factor code not entered | Look for a verification code on your signed-in devices | Keep the device at hand, restart the submission, enter the code in Rork |
| Sandbox purchases fail or products do not load | Paid Apps Agreement not Active | Business → Agreements tab, Paid Apps row | Account Holder signs it and completes tax and banking |
| Cannot create a new app or In-App Purchase | Revised Paid Apps Agreement not accepted | Alert banner at the top of App Store Connect | Account Holder accepts the latest version |
| Organization enrollment will not proceed | No D-U-N-S Number yet, or not yet passed to Apple | Look up your organization on D&B | After receiving it, allow up to 2 business days for Apple to get the data |
| Seller name is not what you expected | Individual accounts show your legal name | Legal entity details under Business | Enroll as an organization, or contact Apple about changing entity details |
The middle four rows reflect conditions stated in Apple's help; the wording in the table is my own summary against the screens. Button labels move when App Store Connect changes, so if one is missing, searching Apple's help for "Paid Apps Agreement" is the reliable fallback.
Three common misreadings
"Rork's price includes Apple's fee." It does not. Rork's guide says you need your own Apple Developer account, and the 99 USD a year goes to Apple directly. I laid out when each bill actually lands in the order the bills arrive in your first year with Rork.
"A registered trade name lets me sell under a brand without a company." It does not. Apple rejects DBAs and trade names, and individual accounts show your legal name.
"Even a free app needs every tax and banking field filled in." Not so. Free apps ship under the License Agreement you accept at enrollment. The Paid Apps Agreement, tax, and banking only become necessary when you sell or offer purchases — which also means that if you plan to add a subscription later, you will be coming back to this page.
An order that keeps the waiting off the critical path
Some of this involves waiting on someone else, and some is entirely in your hands. Start the waiting early and you can build during it. If I were shipping a new app today, this is the sequence I would follow.
- Confirm your Apple Account uses your legal name, with two-factor auth and a phone number you actually receive texts on
- Decide individual or organization (for an organization, check for a D-U-N-S Number now)
- Apply to the Apple Developer Program — this is where the waiting lives
- Build the app in Rork while the application is reviewed
- The day enrollment clears, sign the Paid Apps Agreement and complete tax and banking if you will charge for anything
- List your dependencies and draft your age rating and App Privacy answers
- With the two-factor device in hand, submit from Rork
- Finish the product page and questionnaires in App Store Connect and send it to review
You can reorder this and still ship. Push steps 3 and 5 to the end, though, and you create a stretch of days where the app is finished and cannot go anywhere. That is exactly the mistake I made the first time.
The next place people get stuck: reading the review wait
With all of this done, the next thing you meet is review itself, and you cannot control when it clears. I no longer promise a launch date at submission time; I set the release to manual and choose the day after approval. The reasoning is in setting your release date outside the review queue.
If you want to turn the whole path — enrollment, testing, review — into a day count, before promising "released in a week" is the natural next read.
Now that Rork handles the build and the submission, the thing most likely to delay your launch lives outside the app. Starting the paperwork on the same day you start building makes most of this article unnecessary for you, which is the outcome I would want.
Checking the name and two-factor status on your Apple Account takes a minute. That is the one to do first — it is still where I start with every new app.