Google Play Console Guide: Creating a Developer Account and Publishing an App from Pakistan

The first step in bringing an Android app to the Google Play Store is Google Play Console. This is where developers upload their apps, run tests, build their store page and send out updates. In this article you will learn how to create an account from Pakistan, the difference between a Personal and an Organization account, what the 12-tester, 14-day requirement for new accounts is, and the common mistakes that get apps rejected.

Google keeps changing its policies, so check the latest information in the Play Console Help Center before each step.

Personal account or Organization account?

When you create an account, Google asks whether you are creating it for yourself or for an organisation.

• Personal account: If you build apps on your own, or you are a student or a freelancer, this is the one for you. Verification requires your legal name, address and an identity document.
• Organization account: If you have a registered company or business, choose this option. It requires a D-U-N-S number, which is issued free of charge by an organisation called Dun & Bradstreet. Getting this number can take a few days or weeks, so start on it early. Your company's name and address must match the D-U-N-S record exactly.

One important difference is that new Personal accounts face an extra testing requirement, described below, while Organization accounts usually do not. But giving false information to avoid this requirement can get your account closed.

Steps to create an account

1. Choose a Gmail account you will use for a long time, and turn on 2-Step Verification for it.
2. Go to play.google.com/console and sign in.
3. Choose the account type (Personal or Organization).
4. Enter your developer name. This name will appear under your apps on the store.
5. Pay the one-time US$25 registration fee. You do not have to pay it every year. In Pakistan you will usually need a debit or credit card that is enabled for international online payments; check this facility with your bank beforehand.
6. Complete identity verification. Your name and address must match your official document (such as your CNIC or passport). Sometimes a utility bill or bank statement may also be requested as proof of address.
7. Verify your phone number and email.

Verification can take a few days. If a document is rejected, see which information doesn't match (for example, the spelling of your name) and resubmit it with a clear photo.

New Personal accounts: the 12 testers and 14 days requirement

Under Google's current rules, Personal developer accounts created after 13 November 2023 must run a closed test before publishing an app to everyone (Production). At least 12 testers must have opted in, and they must stay in the test for at least 14 continuous days. Once this requirement is met, you choose Apply for production access from the Dashboard and fill out a short questionnaire about how the test went, what feedback testers gave and what improvements you made.

Practical tips:

• Put your testers' Gmail addresses into an email list and select that list in the Testers section of the Closed testing track.
• Send each tester the opt-in link. Just being on the list is not enough; the tester must open the link, tap "Become a tester" and install the app.
• Testers should not uninstall the app for 14 days, and should use it and give feedback. If someone drops out midway, your count can fall, so add a few more than 12 people.
• Have real people test your app. Fake or purchased testers are against policy, and your request for production access may also be rejected.

These numbers and days have changed before, so be sure to read the Help Center page "App testing requirements for new personal developer accounts".

The difference between Internal, Closed and Open testing

There are three tracks under Testing:

• Internal testing: The fastest option for a small team; releases become available quickly, but it does not count towards the 14-day requirement.
• Closed testing: People from an email list or Google Group you choose. The requirement for new Personal accounts is met through this track.
• Open testing: Anyone can become a tester from the store.

App signing and the AAB file

New apps are uploaded to the Play Store in Android App Bundle (AAB) format. You sign your app with an upload key, and through Play App Signing, Google keeps the actual app signing key safe.

• Keep your keystore file and passwords in two safe places, never on GitHub or anywhere public.
• If you lose your upload key, you can request an upload key reset from Play Console, but it takes time.

Google also raises the target API level requirement every year; check "Target API level requirements" in the Help Center before uploading.

Store listing: how to build your store page

Go to Grow → Store presence → Main store listing and fill in the following:

• The app name, Short description and Full description, honestly stating what the app does
• A 512 × 512 app icon
• A 1024 × 500 feature graphic
• Real phone screenshots that show actual parts of the app

Claims like "Best app", "No.1" or "100% free money", or using a famous brand's logo without permission, are common reasons for rejection.

The Data safety form and Privacy policy

In the App content section you have to fill out several forms, the most important of which is Data safety. Here you must honestly declare what data your app collects or shares. Remember that the libraries in your app also collect data; for example, if you have added AdMob, you must declare device identifiers and ads-related data. To learn more about this, read our article AdMob Basics.

You also need a Privacy policy URL, meaning a public web page that opens without logging in and states your app's name, the data collected, how it is used and how to contact you.

Also fill out the Ads, Content rating, Target audience and (for apps with a login) App access forms.

Common reasons for rejection

1. The privacy policy link doesn't work, or the policy doesn't mention the app.
2. The Data safety form doesn't match how the app actually behaves.
3. Unnecessary permissions, such as SMS or Call log, that the app doesn't need.
4. The app crashes, or the review team can't open it because of a login.
5. An app that only displays a website without any added value, or copyrighted content.
6. Testers in the closed test didn't really use the app, or the answers to the production questionnaire were vague.

If you get a rejection, go to Policy status, read Google's email carefully, fix the problem and then submit a new release. If the decision seems wrong, you can also appeal.

If you haven't built your app yet, start with our guide Build an App with AI Without Coding. And to keep your account secure, be sure to read Safety and Privacy in the Age of AI as well.

Summary

• Choose the account type that matches your real situation; an Organization account needs a D-U-N-S number. The US$25 fee and identity verification are mandatory.
• Personal accounts created after 13 November 2023 must run a 14-day closed test with 12 real testers.
• Keep your keystore safe, fill out the Data safety form honestly and provide a working Privacy policy link.
• Always check the latest rules in the Play Console Help Center before each step.