Make sure your app targets the right version of the Android SDK as required by
Play store policy.
Create immersive virtual reality experiences for Daydream and Google Cardboard
Design your app to drive conversions
Sell subscriptions with Play In-app Billing
Sell subscriptions through Google Play Billing to provide users with access to
content and features on an ongoing basis.
Google Play’s subscription platform gives you the tools and actionable
intelligence to grow your subscription businesses. You can quickly and easily
get set up with Google Play Billing, and then Google Play handles the checkout
details so your app never has to process financial transactions. You’ll have
access to customizable subscription options and management features to help you
attract and retain more customers. And, because your app will use the same
checkout flow that is used for content purchases on Google Play, users will get
a familiar, reliable, and secure experience.
quarterly, half-yearly, or annually.
* Local pricing: Customize the price for each locale and bill users in
* Account holds: Block access to your content or service if a user’s form
of payment fails until they upd ate their payment information.
plan to another (for example, from a basic to a premium subscription) or
to re-sign up to keep access.
* Server-side API: See fine-grained details about each subscription, such
as expiration date, payment status, cancellation reason, and more.
* Subscription restore: Allow users to restore a subscription directly from
the Play Store.
**** Setup ****
* Use the Google_Play_Billing_Library to simplify development. The library
provides an interface for sending in-app billing requests, and managing
in-app billing transactions using Google Play.
* Configure all of your subscriptions SKUs at the app level using the
Google_Play_Console, instead of having to manage all of your SKUs
* Use license test accounts to test purchases without spending real money.
We provide a “good” test instrument and a
“bad” test instrument for each account so you can make
se cure and convenient test purchases during development or in preparation
for launch. For more information on testing, visit the Help_Center.
* Record purchase_tokens_and_order_IDs to make sure you’re tracking users
appropriately. Order IDs appear in financial reports, and tokens are
required for using Play Billing APIs and validating purchases.
**** Acquire ****
* Offer free_trials to let users try your app before committing to a
purchase. It’s one of the biggest conversion drivers, and our_research
* Verify_purchases to ensure they complete successfully. You should also
check at renewal time to ensure successful renewal and catch any issues.
**** Retain ****
* Monitor subscriber state changes using real-time_developer_notifications
(RTDN). To enable RTDN, you’ll need to integrate your backend with Cloud
Pub/Sub using your own Google_Cloud_Platform_(GCP) proje ct, and indicate
in Google_Play_Console the Pub/Sub topic to which Play should publish
notifications. Whenever an RTDN is received, call the server-side API to
get the latest subscription state. Then, sync the state with your
database. This should be done even for notification types you haven’t
* Notify your users when their payment information needs updating, which
helps to reduce involuntary churn as a result of payment failures. When
paymentState is 0, the user needs to update their payment information.
can be configured in the Play_Console.
* Help prevent involuntary churn by enabling account_holds. With account
holds, you put subscribers with payment failures in a suspended state and
block access to content until they update their form of payment, which
hopefully motivates them to do so. We see the best results when
developers enable both grace periods and account holds for their
* Allow users to easily restore a subscription from the subscription
management page in the Play Store by enabling subscription_restore in the
* Analyze the cancelReason and cancellation time so you can correlate
cancellations with user behavior to try and prevent it from happening in
the first place.
* Defer billing through the Google_Play_Developer_API to give existing
users free service for a temporary period of time. Deferring billing is
as a gesture of goodwill while also helping you to address outages or
Use Google Play In-app Billing to sell users access to content and features
through a subscription for an ongoing revenue stream.
When you use Google Play In-app Billing to sell a subscription, Google Play
handles the checkout details so your app never has to process financial
transactions. Your app will use the same checkout flow that is used for content
purchases on Google Play, so users will get a familiar, reliable, and secure
experience. Google Play also helps you attract and retain more customers with
customizable subscription options and management features.
quarterly, half-yearly, seasonally, or annually.
* Local pricing: Customize the price for each market and bill users in
* Account hold: Block access to your content or service if a user’s form of
payment fails until they update it.
plan to another (for example from a basic to a premium subscription).
* Test In-App Billing implementation with a licensed test account. Testing
is an important part of implementing In-App Billing, but doing so with
real accounts can be pricey. Use our In-App_Billing_Sandbox during
development or in preparation for launch to make large-scale, secure, and
convenient test purchases with authorized user accounts so you’re not
spending real money during testing. Visit our Help_Center for more
information on testing In-app Billing.
* Check subscriptions regularly from your server. A user’s subscription
state changes, so make sure to check_your_server at suitable intervals.
For example, you should check after a purchase to ensure it completes
successfully. Check again three to five days before a subscription is due
to renew to anticipate cancellations so that you can try to re-engage.
You should also check at renewal time to ensure successful renewal and
catch any issues.
* Store purchase tokens and order IDs. To make sure you’re tracking users< br/>appropriately, record_both_purchase_tokens_and_order_IDs. OrderID appears
in financial reports, and tokens are required for using Play Billing APIs
and validating purchases.
* Track and notify your users when their payment information needs
updating. Tracking “paymentState” and notifying your users when their
payment state is 0: “Payment pending” helps to reduce involuntary churn
as a result of payment failures.
can be done simply by flipping a switch in the Play_Console without any
* Monitor cancellations. The cancelReason and cancellation time provide the
reason for the cancellation and time it occurred, so you can correlate
cancellations with user behavior to try and prevent them from happening
in the first place.
* Use the “deferred API” to give existing users free service. Address
outages or service issues using the “deferred API” to defer payments as a
gesture of goodwill to your users.
* Prev ious_pageSell_in-app_digital_purchases_with_Play_billing