Publishing an app is more than uploading a file. Google and Apple verify the developer’s identity, product stability, data practices and consistency between the app and its listing. Preparing these items during development prevents many avoidable rejections and delays.

Store rules change regularly. The information below was checked on 7 September 2026; always review the official pages before submitting.

1. Create accounts in the owner’s name

The client should ideally own the developer accounts. Google Play Console currently requires a one-time USD 25 fee. Apple Developer Program membership costs USD 99 per year, or the local price shown by Apple. An Apple organisation must provide its legal-entity information and generally a D‑U‑N‑S Number.

A developer can receive an appropriate role without owning the account. This makes maintenance and provider changes easier. Read the official Google Play Console and Apple Developer Program information.

2. Stabilise the technical identity

Choose the Android package name and iOS Bundle ID carefully. These identifiers associate every version with the product and become difficult or impossible to change after publication. Prepare the Android signing key, Apple certificates and secure storage for credentials.

Google Play uses Android App Bundles to generate packages suited to each device. The production bundle must be signed and tested. On iOS, a build is uploaded to App Store Connect using Xcode or another supported tool, then processed before it becomes available for TestFlight or submission.

3. Test before production

Test on real phones, multiple screen sizes, a slow connection and the system versions you target. Check account creation, network errors, purchases, notifications, links and account deletion when the feature is required.

For personal Google Play accounts created after 13 November 2023, Google currently requires a closed test with at least 12 testers continuously opted in for 14 days before production access can be requested. Start with internal testing, fix defects and then organise the closed test. See the official testing requirements.

4. Prepare privacy information

List all data collected by your code and SDKs: accounts, location, photos, device information, analytics, advertising or payments. The privacy policy must be publicly accessible and match the product’s actual behaviour.

Google requires developers to complete Data safety information, including when an app collects no data, and to declare third-party SDK practices. Apple requires App Privacy information and a privacy-policy URL for every app. An inaccurate declaration can delay review or lead to enforcement later.

5. Build a convincing store listing

  • A clear name and promise without artificial keyword stuffing.
  • A description that matches features actually available.
  • An original icon that remains readable at small sizes.
  • Screenshots from the real app in the required formats.
  • An accessible support email, website and privacy policy.
  • Honest content questionnaires and age ratings.

6. Upload the build and support review

On Google Play, complete the dashboard sections, upload the AAB to the appropriate testing track and resolve warnings before production. On Apple, create the App Store Connect record, upload the build, associate it with the version and answer compliance questions.

If any part of the app requires login, provide a demo account and precise review instructions. The review team should be able to reproduce the main features without guessing your process.

7. Plan beyond launch

Publication is not the end of the project. Monitor crashes, reviews, performance and policy changes. Keep the Android key safe, renew Apple membership, update SDKs and ship fixes. Keep the store listing and privacy declarations aligned with every new feature.

Read my guide to mobile app development costs and explore Android and iOS development. For technical preparation and submission, tell me about your app.