Your app is built. There's still work to publish it.

This handbook walks through the accounts, forms, builds, and review decisions between a working app and a public release.

Why Draftbit publishes these guides

We make tools for building apps. Getting those apps into people's hands means working through the stores, too. These guides explain that part of the job, whichever tool you used to build your app.

When a Draftbit feature, guide, or service can help with a step, we link to it there. Those links include referral parameters that identify this site and the article you came from. You don't need an account to read the handbook.

See what you can build with Draftbit

How we check the instructions

We use Apple's and Google's official documentation for store requirements. Each guide says who it applies to, links to its sources, and records when we checked them. We check the written instructions; that doesn't mean we've tested each guide by submitting an app.

We explain what the stores require and where we're offering practical advice. We also separate rules you need to follow now from changes with a future deadline. If the official sources disagree or leave something unclear, we say so.

Our schedule calls for a source check each month and again before a known deadline. Each guide shows two dates: when we last changed the page, including its sources and requirement boxes, and when we last checked the sources. Updating the site doesn't mean we've rechecked a policy. Follow any specific instructions in your console or review message, too; a general guide can't cover every decision about your app.

What the handbook covers

These guides cover public iPhone and iPad releases on Apple's App Store and Android phone and tablet releases on Google Play. Other devices, private enterprise distribution, and alternative marketplaces can have different processes.

The policy library explains the numbered Apple rules and named Google policies that apply to those apps. Apple clauses stay with their parent rule, with links you can share directly. We leave out intentionally omitted rules, requirements only for other devices, and retired programs. Repeated Google policy sections point to one explanation.

If something has changed

Open the official source at the end of the guide to compare the requirement. If you're working with Draftbit, include the guide URL and exact console wording when you contact Draftbit support. Leave out credentials and customer information.

Apple and Google operate their own stores and make their own review decisions. Draftbit publishes this handbook and isn't affiliated with either store operator.