App Store Submission Gate (Delivery)

App Store Submission Gate (Delivery)

1. 01

   Confirm the client owns the developer accounts before any build is uploaded

   Apple Developer and Google Play Console accounts should sit under the client's legal entity or a written agency-of-record agreement. Publishing under an agency account creates a transfer problem the day the retainer ends.

2. 02

   Lock the app name, bundle ID, and store listing copy at least 10 business days before target submission

   Name collisions and trademark flags are the two most common causes of a rejected first submission. Reserve the name in App Store Connect early, since reservations expire after roughly 180 days of inactivity.

3. 03

   Map every native permission the build requests to a plain-language justification

   Camera, location, contacts, and push each need a purpose string that matches actual app behavior. Reviewers reject builds where the stated reason does not match what the app does on screen.

4. 04

   Run a full pass on a physical device, not a preview link

   Test offline behavior, deep links, and push delivery on at least one current iOS and one current Android handset. Preview environments in builders such as Adalo or Draftbit can mask rendering differences that only appear in a signed build.

5. 05

   Verify account deletion and data-retention flows are reachable inside the app

   Both stores now require an in-app path to delete an account and its data. A web-only deletion form is a common rejection cause for client apps built on hosted backends.

6. 06

   Stage the submission with a 5 to 7 day buffer before any client-facing launch date

   First-time reviews routinely take longer than repeat submissions, and a rejection restarts the clock. Never promise a client a live date that assumes same-week approval.

7. 07

   Capture the submission receipt, review notes, and version number in the client's delivery record

   Store the build number, submission timestamp, and reviewer feedback in one place. When a client asks why version 1.0.3 differs from 1.0.2, the answer should take seconds, not a support ticket.