The full submission process, from Play Console setup to handling a policy rejection.
Building the app is only part of getting it live. The Play Store submission process has its own requirements, and missing any one of them is a common reason apps get delayed or rejected on a first attempt.
This requires a one-time registration fee and identity verification. Complete this well before you plan to submit — verification can take time, and an unverified account can't publish.
This includes an app title, short and full descriptions, a feature graphic, an app icon, and phone screenshots. Descriptions should accurately describe what the app does — overselling features that don't exist, or including keywords unrelated to the app's function, is itself a policy violation, not just bad practice.
Google requires every app to go through a content rating survey covering violence, language, and other content categories. Answer accurately — a puzzle game and a music player will typically both qualify for the lowest rating tiers, but the questionnaire still has to be completed for every submission.
This section requires disclosing what data your app collects and why — including data collected indirectly through the AdMob SDK for ad personalization. This must match your actual implementation and your privacy policy; mismatches here are a common cause of rejection.
Every app, even a simple offline game, needs a published privacy policy URL if it uses any SDK that can collect data (AdMob included). This needs to be a real, accessible page — not a placeholder.
Use an internal or closed testing track first to catch install-time issues before going to production. This also gives you a chance to test the exact production build — including confirming AdMob ad units are set to live IDs, not test IDs (see our AdMob integration guide).
Review timelines vary, from a few hours to several days, depending on the app and account history. New developer accounts and apps requesting sensitive permissions typically see longer review times.
Read the specific policy cited, not just the headline reason. Google's rejection messages usually link to the exact policy section violated. Fix the underlying issue — not just the symptom — before resubmitting, and where relevant, request a review rather than resubmitting blind, since some policy areas (like low-value content flags on companion websites) need a specific review request after changes are made.
It varies, but commonly ranges from a few hours to a few days. Apps from new developer accounts or those requesting sensitive permissions can take longer.
If the app uses any third-party SDK that can collect data — including AdMob — yes, a privacy policy is required even if the app itself stores nothing.
Yes, but only after actually fixing the cited policy issue. Resubmitting the same build without changes typically results in the same rejection.