How to Submit Your App to the App Store in 2026: Step-by-Step Guide, Requirements & Approval Tips
Submitting an iOS app to the Apple App Store requires completing seven sequential steps: enrolling in the Apple Developer Program, configuring code signing in Xcode, creating an app record in App Store Connect, testing via TestFlight, uploading your build through Xcode Organizer, configuring metadata and privacy declarations, and submitting for Apple review. Each step has specific technical requirements. Missing any single one causes rejection or delays.
The process applies whether you are submitting a brand-new app or a major version update. Minor updates follow the same path but skip some one-time setup steps, such as Bundle ID registration. This guide covers every step in sequence, including Apple-specific tools, common reasons for rejection, and what to do in the first 72 hours after approval.
What You Need to Know Before Submitting to the App Store
Before touching Xcode or App Store Connect, three foundational requirements must be in place: an active Apple Developer Program membership, a Mac running a supported version of macOS, and an app build that passes Apple’s App Review Guidelines. All three are non-negotiable.
Apple updates its App Review Guidelines regularly. Developers should check the current version before submission, particularly sections covering data privacy, in-app purchases, and minimum functionality standards.
Apple Developer Program: Individual vs. Organization Accounts
The Apple Developer Program costs $99 USD per year and grants access to App Store Connect, Xcode capabilities, TestFlight, and the full distribution toolchain. Individual accounts are registered under a personal legal name. Organization accounts require a D-U-N-S Number issued by Dun & Bradstreet and display the company’s legal name on the App Store.
Choosing the wrong account type is a common early mistake. If you intend to publish under a business name, register as an organization. Apple does not allow account-type changes after enrollment. Enterprise accounts (Apple Developer Enterprise Program) are separate and cannot distribute apps on the public App Store.
App Store Requirements Checklist Before You Begin
Apple enforces both technical and content requirements at submission. The most frequently violated technical requirements include:
- App binary compiled for arm64 architecture using Xcode 15 or later
- Privacy manifest file (PrivacyInfo.xcprivacy) included for any use of required reason APIs
- App Transport Security (ATS) compliance for all network connections
- Support for the two most recent major iOS versions
- All referenced URLs, support links, and marketing links must be live and accessible
- App icons provided at all required resolutions, including 1024x1024px for the App Store
Content requirements include a complete privacy policy URL, accurate age rating declarations, and compliance with Apple’s guidelines on user-generated content, payments, and third-party SDKs.
Understanding Apple’s App Review Guidelines (2026 Updates)
Apple’s guidelines are organized into five categories: Safety, Performance, Business, Design, and Legal. The most frequently cited rejection categories in recent years are Guideline 2.1 (Performance: crashes and bugs), Guideline 5.1.1 (Privacy: data collection), and Guideline 4.3 (Spam: duplicate apps).
In 2024 and 2025, Apple added stricter requirements around AI-generated content disclosure, third-party SDK privacy nutrition labels, and app functionality minimum standards. Apps that primarily display web content without native functionality are routinely rejected under Guideline 2.3.1.
Step 1: Set Up Code Signing | Distribution Certificate and Provisioning Profile
Code signing is the mechanism Apple uses to verify that an iOS app binary has not been tampered with and originates from a known, enrolled developer. Without valid code signing, Xcode cannot export a distribution build, and App Store Connect cannot process the upload.
Code signing involves three linked components: a Distribution Certificate, an App ID (Bundle Identifier), and a Distribution Provisioning Profile. All three are managed through the Apple Developer Portal.
How to Create an iOS Distribution Certificate in Xcode
Xcode can automatically manage certificates and profiles if Automatic Signing is enabled under the target’s Signing & Capabilities tab. This is the recommended approach for most developers. Xcode generates a Distribution Certificate, stores it in your macOS Keychain, and links it to your Apple ID.
For manual management, navigate to Xcode > Settings > Accounts, select your Apple ID, and click Manage Certificates. Add an Apple Distribution certificate. This certificate is then referenced by your provisioning profile and must remain in your Keychain on any Mac used for building distribution builds.
Creating an App Store Distribution Provisioning Profile
A provisioning profile ties together your App ID, Distribution Certificate, and distribution type (App Store, Ad Hoc, or Enterprise). For App Store submission, create an App Store Distribution Provisioning Profile in the Apple Developer Portal under Certificates, Identifiers & Profiles.
The profile must reference an App ID that exactly matches your app’s Bundle Identifier. Wildcard App IDs (using an asterisk) are not compatible with push notifications, Apple Sign In, in-app purchases, or several other entitlements. Register an explicit App ID if your app uses any of these capabilities.
Registering Your App Identifier (Bundle ID) in Apple Developer Portal
The Bundle Identifier is a reverse-domain string (for example, com.companyname.appname) that uniquely identifies your app across the Apple ecosystem. Register it once in the Apple Developer Portal under Identifiers. Enable all capabilities your app uses at this stage, including Push Notifications, Sign In with Apple, HealthKit, and others.
Capability mismatches between your Xcode project entitlements file (.entitlements) and the registered App ID cause immediate validation errors during upload. Verify both match before archiving.
Step 2: Create Your App Record in App Store Connect
App Store Connect is Apple’s web-based portal for managing app submissions, TestFlight builds, sales data, and review communications. Every app on the App Store has a corresponding record in App Store Connect that holds its metadata, build history, and review status.
Access App Store Connect at appstoreconnect.apple.com using your Apple ID enrolled in the Developer Program. If your team uses multiple roles, the Account Holder or Admin role is required to create a new app record.
How to Add a New App in App Store Connect
From the App Store Connect dashboard, select My Apps and click the + button to create a new app. You will need to specify the platform (iOS, iPadOS, macOS, or tvOS), the app name as it will appear on the App Store (maximum 30 characters), the primary language, the Bundle ID registered in the Developer Portal, and a unique SKU for internal tracking.
The app name is one of the most important ASO (App Store Optimization) fields. It directly affects keyword indexing on the App Store search algorithm. Choose a name that includes the primary keyword category while remaining brandable. Apple does not allow keyword stuffing in app names.
Setting Pricing, Availability, and Distribution Territories
Under the Pricing and Availability section, set the base price tier. Apple uses 800+ price tiers synchronized across 175 storefronts. A free app is Tier 0. Paid tiers start at $0.99 USD and follow Apple’s pricing matrix.
For geographic distribution, you can limit availability to specific countries. Apps targeting regulated industries (healthcare, financial services, or education) often restrict availability to jurisdictions where they hold required certifications or meet data residency requirements.
Configuring In-App Purchases in App Store Connect
If your app monetizes through subscriptions, consumables, or non-consumable purchases, configure these in App Store Connect before submission. In-app purchase items must be approved by Apple as part of the app review process. Submitting an app with in-app purchase references that have not been created in App Store Connect causes a metadata rejection.
Auto-renewable subscriptions require a subscription group, a free trial or introductory offer configuration, and a localized description for each market. Apple’s StoreKit 2 framework handles the client-side transaction logic for iOS 15 and later.
Step 3: Best Practices for Testing Your iOS App Before Submission
Apple’s automated review pipeline rejects builds that crash on launch, fail core functionality, or display visual layout issues on supported devices. Thorough pre-submission testing is the single most effective way to avoid an initial rejection, which adds one to three days to your timeline.
Testing should cover functional correctness, performance benchmarks, accessibility compliance, and edge-case user flows. The goal is to replicate the conditions Apple’s reviewers encounter when they evaluate your app.
Using Xcode Instruments to Find Performance Bottlenecks
Xcode Instruments is Apple’s profiling and diagnostics toolset, included in the Xcode IDE. It provides real-time measurements for CPU usage, memory allocation, energy consumption, and network activity. The Time Profiler instrument identifies functions consuming disproportionate CPU time. The Allocations instrument tracks heap memory and detects memory leaks.
Apple has published performance benchmarks that apps are expected to meet. Launch time should be under 400 milliseconds from process start to first meaningful render. Apps consuming sustained high CPU or excessive background energy are flagged by both automated testing and human reviewers. Run instruments on a physical device, not the iOS Simulator, for accurate measurements.
How to Distribute a Beta Build via TestFlight
TestFlight is Apple’s official beta testing platform, integrated directly with App Store Connect. Internal testers (up to 100 members of your App Store Connect team) receive builds immediately after upload. External testers (up to 10,000 users) require a TestFlight review, which typically takes 24 to 48 hours.
Upload a TestFlight build using the same Xcode archive and export process used for App Store submission. This ensures the exact same binary is tested. Builds on TestFlight expire after 90 days. Use TestFlight’s crash reporting and session data to identify issues before submitting the production build.
App Store Best Practices: What Apple Reviewers Actually Look For
Apple reviewers follow a structured evaluation against the App Review Guidelines. Based on Apple’s published rejection statistics and developer communications, the highest-risk areas include apps that require login before demonstrating core functionality, apps with placeholder content or incomplete features, and apps that reference competing platforms.
Provide demo account credentials in the App Review Information section of App Store Connect if your app requires authentication. Without them, reviewers cannot access gated features and will reject the build under Guideline 2.1. Use the Review Notes field to explain any non-obvious flows, hardware requirements, or special configurations the reviewer needs to know.
Accessibility Testing Checklist for iOS Apps (VoiceOver and Dynamic Type)
Apple requires that apps function correctly with accessibility features enabled. VoiceOver is the screen reader built into iOS. All interactive UI elements must have descriptive accessibility labels. Buttons with only icon imagery must include accessibilityLabel values in code. Test VoiceOver navigation by enabling it in iOS Settings > Accessibility > VoiceOver.
Dynamic Type allows users to increase or decrease the system font size. Apps that use custom fonts or fixed-size labels frequently clip or overlap text when Dynamic Type is at larger scales. Use UIFontMetrics in UIKit or the scaledFont modifier in SwiftUI to ensure text scales correctly. Accessibility testing is part of Guideline 3.1 (Design: User Interface Design).
Memory, Battery, and Network Performance Benchmarks Apple Expects
Apps should not exceed 200MB of memory usage on baseline supported devices under normal operation. Background processes must implement Background App Refresh correctly or terminate cleanly. Apps that maintain unnecessary background network connections or location services without user-facing justification are rejected under Guideline 2.4 (Hardware Compatibility).
For network performance, implement retry logic with exponential backoff, handle no-network states gracefully with appropriate UI messaging, and avoid performing network-intensive operations on the main thread. Use URLSession with background configuration for large file transfers.
Step 4: Archive and Upload Your App Build Using Xcode
The archive process in Xcode compiles your app with the distribution configuration, packages it as an .xcarchive bundle, and prepares it for export. The resulting .ipa file is what gets submitted to App Store Connect.
How to Archive Your App in Xcode
In Xcode, set the scheme destination to Any iOS Device (arm64) rather than a simulator. Select Product > Archive from the menu bar. Xcode builds the app with the Release configuration and opens the Organizer window when complete. The Organizer lists all archives with timestamps.
Before archiving, verify the version number and build number in the target’s General tab. App Store Connect rejects uploads where the build number has already been used for that version string. Increment the build number (CFBundleVersion) for every upload, even if the version string (CFBundleShortVersionString) stays the same.
Validating and Uploading Your Build via Xcode Organizer
In the Organizer window, select the archive and click Distribute App. Choose App Store Connect as the distribution method. Select Upload. Xcode validates the binary against App Store requirements, checks entitlements, verifies the provisioning profile, and uploads the build if all checks pass.
The validation step catches common issues before upload: missing privacy manifest files, unsupported architectures, expired certificates, and missing exported symbols. Address any validation errors before attempting the upload. After a successful upload, the build appears in App Store Connect under TestFlight or the app version within minutes to an hour.
Common Upload Errors and How to Fix Them
The most frequent upload errors include: ITMS-90338 (non-public API usage), ITMS-90683 (missing purpose string for privacy-sensitive APIs), ITMS-90809 (deprecated API usage that will be rejected in a future review), and ITMS-91053 (missing privacy manifest for third-party SDK).
ITMS-90338 errors caused by third-party SDKs require contacting the SDK vendor for an updated version or removing the SDK. Apple’s PrivacyInfo.xcprivacy format for privacy manifests was mandated beginning with the spring 2024 deadline for all apps using required reason APIs.
Step 5: Configure Metadata, App Store Listing Assets, and Privacy Declarations
The App Store listing is both a discovery surface and an evaluation tool. Apple reviewers check that the metadata accurately represents the app’s functionality. Inconsistencies between screenshots and actual app behavior cause rejection under Guideline 2.3 (Accurate Metadata).
App Name, Subtitle, Description, and Keywords: ASO for the App Store
The App Store search algorithm indexes three text fields: the app name (30 characters), the subtitle (30 characters), and the keyword field (100 characters). The long description is not indexed by the App Store search algorithm but is visible to users and affects conversion rates.
Avoid repeating words across the name, subtitle, and keyword fields. The algorithm treats repetition as a waste of character budget. Use the keyword field for secondary terms not already present in the name or subtitle. Tools such as AppFollow, Sensor Tower, and AppTweak provide keyword volume data specific to the App Store search index.
Screenshot and App Preview Video Specs for Every iPhone and iPad Size
Apple requires screenshots for at least one iPhone size (6.9-inch display for 2026 submissions) and optionally one iPad size. Screenshots sized for larger displays are auto-scaled for smaller ones. Provide device-specific screenshots to maximize visual quality across storefronts.
App Preview videos must be 15 to 30 seconds in length, recorded on device or using the iOS Simulator screen recording, and exported in H.264 or HEVC format at 30fps. Preview videos autoplay in search results and significantly affect conversion rate. The first three seconds are the most critical for retaining viewer attention.
Setting Age Ratings and Content Descriptors Correctly
Age ratings in App Store Connect are determined by a questionnaire about content categories: cartoon or fantasy violence, realistic violence, sexual content, profanity, alcohol and drugs, horror, and gambling. Apple generates the rating based on the answers. Misrepresenting content to receive a lower rating is a permanent ban-level violation.
Apps containing user-generated content must check the Unrestricted Web Access and/or User-Generated Content boxes in the rating questionnaire. This automatically applies a 17+ rating unless the app implements content filtering and reporting mechanisms.
App Privacy Nutrition Labels: Data Types, Tracking Disclosures, and Privacy Policy
Apple’s privacy nutrition labels require developers to declare every data type collected by the app and each third-party SDK integrated into the binary. Categories include contact info, health and fitness, financial info, location, sensitive info, and identifiers such as Device ID.
Data linked to a user’s identity and used for tracking must be separately declared in the tracking disclosure section. Apps using the AppTrackingTransparency framework to request IDFA access must declare this. The privacy policy URL is mandatory for all apps. Apple verifies that the URL resolves and that the policy covers the data categories declared in the nutrition label.
App Store Category Selection Strategy and Discovery Impact
Every app is assigned a primary category and an optional secondary category from Apple’s fixed taxonomy. Category choice affects which charts the app appears on and which editorial placements it is eligible for. For apps that bridge two categories (for example, a fitness app with social features), the primary category should reflect the core use case driving the most engagement.
Some categories have significantly lower competition density than others. A utility app listed under Productivity may rank more easily than the same app listed under Lifestyle. Review the Top Charts in candidate categories before finalizing the selection.
Step 6: Pre-Submission Internal Review | Simulate the Reviewer’s Exact Flow
This step is not covered in most submission guides, but it is one of the highest-leverage actions before hitting submit. Apple’s reviewers follow a structured evaluation script. Developers who simulate this evaluation before submission catch issues that automated testing and unit tests miss.
Running Apple’s Automated App Validation in Xcode Before Submitting
Xcode’s Validate App option in the Organizer runs the same automated checks as App Store Connect without actually submitting the binary. This catches bitcode issues, entitlement conflicts, missing provisioning profile capabilities, and privacy manifest gaps before the build is uploaded.
Run validation after every major change to the binary. A build that passes local validation still needs to pass App Store Connect’s additional server-side checks, but local validation eliminates the most common failure modes.
Simulating the Reviewer’s Exact Flow
Apple reviewers typically test apps on a physical device running the latest available iOS version. They follow the onboarding flow without prior knowledge of the app. Conduct a structured walkthrough: install the app fresh (delete and reinstall), complete onboarding without any pre-existing account, attempt every primary use case listed in your app description, and trigger at least one error state (for example, entering invalid input or testing offline behavior).
Common issues found during this simulation include onboarding flows that assume prior context, broken password reset flows, in-app purchase restore functionality that is not accessible, and missing required features mentioned in the description or screenshots.
Demo Account Credentials and Review Notes for Apple’s Team
In App Store Connect, the App Review Information section includes fields for demo account username, password, and review notes. Provide working credentials for any gated content. If the app integrates hardware (for example, Bluetooth peripherals or IoT devices), note this clearly and explain how reviewers should test without the hardware.
Review notes are plain text, with a 4000-character limit. Use them to explain flows that are not self-evident, the regulatory context, or test environment specifics. Reviewers cite inadequate review notes as a contributing factor in many metadata rejections.
Step 7: Submit Your App for Apple Review
Submission is initiated in App Store Connect under the app version record. Add the uploaded build to the version, complete all required fields (including what’s new in this version for updates), verify the App Review Information, and click Submit for Review.
Manual vs. Automatic Release After Approval
App Store Connect offers two release timing options: release automatically after approval, or hold for manual release. Manual release allows you to coordinate the live date with marketing campaigns, press coverage, and support readiness. The manual release hold expires after 30 days. If not released manually within that window, you must resubmit.
Phased Release: Rolling Out to a Percentage of Users
Phased release distributes an update to a gradually increasing percentage of existing users over seven days: 1% on day one, growing to 2%, 5%, 10%, 20%, 50%, and 100% by day seven. New users always receive the latest version regardless of the phased release schedule.
Phased release is only available for updates to existing apps, not initial submissions. It provides an opportunity to monitor crash rates and user reviews at low volume before full rollout. You can pause or stop a phased release at any time in App Store Connect if a critical issue is discovered post-launch.
Understanding the Apple App Store Review Process in 2026
The Apple App Store review process has two distinct stages: automated binary analysis and human review. Understanding both stages helps developers predict timelines and prepare accordingly.
What Is the Apple App Store Approval Process Step by Step?
After submission, the build enters a queue. Apple’s automated systems run binary analysis checks covering malware scanning, API usage validation, entitlement verification, and privacy manifest compliance. Builds that pass automated checks move to human review, where Apple staff evaluate the app against the full App Review Guidelines.
Human reviewers test the app on physical devices, evaluate the metadata for accuracy, check the privacy declarations against observed behavior, and verify in-app purchase implementations. The review process is sequential, not parallel. A rejection at any stage sends the app back to the developer with a written reason.
How Long Does the App Store Review Take in 2026?
As of 2025 and into 2026, Apple’s published App Store Review Statistics indicate that approximately 90% of submissions receive a review decision within 24 hours and 98% within 48 hours. Initial submissions and apps with in-app purchases or complex privacy declarations may take longer. Expedited review requests are available for critical bug fixes through App Store Connect.
Review times increase during Apple’s major product launch periods (typically September through November) and around the December holiday season due to volume spikes. Plan submission timelines to avoid these windows if launch timing is critical.
What Happens During Apple’s Automated vs. Human Review Stages?
Automated review handles binary-level checks: prohibited API scans, obfuscated code detection, third-party SDK privacy manifest audits, and entitlement consistency checks. These are completed within minutes of upload. The vast majority of ITMS error codes (upload validation failures) originate from this stage.
Human review evaluates functional quality, metadata accuracy, user interface design compliance, business model legitimacy, and privacy practice alignment. Human reviewers also evaluate whether AI-generated content is properly disclosed, a requirement Apple has enforced since 2024.
How to Check Your App Review Status in App Store Connect
In App Store Connect, navigate to the app version record. The status field shows one of several states: Prepare for Submission, Waiting for Review, In Review, Pending Developer Release, Ready for Sale, or Rejected. Email notifications are sent for each status transition if enabled in notification settings.
The Resolution Center in App Store Connect is where Apple communicates rejection details and where developers submit responses or appeals. Every rejection message includes the specific guideline violated and, for most rejections, a description of the observed issue.
Top Reasons Apps Get Rejected and How to Avoid Them
Apple publishes rejection statistics periodically. The most common rejection categories remain consistent across years. Understanding the specific guideline violations reduces resubmission cycles and total time to market.
Guideline 2.1: Performance : Crashes, Bugs, and Broken Links
Guideline 2.1: Rejections occur when the app crashes during the reviewer’s evaluation, exhibits broken functionality, contains placeholder content, or includes non-functional links. This is the single most common rejection category. Addressing it requires comprehensive testing on physical devices running the latest iOS and iPadOS versions.
Test every screen state, including empty states, error states, and loading states. Broken support URLs, inaccessible privacy policy pages, and non-functional logout flows are frequently cited under 2.1. All linked URLs must resolve to live content before submission.
Guideline 5.1.1: Data Collection and Privacy Violations
Guideline 5.1.1 covers user data collection practices. Common violations include collecting location data without a visible, user-facing justification, accessing contacts or photos without a clear use case, and integrating third-party analytics SDKs that collect data types not declared in the privacy nutrition label.
Apple cross-references the declared data types in App Store Connect with the actual data access patterns detected in the binary. Using an SDK that accesses the advertising identifier (IDFA) without declaring it in the tracking section of the nutrition label triggers a 5.1.1 rejection.
Guideline 4.3: Spam and Duplicate App Rejections
Guideline 4.3 targets apps that replicate existing App Store functionality without meaningful differentiation, submit multiple similar apps under the same developer account, or use templates to generate low-effort apps at scale. Apple applies 4.3 broadly to apps that function primarily as thin wrappers around web content without native value.
Building meaningful differentiation requires native functionality, original user interface design, and content or services that are not trivially replicable by opening a URL in Safari. Apps built for a single, specific business use case (such as a booking or ordering app for a specific business) are generally exempt from 4.3 if they provide genuine utility.
How to Respond to a Rejection and Use the App Review Appeals Process
Upon receiving a rejection, the developer has three options: fix the cited issue and resubmit, provide clarifying information through the Resolution Center if the rejection appears to be based on a misunderstanding, or formally appeal through the App Review Board if the guideline application is disputed.
The App Review Board, accessible through App Store Connect, handles formal appeals for disputes about guideline interpretation. Appeals are evaluated by a separate review team. Submit an appeal with specific reference to the guideline text, an explanation of why the app complies, and any supporting materials. Apple typically responds to appeals within five to seven business days.
After Approval: What to Do in the First 72 Hours on the App Store
Most post-launch guides focus on long-term growth. The first 72 hours require a different, operationally focused response. Launch day concentrates a disproportionate percentage of new user installs, which means issues surface faster and at higher volume than during testing.
Monitoring Crashes and ANRs with Xcode Organizer Post-Launch
Xcode Organizer’s Crashes tab aggregates crash reports from users who have opted into sharing diagnostic data with Apple. Crashes are symbolicated automatically if you have the corresponding .dSYM debug symbol files, which Xcode archives alongside each build.
Prioritize crashes with the highest occurrence count and the widest device and OS distribution. A crash affecting only one device type on an older OS version is lower severity than one occurring on the latest iPhone across all users. Create a fix build immediately for P1 crashes and expedite the review and submission.
Responding to Early User Reviews to Improve App Store Rating
App Store ratings affect App Store search ranking and conversion rate. Early reviews disproportionately shape the app’s overall rating because there are fewer total reviews to average against. Respond to negative reviews through App Store Connect within 24 hours, where possible.
Use the SKStoreReviewRequestAPI to prompt satisfied users for a review at a contextually appropriate moment, such as after a completed action or successful transaction. Apple permits a maximum of three review prompts per 365-day period. Prompting at low-satisfaction moments produces negative reviews.
Using App Store Analytics to Track Day-1 Conversion and Acquisition
App Store Connect Analytics provides impression-to-download conversion data broken down by traffic source: App Store Browse, App Store Search, App Referrer, and Web Referrer. Day-1 data reveals which acquisition channels are performing and whether the store listing is converting at an acceptable rate.
Industry benchmarks for App Store conversion rate vary significantly by category. Utility and productivity apps average 30 to 40% conversion from product page views to downloads. Games average 25 to 35%. If conversion is significantly below category benchmarks, the priority is iterating on screenshots, the subtitle, or the preview video rather than driving more traffic.
How Our iOS App Development Team Handles App Store Submission for You
At Premium App Developer, our iOS app development team manages the complete App Store submission workflow as part of every project delivery. This includes code signing configuration, TestFlight beta distribution, metadata optimization, and post-submission support through the review process.
For startups validating an idea, our MVP development service includes App Store submission as a defined deliverable, so founders receive a live, approved app without navigating the technical requirements independently.
End-to-End iOS App Development and Submission Services in the USA
Our mobile app development services are based in the United States and cover the full development lifecycle from requirements to App Store approval. We have submitted apps across categories, including healthcare, fintech, e-commerce, and logistics.
For cross-platform projects, we build using React Native or Flutter, both of which produce iOS binaries fully compatible with App Store Connect’s submission requirements. Our Android app development team handles Google Play submission in parallel when both platforms are targeted.
To discuss your project, contact our team for a free consultation.
Frequently Asked Questions About Submitting Apps to the App Store
How much does it cost to submit an app to the App Store?
The Apple Developer Program costs $99 USD per year. This fee covers all app submissions under the account. There is no per-submission fee. Apple takes a 30% commission on paid app purchases and in-app purchases, reduced to 15% for developers earning under $1 million USD per year through the Small Business Program.
What are the App Store requirements for submission?
Minimum requirements include: an Apple Developer Program membership, an app built with Xcode 15 or later targeting iOS 16 or later, a valid Distribution Certificate and Provisioning Profile, a privacy manifest file for any required reason API usage, a privacy policy URL, accurate App Store metadata, and compliance with Apple’s App Review Guidelines.
How long does the Apple App Store approval process take?
Apple approves approximately 90% of submissions within 24 hours and 98% within 48 hours. Initial submissions, apps with in-app purchases, and apps with complex privacy declarations may take longer. Expedited review is available for critical bug fixes. Review times are longer during major Apple product launch windows.
What are the best practices for testing apps for the Apple App Store?
Best practices include: running Xcode Instruments to identify memory leaks and performance issues, distributing a TestFlight build to at least 20 external testers across multiple device types, testing VoiceOver and Dynamic Type accessibility compliance, verifying all linked URLs are live, simulating the reviewer’s onboarding flow on a freshly installed device, and providing working demo credentials in App Store Connect Review Notes.
Can you resubmit an app after App Store rejection?
Yes. After resolving the cited issue, resubmit through App Store Connect by selecting the rejected version and clicking Submit for Review again. If the rejection is based on a guideline interpretation dispute rather than an actual violation, use the Resolution Center to provide clarifying information or submit a formal appeal through the App Review Board.
Is it hard to get an app approved on the App Store?
For apps that follow the App Review Guidelines and complete thorough pre-submission testing, initial approval is achievable in most cases. Apple’s App Store Review Statistics indicate that the vast majority of apps are approved. The most common rejection causes (crashes, privacy violations, and inaccurate metadata) are preventable with structured pre-submission testing and careful attention to Apple’s current guidelines.
Related Reading
How to Get Your App Approved on the App Store
Android App Development: Google Play Submission Guide
Flutter vs React Native 2026: Which to Choose?
How Much Does It Cost to Build an App in 2026?
