App Store Submission: What to Prepare Before Sending Your App for Review

App Store Submission: What to Prepare Before Sending Your App for Review

Before you submit an app for review, have five things ready: developer accounts in your company's name; a finished build that meets the stores' current technical requirements; a complete store listing with accurate screenshots; privacy answers, a privacy policy and an age rating; and everything a reviewer needs to reach every feature – a demo account, notes and a live back end. If you distribute in the EU, add one more: your trader status. Most rejections and delays come from something missing on this list, not from the code. Approval is never guaranteed, but every item below is within your control. A good starting point is Apple's App Review Guidelines, which open with a short "before you submit" checklist; Google Play has equivalent pages in the Play Console Help.

1. Accounts: who owns the app

Whoever holds the developer account controls the app: updates, listing, reviews and payments. Register both store accounts in your company's name, not a developer's personal account, and give more than one person access. The principle is the same as for websites – see who should own the domain, hosting, code and accounts.

On Google Play, the account type affects your timeline. Personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers, opted in for at least 14 consecutive days, before they can apply for production access. Check your account type before setting a launch date.

2. The build: current technical requirements

Both stores raise their minimum requirements over time, and they apply to every upload:

  • Apple: since 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later and the iOS 26 SDK (or its equivalent for other Apple platforms). Apple's submission page already announces the next step: from April 2027, iOS and iPadOS apps must be built with the iOS & iPadOS 27 SDK or later.
  • Google Play: new apps and app updates must target Android 16 (API level 36) or higher (deadline 31 August 2026; extensions to 1 November 2026 were available). New apps have had to be published as Android App Bundles since August 2021.

Then the basics: test for crashes and bugs on real devices. Apple's App Review page says that over 40% of unresolved issues relate to guideline 2.1, App Completeness – crashes, broken links, placeholder content and missing information.

3. The store listing

Prepare texts and images for each store and each language you support:

ItemApp StoreGoogle Play
NameUp to 30 charactersUp to 30 characters
Short text under the nameSubtitle, up to 30 charactersShort description, up to 80 characters
DescriptionUp to 4,000 charactersFull description, up to 4,000 characters
Search termsKeywords field, up to 100 bytesNo separate field
ScreenshotsRequired, up to 10At least 2, up to 8 per device type
Other graphicsOptional app preview videos512 × 512 px icon, 1024 × 500 px feature graphic, optional YouTube video

Limits from App Store Connect's reference, Apple's product page guide and Google's listing and graphics guidance.

Two rules often cause problems. Apple's guidelines say screenshots should show the app in use, "not merely the title art, login page, or splash screen", and that names and keywords must not be packed with trademarked terms, popular app names or pricing information. Google's listing requirements forbid ranking and promotional claims such as "Best", "#1", "Top", "New" or "Discount", and calls to action such as "download now". Write the listing as an accurate description, not an advert.

4. Privacy: policy, labels and permissions

  • Privacy policy. Both stores require a link in the store listing and inside the app. Apple's review page adds that the policy must identify what data is collected, how it is shared with third parties, and how it is retained and deleted.
  • Apple privacy details and Google Play Data safety. Both are required, and both must include data collected by third-party code in your app – analytics tools, advertising networks, SDKs. Google requires the Data safety form even from apps that collect no user data. Ask your developer for a list of every SDK and what it collects.
  • Permission explanations. On iPhone, an app that accesses sensitive data must include a purpose string explaining why; unclear ones are among the common reasons for rejection Apple lists. On Google Play, apps that use certain high-risk or sensitive permissions may have to complete a Permissions Declaration Form and receive approval.
  • Account deletion. If users can create an account in the app, Apple requires that they can also delete it from within the app.

5. Age rating, audience and ads

Each store has a questionnaire. Apple's age rating questionnaire is completed in App Store Connect; Apple has moved to an updated rating system and asked developers to answer the new questions by 31 January 2026 to avoid interruptions when submitting updates. Google asks you to complete the content rating questionnaire – otherwise the app may be listed as "Unrated" – and to declare the target age group and whether the app contains ads. If children are in the audience, Google's Families policy applies too.

6. EU trader status

Under the EU Digital Services Act, both stores ask whether you are a trader. Apple requires trader status for apps distributed in the EU: since 17 February 2025, apps without it are removed from the EU App Store until trader status is provided and verified. Google Play asks every developer to declare it – new accounts immediately on creation, existing accounts by 1 February 2027 – regardless of where the apps are distributed. Google's definition of a trader – anyone acting for purposes relating to their trade, business, craft or profession – covers a company publishing its own app. From 1 March 2027, Google will show traders' contact details in the "App support" section of the listing. Decide in advance which address, phone number and email you want to be public.

7. Give the reviewer full access

Apple asks for full access: an active demo account or a full demo mode if the app has accounts, anything else needed – hardware, a sample QR code – and back-end services that are live during review. Google asks for all the details needed to access the app; you can add up to five sets of instructions and use a separate field for things like one-time passwords or multi-factor authentication. In practice:

  • create a demo account with realistic data that won't expire during review;
  • add notes on how to reach features that aren't obvious – a paid area, a role-specific screen;
  • keep the server compatible with the submitted version throughout the review.

8. Plan the timing and the release

Apple says it typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours; incomplete ones may take longer. Google says reviews for certain accounts and apps may take up to seven days, or longer in exceptional cases. Leave a margin before any date you have promised – a launch event, a campaign, the start of a season.

  • Control the moment of publishing. Google Play's managed publishing lets you decide when approved changes go live; both stores also support gradual releases – see the rollout section of planning your first app release.
  • If the app is rejected, Apple names the guidelines that weren't met and lets you correspond with App Review; if the app was misunderstood, you can file one appeal per rejected submission. For a critical bug in a live app, you can request an expedited review.

Checklist before you press "Submit"

  1. Developer accounts in the company's name, with access for more than one person.
  2. A build tested on real devices, meeting current SDK and target API requirements, with no placeholder content or broken links.
  3. Name, short text, description, keywords and screenshots in every language.
  4. Privacy policy linked in the app; privacy details and Data safety answers covering all SDKs; permission explanations; in-app account deletion if there are accounts.
  5. Age rating and content questionnaires completed; ads and target audience declared.
  6. Trader status declared and the public contact details agreed.
  7. Demo account, review notes and a live back end.
  8. A release date with a margin, and someone watching crash reports and reviews in the first days.

Store submission is the step where missing pieces become visible. We can prepare the store side together with the app – accounts, listing, privacy forms, review notes and a release plan – as part of our mobile app development work. If your app is almost ready, or was rejected and you're not sure why, send us the details.

Sources

← All articles

Have an idea for a website, app or system?

Tell us briefly what you need – we will get back to you for a short call and a clear quote.