My Pre-Submission Checklist Before App Store Review
A practical pre-submission checklist for iOS App Store review, covering app metadata, privacy details, permissions, screenshots, Review Notes, backend status, and compatibility.
Contents
Building an app and submitting an app are related, but they are not the same job.
During development, the main question is whether the feature works. Before App Store review, there are more things to check: privacy policy, permission strings, screenshots, app description, backend status, test accounts, and Review Notes.
That is why I prefer having a pre-submission checklist.
This post is a practical list of what I want to check before submitting an iOS app for review. The scope is broader than the app binary itself.
Start With App Store Connect Metadata
The first thing I check is not the code. It is the information that appears in App Store Connect.
- App name and subtitle
- Description
- Keywords
- Category
- Age rating
- Support URL
- Privacy Policy URL
- Screenshots and app previews
These fields do not fail a build, which makes them easy to miss.
The Privacy Policy URL is especially important. The app needs a clear place that explains what data it handles, why it handles it, and how users can contact the developer.
Permission Strings Should Match Real Features
iOS apps need clear permission descriptions for things like camera, photos, location, and notifications.
Those strings are short, but they matter.
If the app asks for photo access, the user should understand why. The request should map directly to a real feature.
My checks are:
- Does the app request only the permissions it actually needs?
- Does each permission string explain the related feature?
- Are unused permission keys removed from
Info.plist? - Does the app still behave reasonably if the user denies permission?
Permissions should not be added "just in case." Unused permissions can become review and trust risks.
App Privacy Details Must Match the App
Apple shows privacy information on the App Store product page. Developers provide the app's data collection and usage details in App Store Connect.
The important part is accuracy.
If the app has accounts, comments, analytics, ads, push notifications, payments, or third-party SDKs, I need to understand what data is involved.
For a personal app, it is easy to assume there is not much to disclose. But small features can still matter from a data perspective.
Email support, anonymous analytics, ad SDKs, and server logs may all affect the privacy explanation.
Review Notes Are More Useful Than They Look
The reviewer is seeing the app for the first time.
What feels obvious to me may not be obvious to them. That is why Review Notes are useful for login instructions, test accounts, feature entry points, external requirements, or anything that may be misunderstood.
I want to include:
- Whether a test account is required
- Login credentials if needed
- Where the core feature can be found
- Whether a feature depends on backend data
- Anything that could be misunderstood during review
Review Notes are not an excuse. They are a short guide for the reviewer.
Backend Status Matters Too
Many apps depend on a backend.
If the app cannot load because the server is down during review, the app may look broken even if the binary itself is fine.
Before submission, I want to check:
- Production APIs respond correctly.
- No required feature is under maintenance.
- Test account data exists.
- Empty states look acceptable.
- Server changes do not break existing app versions.
This matters even more for a solo or small project. The same person may be handling the app, server, and release. That makes checklists useful.
Final Pass Before Submission
My final pass is from the user's perspective.
| Item | Check |
|---|---|
| First launch | Permissions, onboarding, empty states |
| Core feature | The app's main value is clear |
| Error handling | Network failures, empty data, retries |
| Links | Privacy Policy, support URL |
| Version | Build number and release notes |
App Review does not always finish exactly when I want. Reducing avoidable issues before submission is the practical move.
Summary
Preparing for App Store review is not only about testing features.
The submit button is simple. The preparation before that button is not.
A checklist is not exciting, but it is one of the best ways to reduce review delays and post-release problems.
References:
Comments
0