Published on June 12, 2017 by Android Developers

We are pleased to provide this Play Billing Library developer preview to help simplify the development process, allowing you to focus your efforts on implementing logic specifics to your app, such as displaying in-app products and purchasing items. This library includes several classes and features for you to use when integrating your Android apps with the In-app Billing service.
As of now, the Play Billing Library’s minimum supported API level is Android 2.2 (API level 8), and the minimum supported In-app Billing API is version 3.

For more details about this launch, checkout our blog post “Money made easily with the new Play Billing Library” – goo.gl/oQF75z

Documentation:
In-App Billing Page – goo.gl/lPW8E0
Play Billing Library page – goo.gl/8plVWz
Play Billing Library reference – goo.gl/txfgG5
Play Billing Library Training Class – goo.gl/W3Kyay

Sample app: Trivial Drive V2 – github.com/googlesamples/android-play-billing/tree/master/TrivialDrive_V2

Leave a Reply

145 Comments on "Introducing the Play Billing Library – Developer Preview #1"

Notify of
avatar

The Head Shots
Guest
The Head Shots
3 months 7 days ago

f*cked up accent man I am super annoyed

Jomin V George
Guest
Jomin V George
3 months 20 days ago

There is no purchase state method in Purchase Object as described here:

, check this : developer.android.com/reference/com/android/billingclient/api/Purchase.html How am supposed to find subscription state?

Sergey Solovyev
Guest
Sergey Solovyev
7 months 1 day ago

I wonder why devs working at Google didn't even try to look for existing in-app billing libraries, there is quite few of them. Not invented here syndrome?Checkout [1], for example, has been around for more than 3 years. It has a high test coverage (~70-80% depending on metric), good API (Volley-like) and it is used by a lot of developers (>700 stars on github).Here [2] you can read about how to integrate the library and how to cover the most common use cases.1: github.com/serso/android-checkout2: hackernoon.com/implementing-in-app-billing-in-android-4896232c7d6b

Sergey Solovyev
Guest
Sergey Solovyev
7 months 1 day ago

I wonder why devs working at Google didn't even try to look for existing in-app billing libraries, there is quite few of them. Not invented here syndrome?Checkout [1], for example, has been around for more than 3 years. It has a high test coverage (~70-80% depending on metric), good API (Volley-like) and it is used by a lot of developers (>700 stars on github).Here [2] you can read about how to integrate the library and how to cover the most common use cases.1: github.com/serso/android-checkout2: hackernoon.com/implementing-in-app-billing-in-android-4896232c7d6b

Yakiv Bondar
Guest
Yakiv Bondar
7 months 15 days ago

How to add base64 public key using new billing library?

Yakiv Bondar
Guest
Yakiv Bondar
7 months 15 days ago

How to add base64 public key using new billing library?

Al El
Guest
Al El
8 months 6 days ago

Would be great if we could have backend notifications like renewals, cancellations…

Al El
Guest
Al El
8 months 6 days ago

Would be great if we could have backend notifications like renewals, cancellations…

Anton Smirnov
Guest
Anton Smirnov
8 months 19 days ago

Lot's of typos in the source code shown: "If", "SkuType.INAPP , skuList" ..

Anton Smirnov
Guest
Anton Smirnov
8 months 19 days ago

Lot's of typos in the source code shown: "If", "SkuType.INAPP , skuList" ..

1 2 3 9
wpDiscuz