Publishing an app is a sequence of checks, not a single upload. A build can be accepted for processing while the app still needs privacy declarations, reviewer access, production-track approval or a release decision. Plan App Store submission and Google Play publishing alongside development rather than treating them as a final administrative task.
- Establish account ownership and responsibilities The business should know who owns the developer accounts, who can publish, and who provides legal and store-listing information. Invite developers through appropriate roles rather than sharing passwords or recovery codes. Complete required identity or business verification early.
Make a responsibility list for the app name, support contact, privacy policy, screenshots, age/content rating, data declarations and review notes. Developers can explain technical behavior, but the owner must confirm business facts and data practices. Allocate time for missing materials before announcing a fixed public launch date.
- Check current build requirements, not an old tutorial As of this review, Apple requires uploads to use Xcode 26 or later with the applicable version-26 SDK. Apple also lists a separate iOS/iPadOS deployment-target minimum of iOS 13. These are different concepts: the SDK used to build an app is not the minimum operating system your app or chosen framework supports. See Apple’s current requirements.
For standard Android phone and tablet apps, Google’s published requirement since August 31, 2026 is Android 16, API level 36, for new apps and updates. Other device categories have different thresholds. An existing app’s discoverability requirement is also distinct from submitting an update. Check the Google Play target API policy and the actual Play Console notice.
Do not stop at changing a version number. Test your release build and its dependencies against the required platform behavior. A build configuration that passes upload validation is not proof that the app works correctly on real devices.
- Allow for Google Play closed testing where applicable For personal developer accounts created after November 13, 2023, Google requires a closed test with at least 12 testers continuously opted in for at least 14 days before applying for production access. Meeting that threshold enables the application for access; it is not automatic publication. This is not a universal rule for every organization account. Follow the official account-specific testing requirements.
Recruit people who can use the actual workflow and report problems. Keep a simple record of feedback, fixes and what was tested. A last-minute tester count is not a substitute for a useful test, and internal distribution should not be confused with public production availability.
- Make privacy declarations match the released app Inventory authentication, analytics, crash reporting, payments and every SDK that may handle data. Google requires Data safety disclosures to account for third-party libraries as well as your own code. Compare declarations with the release configuration, not only an early prototype. Google’s Data safety guidance explains the required disclosures.
Apple has privacy-manifest requirements for listed SDKs, with signature conditions for relevant binary dependencies. Flutter and common plugins can be part of that dependency review. Check Apple’s SDK requirements rather than assuming a framework handles every declaration automatically.
- Test deletion, login and reviewer access Where account creation is supported, Apple requires an in-app account-deletion route. Google’s applicable policy requires an in-app deletion path and an external web resource for requesting deletion. Test the complete path, including how the backend handles associated data and any disclosed retention exceptions. See Apple’s privacy rules and Google’s deletion requirements.
Provide working review credentials or the appropriate review mode, clear instructions and a reachable backend. Explain hardware or location dependencies. Reviewers should not meet an empty account, an expired login or a feature that only works on the developer’s network.
- Respond to rejection with evidence Read the cited issue, reproduce it on the submitted version and distinguish a code problem from missing information. Fix the relevant cause, update inaccurate metadata and explain the change plainly. Do not resubmit an identical build repeatedly without addressing the issue. Payments, subscriptions and regional distribution require their own policy check; there is no universal payment shortcut.
AIUNSEEN Studio’s mobile MVP service can include an agreed submission-support cycle. Apple and Google retain approval authority. Include account status, target platforms and known review constraints in the project brief so development and launch responsibilities are scoped together.
Top comments (0)