PPlatformAppStores

Google Play Store

Consumer

Google LLC · Browser & OS extension stores

Best for: Native Android apps seeking broad global distribution.

Overview

Google Play is the primary app store for Android, reaching billions of devices worldwide. Developers pay a one-time $25 registration fee, use the Google Play Console to upload signed Android App Bundles, and pass Google's policy review, which blends automated malware/privacy scanning (Play Protect) with human evaluation. Google has tightened identity verification and pre-launch testing requirements in recent years, raising the practical bar despite the low entry cost.

Monetization flows through Google Play Billing, with Google as Merchant of Record for taxes and payouts. Commission has historically been 30% standard and 15% reduced, but a 2026 settlement with Epic Games is driving materially lower headline rates in the US, UK, and EEA — verify the exact current percentages when listing, as they are actively changing and vary by region. As with Apple, the store install requires no developer credential, but apps typically authenticate users via Google Sign-In / OAuth2, and developers automate release management through the OAuth2-secured Play Developer API.

How to build & ship

  1. 1Create a Google Play Console account and pay the one-time $25 registration fee
  2. 2Build with the Android SDK in Kotlin or Java, using Jetpack/AndroidX libraries
  3. 3Produce a signed Android App Bundle (AAB) via Gradle (bundleRelease)
  4. 4Create the listing, content rating, and data-safety details in Play Console
  5. 5Upload to a release track and submit for review

Key APIs & SDKs

Android SDK
Kotlin / Java
Jetpack / AndroidX
Android App Bundle (AAB)
Gradle
Play Console / Play Developer API

Integration types

Embedded app

Authentication & security

  • Primary auth: None
  • Also supports: OAuth 2.0, API key
  • Security review: Required
  • Google combines automated scanning (Play Protect) with policy/human review of apps and updates for malware, privacy, and content compliance.
  • Automated and human policy/security review that can take from hours to several days (longer for new developer accounts).
  • No marketplace-wide runtime rate limit on installed apps; governed by the Android SDK and any backend the app calls.
Auth docs Store policies

Monetization

Free
Paid app
Usage-based
Revenue share
Onboarding
$25 one-time developer registration
Commission
Historically 30% standard / 15% reduced; lower tiers rolling out in 2026 (verify current rates)
Merchant of Record
Google Play Billing is MoR for paid apps and in-app purchases

Pros & cons for builders

Pros

  • Very large global Android audience
  • Low one-time fee
  • Flexible release tracks and staged rollouts
  • Strong CI/build tooling

Cons

  • Review times can be unpredictable, especially for new accounts
  • Frequent policy changes require ongoing maintenance
  • Commission on paid content

Frequently asked questions

How do I get my app approved on Google Play Store?

Automated and human policy/security review that can take from hours to several days (longer for new developer accounts).

What authentication does Google Play Store use?

Google Play Store apps primarily authenticate with None, also supporting OAuth 2.0, API key.

How is Google Play Store monetized?

Google Play Store supports Free, Paid app, Usage-based, Revenue share. Typical commission: Historically 30% standard / 15% reduced; lower tiers rolling out in 2026 (verify current rates). Onboarding fee: $25 one-time developer registration.

Is a security review required to list on Google Play Store?

Yes, Google Play Store requires a formal security or listing review before apps go live. Google combines automated scanning (Play Protect) with policy/human review of apps and updates for malware, privacy, and content compliance.