ChecklistsDecember 20, 202510 min read

Mobile App Publishing Checklist: Everything You Need Before Submitting

A comprehensive, step-by-step checklist covering everything you need to verify before submitting your app to the App Store or Google Play.

Why You Need a Pre-Submission Checklist

The app submission process involves dozens of requirements spread across multiple systems (developer portals, store consoles, your codebase, and legal documents). Missing even one requirement means rejection, which adds days to your timeline while you fix the issue and wait for re-review. This checklist consolidates every requirement into a single, ordered sequence. Work through it from top to bottom before clicking 'Submit' — it covers the areas where 90% of rejections occur. Bookmark this page and use it for every app and every update you publish.

Developer Account Checklist

Before anything else, verify your developer accounts are in good standing. For Apple: confirm your Apple Developer Program membership is active and not expiring within the next 30 days. Verify your legal entity name and contact information are current. Ensure you have the Account Holder or Admin role in App Store Connect — Editor role can't create new apps. Check that your Agreements, Tax, and Banking information is complete (required for both free and paid apps). For Google Play: confirm your developer account is registered and verified. Complete the developer profile including physical address and contact email (Google now requires this for account verification). If publishing on behalf of an organization, ensure the organization details are verified. Check that your Google Payments merchant account is set up if you plan to sell paid apps or in-app purchases.

Code and Build Checklist

Your app's code must be production-ready. Remove all debug logging, test credentials, development API endpoints, and console.log statements that expose sensitive information. Verify environment variables point to production servers, not development or staging. Ensure no development-only features are accessible (React Native dev menu, Flutter debug banner, etc.). Set the correct version number and build number — both must be higher than any previous submission. For iOS: build with the latest stable version of Xcode. Ensure your deployment target is set appropriately (dropping very old iOS versions is acceptable and recommended). Archive the app and validate it using Xcode's built-in validator before uploading. For Android: ensure targetSdkVersion meets Google's current requirement (API 34+). Build an Android App Bundle (AAB), not an APK. Run lint checks to catch common issues. Test the release build with ProGuard/R8 enabled to verify that obfuscation doesn't break runtime functionality.

Code Signing Checklist

Code signing issues are the most common technical blocker for first-time publishers. For iOS: verify your distribution certificate is valid and not expiring soon. Confirm the provisioning profile is for App Store distribution (not development or ad hoc). Ensure the bundle identifier in your project matches the App ID registered in the Apple Developer portal. If using automatic signing, verify Xcode shows a green checkmark under Signing & Capabilities with no warnings. If using manual signing, double-check that the provisioning profile includes the correct certificate and App ID. For Android: ensure your upload keystore file is securely backed up in at least two locations. Verify the keystore password, key alias, and key password are documented somewhere secure. Confirm Play App Signing is enabled for your app in Google Play Console. Test that the signed AAB installs and runs correctly on a device using bundletool.

Store Listing Assets Checklist

Both platforms require specific assets, and missing any one of them blocks submission. For Apple App Store: app icon at 1024x1024 px (no transparency, no rounded corners — Apple applies the rounding). Screenshots for required device sizes: 6.7-inch iPhone (1290 x 2796 px), 5.5-inch iPhone (1242 x 2208 px). iPad screenshots required if your app supports iPad. App preview videos are optional but recommended (15-30 seconds, captured on-device). For Google Play: app icon at 512x512 px. Feature graphic at 1024x500 px (appears prominently in store listing). At least 2 phone screenshots (JPEG or PNG, minimum 320px, maximum 3840px on any side). Tablet and Chromebook screenshots are optional but recommended for broader reach. For both platforms: app name within character limits (30 on iOS, 50 on Android). Short description (30-character subtitle on iOS, 80 characters on Android). Full description (up to 4,000 characters on both). Privacy policy URL (must be a live, accessible webpage).

Compliance and Legal Checklist

Compliance issues cause some of the most frustrating rejections because they often require non-code changes. Privacy policy: must be hosted at a publicly accessible URL (not behind a login). Must accurately describe all data collection, including data collected by third-party SDKs. Must include your contact information and the date it was last updated. Data privacy declarations: complete Apple's App Privacy nutrition labels in App Store Connect. Complete Google Play's Data Safety section. Audit every third-party SDK in your project for data collection — check each SDK's privacy documentation. Content rating: complete the IARC questionnaire on Google Play. Complete Apple's age rating questionnaire in App Store Connect. Answer honestly — misrepresenting content ratings can lead to app removal. Export compliance: answer Apple's export compliance questions (most apps using standard HTTPS encryption can select 'Yes' to the exemption). For Android, similar export regulations apply but are handled differently. If your app targets children (under 13 in the US, under 16 in the EU), additional COPPA and GDPR-K requirements apply on both platforms.

Testing Checklist

Test the exact build you're submitting, not a different build. Install the release/production build on a physical device (not a simulator or emulator). Verify app launches without crashing. Test all core user flows from start to finish. Test with no network connection — the app should handle offline gracefully, showing appropriate error messages rather than crashing or hanging. Test with slow network (both platforms' developer tools can simulate this). If your app requires login, test the complete registration and login flow. Test in-app purchases in the sandbox/test environment. Verify all links (privacy policy, terms of service, support URLs) open correctly. Test push notifications if applicable. On iOS: test on the latest iOS version and at least one older supported version. On Android: test on Android 12+ and verify the app works with different screen sizes and display densities. Check that your app doesn't request permissions it doesn't need — both platforms flag excessive permission requests.

Final Pre-Submit Checklist

Before clicking submit, do these final checks. Review notes for reviewers: provide clear instructions on how to test your app. Include demo account credentials (username and password) if login is required. Explain any non-obvious features or functionality. If your app requires specific hardware (Bluetooth, NFC, camera), note this so reviewers can test on appropriate devices. Verify your contact information is current in both App Store Connect and Google Play Console — reviewers may contact you with questions. Double-check your release settings: on iOS, choose between automatic release (goes live after approval) or manual release (you control when it goes live). On Google Play, choose your rollout percentage for production (100% for full rollout, or a smaller percentage for staged rollout). Take a deep breath. You've done the work. Submit.

Key Takeaways

  • Complete developer account setup, including tax and banking info, before attempting submission
  • Remove all debug code, test credentials, and development endpoints from production builds
  • Verify code signing is correctly configured — this is the #1 technical blocker for first-time publishers
  • Prepare all required assets: icons, screenshots, descriptions, and privacy policy URL
  • Test the exact production build you're submitting on a physical device with various network conditions

Related Framework Guides

Don't want to deal with this? Let us publish your app.

Our publishing experts handle the entire process — from developer accounts and code signing to store optimization and review management.

More Articles