Short practical notes we use ourselves. Always check current store rules — they change.
Common causes: incomplete features or placeholders; no demo account for the reviewer; external payment links for digital goods; privacy label mismatch. Before submitting: add test login in Review Notes, scan every screen for stubs, reconcile App Privacy with SDKs in the build.
Build a table: each SDK → data it collects → shared with third parties? → encrypted in transit? The Data safety form must cover both your code and libraries. Re-check it on every dependency update.
A practical ladder: 1–5% for the first day, then 20%, 50%, 100% only if the crash-free rate is not below the previous version. Define the halt threshold and who can press “pause” in advance.
Keep the visible version (2.14.0) separate from a build number (311) that always increases. Repo tag = build number. Any crash report then maps to one commit.
Make 4–6 frames, each answering one user question. On-image text up to 7 words. Generate them from UI tests so they update with the interface automatically.
HTTPS and www redirect; correct canonical and hreflang; a 404 page; cache headers for static files; forms tested on the real server; a backup of the previous version.