Finishing an app in Rork feels great right up until you decide to submit it to the App Store. Apple's review process has a learning curve, and the first submission is usually where first-time developers hit unexpected friction. Here's what I've learned through my own first submissions and the pattern I follow now to get through review efficiently.
Before You Start: Apple Developer Program
If you haven't already, you'll need to enroll in the Apple Developer Program — $99/year as of 2026. Both individuals and organizations can enroll.
After registering, expect the approval process to take a few hours to a day before your account is fully active. Build that time into your launch schedule.
Decide on a Bundle ID
Before submitting, choose your app's Bundle ID. This can't be changed later (changing it creates a new app entirely in the system).
The convention is com.{yourbrand}.{appname} — for example, com.dolice.myapp. Set this in Rork before exporting your project.
Exporting from Rork and Configuring Xcode
Use Rork's export feature to generate a native iOS project. Once you open it in Xcode, check the following:
Signing & Capabilities
Open TARGETS → General → Signing & Capabilities.
- Team: Select your Apple Developer account
- Bundle Identifier: Enter your Bundle ID
- Automatically manage signing: Check this on — Xcode will handle Provisioning Profiles for you
Keeping "Automatically manage signing" on is safest for initial submissions. Manual signing adds certificate management complexity that's easy to get wrong.
Minimum iOS Version
Check General → Deployment Info for the iOS minimum version. Setting this too high reduces your addressable audience. Review the default that Rork exports and adjust if needed.
Creating an Archive
With configuration done, go to Product → Archive to create a release build.
Before archiving, confirm that the destination in Xcode's upper-left is set to "Any iOS Device (arm64)" or a connected physical device — not a simulator. Archiving with a simulator selected doesn't work.
Setting Up App Store Connect
Log in to App Store Connect and create a new app.
Basic Information
- Name: The app name shown on the App Store (30 characters max)
- Primary Language: Your app's primary language
- Bundle ID: Select the Bundle ID you configured
- SKU: An internal identifier you choose (not visible to users)
The app name can be changed later, but changes after approval require a new review cycle. Use the final name from the start.
Age Rating
Work through the age rating questionnaire — it covers violence, sexual content, substances, and similar topics. The rating is calculated automatically from your answers.
Setting an inaccurate rating is a common rejection cause. If you're unsure, err toward a higher rating.
Pricing and Availability
- Price: Free or paid (paid apps use Apple's pricing tiers)
- Availability: Countries and regions where the app will be available
- Release: Auto-release after approval, or manual release
I recommend manual release for first submissions. It gives you a chance to confirm everything before going live after waiting through the review process.
Screenshots and Metadata
How your app looks on the App Store page directly affects both review outcomes and download rates. This is worth investing time in.
Required Screenshot Sizes
The minimum you need:
- 6.5-inch (iPhone 14 Pro Max and similar): 1290 × 2796px
- 5.5-inch (iPhone 8 Plus and similar): 1242 × 2208px
If your app runs on iPad, iPad screenshots are also required. Using Figma or a similar design tool to add device frames around your screenshots significantly improves the visual presentation.
App Preview Video
Optional, but a preview video helps reviewers understand the app faster. Keep it under 30 seconds and show the core functionality. A screen recording via QuickTime and basic trimming in iMovie is sufficient.
Writing the Description
The description is truncated after about 170 characters with a "more" link. Put your most important information in those first 170 characters:
[Short, clear description of what the app does]
Key Features:
• Feature A
• Feature B
• Feature C
Keywords are a separate field (100 characters). Don't stuff keywords into the description — they won't affect search ranking there.
Uploading the Build and Submitting for Review
Once App Store Connect is configured, upload your build from Xcode.
Go to Window → Organizer, select your archive, click "Distribute App" → "App Store Connect" → "Upload." The upload takes a few minutes.
The build appears in App Store Connect's Builds section within minutes to a few hours. Select it, connect it to your app version, and click "Submit for Review."
Review Timeline
Most reviews complete within 1–3 days. Peak times around major Apple events or holidays can stretch to a week or more. Check status under "App Store Review Status" in App Store Connect.
Common Rejection Reasons and How to Prevent Them
These show up frequently in first submissions.
Guideline 4.0 — Design (crashes and broken UI)
Any visible bugs, non-functional buttons, or crashes during review will result in rejection. Do a complete walkthrough on a physical device before submitting.
Guideline 2.1 — App Completeness (placeholder content)
Test content left in the app — "test," "Lorem ipsum," placeholder email addresses — signals an unfinished app. Replace all placeholder content before submitting.
Guideline 5.1.1 — Privacy Policy
Apps with accounts, location access, camera, or other data collection require a privacy policy. Add the policy URL to App Store Connect and link to it within the app (typically from a Settings or About screen).
Guideline 3.1.1 — In-App Purchase (external payment)
If you're using Stripe or another payment processor in your Rork app, the App Store version must use Apple's IAP system for purchases, not an external payment link. Plan your iOS submission strategy around this constraint early.
Handling a Rejection
Getting rejected doesn't affect your account standing. Here's how to respond efficiently:
- Click the Resolution Center link in the rejection email for the full explanation
- Fix the issue and describe what you changed in the Resolution Center
- Submit the updated build for re-review
If the rejection reason is unclear, you can ask follow-up questions in the Resolution Center. Apple's review team will often provide clarification.
From experience: explaining your reasoning clearly — especially for anything that might seem unusual — helps reviewers understand the intent and reduces back-and-forth.
After Launch: Updates and Momentum
Updating is simpler than the initial submission. Increment the version number in Xcode, create a new archive, upload, and submit. That's it.
Submitting regular updates — even small bug fixes — tends to improve App Store search visibility over time. Consistent updates signal an active, maintained app, which is a positive signal both for users and for the App Store algorithm.
For deeper monetization strategy — AdMob optimization, In-App Purchase design, user retention approaches — that's covered in detail in the Rork Lab membership articles. Worth a look once your app is live.