Google Play Publishing Guide: From Build to Launch

Your app is built. Tested. Working. Now comes the question every developer faces: how do you actually publish it on Google Play so people can download it?

Having published over 20 apps on the Google Play Store in recent years, we have seen some sail through in a day and others get rejected three times before approval. This article covers everything you need to know -- no theory, just practical experience.

Step 1: Google Play Developer Account

Everything starts with a developer account. Head to play.google.com/console and register.

There are two options:

• Personal account -- $25 one-time fee. Suitable for freelancers and small companies.
• Organization account -- also $25, but requires additional verification. Google checks whether your company is legitimate -- DUNS number, website, contact details.

Our recommendation: if you are building an app for a business, register an organization account. It looks more professional and Google tends to trust these accounts more during review.

This means: if you plan to publish on a specific date, start the developer account registration at least 3 weeks in advance. We have seen cases where a client wanted to launch on Monday, but account verification took 10 days.

Step 2: Prepare Everything Before Upload

Before uploading your app to Google Play Console, you need to have a whole set of assets ready. Here is the complete list:

App Bundle (Not APK!)

Since 2021, Google Play only accepts AAB (Android App Bundle) format, not APK. This is important -- if your developer gives you an APK file, ask them to convert it to AAB. The difference: AAB lets Google optimize the app size for each phone individually, resulting in smaller downloads.

App Icon

512 x 512 pixels. PNG format. Make it look professional -- this is the first thing users see. We have seen cases where simply changing the icon increased downloads by 25%. People decide in a split second whether to tap or scroll past.

Screenshots

Minimum 2, we recommend 5-8. Specifications:

• Phone: 1080 x 1920 px (or larger)
• Tablet: 1200 x 1920 px (if your app supports tablets)
• Best practice: not just raw screenshots, but designed images with text overlays and branding. "Feature graphic" style.

Tip: the first 2 screenshots are the most important -- everyone sees them. The rest only appear for users who scroll. Show your core value proposition immediately.

Feature Graphic

1024 x 500 pixels. This is the large banner image shown at the top when Google Play features your app. It is mandatory.

Store Description

• Short description -- up to 80 characters. This is your headline -- it needs to hook users in one second.
• Full description -- up to 4,000 characters. Explain what the app does, what problems it solves, and what the main features are.

Write like a human, not a marketer. "Manage your finances easily" is better than "Revolutionary AI-powered financial management platform with cutting-edge insights."

Privacy Policy

This is mandatory. If your app collects any data (and almost all do -- at minimum crash reports), you must have a privacy policy page. The URL must be live and accessible.

If your app targets EU users, the privacy policy must comply with GDPR. You can use generators, but we recommend having a lawyer review it -- especially if you collect personal data.

Asset Required	Specification	Mandatory?
App Bundle (AAB)	Max 150 MB	Yes
App Icon	512 x 512 px, PNG	Yes
Screenshots	Min. 2, recommended 5-8	Yes
Feature Graphic	1024 x 500 px	Yes
Short description	Up to 80 characters	Yes
Full description	Up to 4,000 characters	Yes
Privacy policy	URL with live page	Yes
Promo video	YouTube link	No, but recommended

Step 3: Google Play Console Settings

Once you have everything prepared, log into Google Play Console and start filling in the details. Here are the critical sections:

Content Rating

Google asks you to complete a questionnaire about your app's content -- violence, gambling, adult content, and so on. Based on your answers, the app receives a rating: PEGI 3, PEGI 7, PEGI 12, etc.

Do not try to game this. If Google finds a discrepancy during review, the app will be rejected. Answer honestly and you will be fine.

Data Safety Declaration

Since 2022, this is mandatory. You must specify: what data you collect, how you use it, and whether you share it with third parties. This is Google's equivalent of Apple's "App Privacy" labels.

Be precise. If you use Firebase Analytics, you are collecting usage data. If you have registration, you are collecting email addresses. Do not forget anything -- Google checks, and discrepancies cause problems.

Countries and Languages

Choose which countries your app will be available in. You can start with one market and expand later.

Pricing: if your app is paid or has in-app purchases, configure it here. Remember that Google takes 15% commission on the first $1M per year (it used to be 30%).

Step 4: Store Listing Optimization (ASO)

ASO -- App Store Optimization. Think of it as SEO for the Google Play Store. Most developers completely ignore it. That is a mistake.

From experience: good ASO can increase organic downloads by 40-60% in the first month. It is free -- it just takes effort.

Step 5: The Review Process

Once everything is filled in and confirmed, your app goes to Google for review. Here is what to expect:

• First app on a new account: 3-14 days
• First app on an established account: 1-7 days
• Updates: 1-3 days (sometimes just a few hours)

During review, Google checks for malware, stability issues, policy violations, content rating accuracy, and the existence of a privacy policy.

Google uses both automated and manual review. Automated is faster but sometimes triggers false rejections. Manual is slower but more accurate.

Step 6: When Your App Gets Rejected

It happens. Do not panic -- it is normal. In our experience, only about 3 out of 20 apps pass on the first try without any feedback.

When you get a rejection, Google sends an email with the reason. Sometimes it is clear, sometimes it is vague. If you do not understand, you can write to Google Support and request clarification. Expect a response in 2-5 business days.

Fix the issue, resubmit, and wait for review again. Re-review typically takes about the same time as the initial review.

Step 7: After Publishing

Your app is live. Congratulations. But the work is not over -- in fact, it has just begun.

Monitor Crashes

Google Play Console has an "Android Vitals" section where you can see crash rate, ANR (Application Not Responding) rate, and other metrics. If your crash rate exceeds 1.09%, Google may reduce your app's visibility in search results.

Use Firebase Crashlytics -- it is a free tool that shows exactly where and why your app crashes. Essential for any published app.

Regular Updates

Regular updates signal to Google that the app is actively maintained. We recommend at least one update per month -- even if it is just bug fixes. Google favors active apps.

Reviews and Ratings

Respond to reviews -- especially negative ones. We see countless apps with 1-star reviews containing questions that the developer never answered. That is bad for both users and the Google algorithm.

Tip: after each update, prompt existing users to leave a review. Android has a built-in "In-App Review" API -- use it. Just do not annoy users too often -- once every 2-3 months is sufficient.

User Analytics

Google Play Console shows statistics: downloads, uninstalls, countries, device types. Use this data. If 70% of your users are from one city, consider adding localized features for that market.

The Full Cost Breakdown

Publishing itself costs $25 and your time. But if you want to do it professionally:

Service	Cost	Required?
Developer account	~23 EUR (one-time)	Yes
Professional icon	100 - 300 EUR	Highly recommended
Screenshot design	200 - 500 EUR	Highly recommended
ASO optimization	300 - 800 EUR	Recommended
Privacy policy (lawyer)	200 - 500 EUR	Yes (if collecting data)
Promo video	500 - 2,000 EUR	Optional

In short: if you do everything yourself, it costs $25. If you want professional results, add 500-2,000 EUR. That is modest compared to the cost of building the app itself.

Pre-Launch Checklist

Before hitting "Submit," run through this list:

1. AAB file is prepared and tested on multiple devices
2. Icon is 512x512 and looks professional
3. 5-8 screenshots with design and text overlays
4. Feature graphic at 1024x500
5. Short and full descriptions with relevant keywords
6. Privacy policy URL is live and accessible
7. Content rating questionnaire completed honestly
8. Data Safety declaration is accurate
9. 20 testers have tested the app (for new accounts)
10. Crash rate is low (Firebase Crashlytics is clean)

If all of that is done -- go ahead. If not, one more hour of preparation is better than a week of waiting after a rejection.