Rork App Publishing: What Founders Should Prepare First

Rork gets you from prompt to a working mobile app faster than almost anything else. What it does not do is get you through Apple's front door. Founders reach the point where the build looks finished, the TestFlight link works, and then the process stalls for weeks on things nobody warned them about: certificates, in-app purchase products, privacy answers, screenshots at exact pixel sizes, and a reviewer who wants to see something a browser cannot do.

This is a practical guide to what you should prepare before you try to publish a Rork app, in the order that saves the most time.

The pain point: the build is done, the launch is not

AI builders compress the engineering. They do not compress App Store compliance. The work that remains after Rork finishes is administrative, legal and commercial, and it is almost entirely front-loaded — you cannot parallelise it once you are already in review.

The three failure patterns we see repeatedly:

• Thin-wrapper rejection. The app is judged under guideline 4.2 as a website in a shell because there is no native capability a reviewer can point at.
• Payment rejection. Digital subscriptions are wired to Stripe or a web checkout instead of Apple in-app purchase, which breaks guideline 3.1.1.
• Account and metadata stalls. The Apple Developer Program enrolment, D-U-N-S verification, privacy policy, App Privacy answers or demo credentials are missing, and each round trip costs another 24 to 48 hours.

None of these are product problems. They are packaging problems, and every one of them can be closed before submission.

Decision logic: what to settle before you write a line of listing copy

1. Are you shipping iOS, Android, or both?

iOS review is stricter and the revenue is usually higher for consumer subscription apps. Android is cheaper to enter ($25 once versus $99 a year) but a new personal Play account now needs 12 testers running the app for 14 days. If you only have bandwidth for one, ship iOS first and treat Play as the follow-on.

2. Do you have a real native layer?

Ask a blunt question: what can this app do that Safari cannot? If the honest answer is "nothing", you are not ready. Push notifications, biometric sign-in, offline behaviour, camera or location use, widgets, or native in-app purchases each give the reviewer something concrete. One of them is usually enough; two is safer.

3. Are you charging inside the app?

If yes, the products have to exist in App Store Connect and the paywall has to be native, with a working restore flow. Decide the price points, the trial length and the billing period now — changing them later means new products, new screenshots and sometimes a new review.

4. Who owns the Apple account?

Individual enrolment is instant-ish; organisation enrolment needs a D-U-N-S number and can take one to two weeks on its own. If you intend to sell the app or raise money against it, enrol as the company from day one. This single decision is the most common cause of a multi-week delay.

Implementation steps: the pre-publish checklist

Step 1 — Open the Apple Developer account today

Before anything else. $99 a year, and organisation enrolment can sit in verification while you do everything else in parallel. Add your team, accept the current agreements, and complete the tax and banking forms in App Store Connect — Apple will not pay you or let you sell paid products until those are green.

Step 2 — Lock the bundle identifier and app record

Create the app record in App Store Connect with a final bundle ID. It cannot be changed afterwards. Reserve the app name at the same time; names are unique across the store and the good ones go early.

Step 3 — Add the native capability

Wrap the Rork output in a native shell and add the features that make it an app rather than a page. Push notifications are the highest-value first choice because they also serve retention. Biometric login and offline caching are cheap wins. Configure the entitlements and the APNs key while you are in the developer portal, not later.

Step 4 — Move digital purchases to in-app purchase

Create the subscription group and products in App Store Connect, wire a native paywall with purchase and restore, and verify receipts server-side. Keep your web billing for web-only customers. Enrol in the Small Business Program while you are there — it takes minutes and drops Apple's cut from 30% to 15% under $1m a year.

Step 5 — Write the compliance pages

You need a public privacy policy URL, in-app account deletion if you have accounts, and completed App Privacy answers that match what your app actually collects. Mismatches here are a common and entirely avoidable rejection.

Step 6 — Prepare metadata and creative

Apple indexes the app name, the subtitle and the 100-character keyword field — not the description. Choose those with intent in mind, then produce screenshots for the 6.9-inch iPhone display (1290 x 2796 px) and, if you support iPad, the 13-inch size (2064 x 2752 px). An app preview video is optional but lifts conversion. If you want a quick read on how competitive your chosen terms are before you commit, run an ASO score on the draft listing and fix the weak fields while changes are still free.

Step 7 — Give the reviewer a clean path in

Working demo credentials, a note explaining any gated feature, and a build that does not crash on first launch. Most "mystery" rejections are a reviewer who could not sign in.

Step 8 — Instrument before you submit, not after

Analytics added after launch cannot tell you what happened during launch. Put your event schema in the first build so that install-to-activation, paywall views and purchase outcomes are measurable from day one. Wire the events before you publish Rork app builds to the store — our guide to app analytics for AI-built apps lists the eleven events worth capturing and the seven numbers that matter in month one.

Step 9 — Submit, then plan the second submission

Most reviews complete in 24 to 48 hours, and Apple reports over 90% inside a day. Peak periods — the weeks before Christmas, or straight after a new iOS release — can stretch to several weeks. Assume one rejection in your timeline and you will rarely be wrong.

Common questions founders ask

How much does it cost to publish an app?

Apple charges $99 a year for the Developer Program; Google Play charges $25 once. Beyond that, the real cost is the work between "the build runs" and "the listing is approved" — native features, in-app purchase plumbing, compliance pages and creative.

Can I publish an app for free?

No on iOS: the developer membership is mandatory even for a free app. You can distribute internally to up to 100 devices, or via TestFlight to 10,000 external testers, but public App Store distribution requires the paid membership.

How long does the whole thing take?

With the account already open and a native layer in place, a Rork app can be submission-ready in a few days. Apple's review adds 24 to 48 hours on top. Organisation enrolment and a first rejection are the two things that turn days into weeks.

What we do

Wanilla runs this end to end for founders who would rather ship than learn App Store Connect. We take the app you built, add the native layer, build and wire the paywall, prepare the listing and submit it under your account — fixed fee, days not months.

If you have a Rork build sitting in TestFlight and no clear route to the store, book a free launch review and we will tell you exactly what is missing.