Taking your users’ money: In-app billing from start to best practices
summary
Covers a concrete recipe: use the Google Play billing library (client + PurchasesUpdatedListener) and the Google Play Developer API to verify purchase tokens on a backend, not on-device; uses Register and BillingX as test helpers; notes real-time notifications for subscription state changes and the publish-to-test requirement for subscription testing (emulator unsupported). Points out quirks: must supply SKUs to query, consumption can misreport, fees are 70/30 (drops to 15% after 12 months).
AI-written summary · about
chapters (8)
- 0:00Start
- 12:03set up your google play store listings
- 19:29set up your app listing for the play store
- 23:43set your product active or inactive at any time
- 25:12support 20 different locales
- 25:44get a list of products
- 28:37roll out a new version of the app
- 36:53get the original json payload from your google play store
related talks
44mTaking your users’ money: In-app billing from start to best practices
44mThe State off in app purchases on Android
46mA deep dive into
34mTesting In App Billing the Easy Way
35mIn-App Billing Version 3
23mIn-App Subscriptions for all Android devices
30mWhat's new with Play Billing
36mGrow and optimize your subscriptions with new Google Play features