Do’s and Don’ts When Submitting Your First iOS App (Real Advice from iOS Developers)
Submitting your first iOS app to the App Store is exciting—and a little terrifying. If you’ve never gone through Apple’s review process before, it’s normal to feel unsure about what to expect, how strict Apple really is, and how painful rejections might be. Based on real discussions from experienced developers in the iOS community, here’s a practical, no-nonsense guide to the **do’s and don’ts of submitting your first iOS app**—what actually matters, what Apple cares about, and how to avoid com
Do’s and Don’ts When Submitting Your First iOS App (Real Advice from iOS Developers)
Submitting your first iOS app to the App Store is exciting—and a little terrifying. If you’ve never gone through Apple’s review process before, it’s normal to feel unsure about what to expect, how strict Apple really is, and how painful rejections might be.
Based on real discussions from experienced developers in the iOS community, here’s a practical, no-nonsense guide to the do’s and don’ts of submitting your first iOS app—what actually matters, what Apple cares about, and how to avoid common mistakes.
The Most Important Mindset Shift
Before any checklist, understand this:
Apple cares about the user, not you as a developer.
If you frame every decision around user experience, clarity, and trust, you’ll already be aligned with how App Store reviewers think.
DO: Read the App Store Review Guidelines (Seriously)
This sounds obvious, but it’s the single most repeated advice from experienced developers.
The App Store Review Guidelines:
- Explain the most common rejection reasons
- Define required language for permissions, payments, and data usage
- Spell out what Apple considers spam, deception, or low-quality apps
Most rejections are not “random”—they’re directly tied to something in the guidelines.
Tip: Skim first, then re-read sections relevant to:
- Permissions (location, camera, notifications)
- Payments / subscriptions
- User-generated content
- Data usage & privacy
DO: Submit a Fully Complete App
One of the fastest ways to get rejected is submitting an app that feels unfinished.
Apple does not allow:
- “Coming soon” screens
- Dead buttons or links
- Placeholder content
- Features that don’t actually work
Rule of thumb:
If a user can tap it, it must do something meaningful.
DO: Prepare Your App Store Assets in Advance
You’ll need:
- App Store screenshots (iPhone, and iPad if supported)
- A clear app description
- A privacy policy URL
- Terms of use (if applicable)
You can edit most store listing content later, but your first submission should still look professional and complete.
DO: Explain Things to the Reviewer (Use the Notes Field)
Many developers overlook this.
In App Store Connect, you can leave notes for the reviewer. Use this space to:
- Explain unusual behavior
- Describe how to test key features
- Mention demo accounts or test credentials
- Clarify what makes your app unique
Reviewers are human. Context helps.
DO: Expect Rejection (It’s Normal)
Almost everyone gets rejected at least once—often multiple times.
Experienced developers report:
- 1–4 rejections is common
- Rejections are usually for small, fixable issues
- Subsequent updates get reviewed faster
A rejection is not failure. It’s part of the process.
DO: Test Thoroughly Before Submitting
Testing is just as important as development.
Best practices:
- Use TestFlight
- Test on multiple devices and iOS versions
- Test edge cases (no internet, permissions denied, empty states)
- Make sure in-app purchases actually work
If you have in-app purchases, explicitly tell Apple to review them in the submission notes—otherwise they may be approved separately and not function correctly at launch.
DON’T: Hide Functionality or Surprise Users
Apple is very strict about transparency.
Don’t:
- Hide features behind undocumented gestures
- Enable functionality after approval without disclosure
- Collect data you didn’t clearly explain
- Ask for permissions without explaining why
If your app requests access, the reason must be clear and user-focused.
DON’T: Be Discouraged by Review Time
Review times vary:
- Could be 1 day
- Could be several days
- First apps sometimes take longer (even weeks)
One developer shared their first app was temporarily marked as rejected while still “waiting for review”—and later approved.
Be patient. Apple’s review system isn’t perfectly predictable.
DON’T: Copy Existing Apps Without Differentiation
Spam and copycat apps are a major rejection reason.
Apple does not like:
- The “1000th version” of the same app
- Minimal differentiation
- Obvious clones with cosmetic changes
If your app belongs to a crowded category, use the reviewer notes to explain what makes it different.
DON’T: Panic Over Minor Rejection Reasons
Some rejections are extremely specific:
- Exact wording on permission dialogs
- Attribution requi