The first store submission should happen several weeks before launch, not on the day the build is finished. Not because review is slow, but because the account and metadata work around it is consistently underestimated.
Account setup takes longer than the review
Before anything can be submitted, a developer account must exist. For a company account this generally requires business registration documents and a verification step that takes days to weeks depending on the jurisdiction and how quickly documents match.
The delays are mundane and predictable: a company name that does not match the registration exactly, an address format the verification does not accept, a legal entity type that needs additional evidence. None is difficult; all take calendar time.
This should start at the beginning of the project, not at the end. It is the single most common cause of a launch date slipping for reasons unrelated to development.
The rejections that recur
Most first-submission rejections fall into a small number of categories:
- Incomplete information for review. If the app requires login, working test credentials must be supplied. Reviewers who cannot get in reject the submission. Where a workflow needs specific data or a particular device state, that has to be explained.
- Crashes or obvious bugs. Reviewers exercise the app and reject on crashes.
- Privacy disclosures missing or inconsistent. A privacy policy is required, must be reachable at a live URL, and must match what the app actually collects. Declaring no data collection while requesting contact permissions is an inconsistency reviewers check.
- Permissions requested without evident purpose. Asking for location, camera or contacts requires a justification the reviewer finds plausible, and the in-app explanation text has to be specific rather than generic.
- Placeholder content. Lorem ipsum, empty screens, non-functional buttons, "coming soon" sections. A store listing is for a finished product.
- Payment handling that does not follow platform rules. The rules on what must use the platform's own payment mechanism are specific and strictly enforced. Getting this wrong can require reworking a core flow.
- Metadata mismatches. Screenshots showing features that are not present, descriptions promising functionality that does not exist.
Every one of these is preventable before submission, and a pre-submission review against this list costs an hour.
Metadata is a work item
The listing needs, per platform and per language:
- App name and subtitle, within character limits.
- Description, usually short and long versions.
- Keywords, where the platform uses them.
- Screenshots at required sizes for several device classes.
- An icon at multiple resolutions.
- Category, age rating and content declarations.
- Support and privacy policy URLs, both live.
Screenshots at specific device sizes are the item that most often causes a scramble, because they need a working build on those device sizes. Producing them properly takes a day, and doing it hurriedly produces a listing that undersells the product.
Review timing
Review typically completes within a day or two on the major platforms, though it varies and slows around holidays. Plan on several days, and plan for at least one rejection on a first submission — that is normal rather than a failure, and resubmission after a fix is usually faster.
Do not schedule a launch event for the day after submission. Submit, get approved, and hold the release until you are ready — both major platforms support approving a build and releasing it later, which removes the timing risk entirely.
After the first release
Updates go through review too. For anything time-sensitive — a fix for a serious bug — build in a day or two for review rather than assuming immediate publication.
Note also that users do not all update. A meaningful proportion stay on older versions for a long time, which means server-side changes have to remain compatible with versions still in the field, and it is worth deciding early how long you will support them.
Related Manboo Services
- Flutter App Development for iOS and Android MVPs.
- Business Software Development for CRM, booking, inventory and workflow systems.
- Admin Panel Development for operations dashboards and backend management.
- AI API Integration when your product is ready for smart search, chat or automation.
- Request a scope review and project estimate when you are ready to plan the first version.