Teams budget for building the app and treat publishing as an afternoon. It is usually the part that slips.
What actually takes the time
Policy declarations
Google asks what data you collect, why, whether it is shared, and whether it is encrypted. Answering casually is the most common cause of rejection, and the answers must match what your app genuinely does — the review process checks.
Work this out before you submit, not while a rejection is open.
The listing
Title, short description, full description, screenshots at several sizes, a feature graphic, an icon, a privacy policy at a live URL. Each is small; together they are a day, and they are on the critical path because you cannot submit without them.
Review
First submissions take longer than updates, and new developer accounts get more scrutiny. Plan for days, not hours, and never schedule a launch campaign against an unreviewed build.
Rejections you can avoid
- Privacy policy missing or unreachable. It must be live, public, and actually about your app.
- Permissions you cannot justify. Every permission needs a visible reason in the app.
- Data declarations that do not match behaviour. If an SDK sends analytics, that is data collection whether or not you wrote the code.
- Screenshots that are not the app. Marketing mock-ups get rejected.
After launch
Publishing is the start of an obligation, not the end of a project. Target API levels rise annually and apps that do not keep up stop being distributed to new devices. Budget for maintenance or plan to be delisted eventually.
