The State off in app purchases on Android
summary
Explains current Android commerce: managed products (consumable vs non‑consumable) and subscriptions, and recommends migrating from community wrappers to the Play Billing Library with BillingClient and PurchasesUpdatedListener. Details testing options: static test SKUs, cumbersome real purchases requiring a published APK, and licensed testers with fake purchases where subscription tests last 5 minutes to 30 minutes and auto‑renew only up to six times (max ~3 hours). Describes using the open source Register fake billing service and a Kotlin Multiplatform remote‑config A/B pricing system that maps semantic product IDs across stores.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 2:05Managed products
- 8:38The journey
- 15:57The components
- 17:55Pros and cons
- 22:03When did the library come out
- 23:14Android InApp Billing v3
- 24:30Testing
- 24:51Why testing
- 25:06Tools
- 25:35Static responses
- 26:55Subscriptions
- 27:42Steps
- 29:08I dont remember
- 30:18Fake purchases
- 32:36New York Times Register Library
- 34:41Play Binary
- 35:17Register
- 35:30Why AB Testing
- 36:48AB Testing Infrastructure
- 37:03Product IDs
- 37:57Multiplatform testing
- 39:59Play Store Console
- 40:27Order Details
- 40:46More Details
- 41:11Financial Reports
- 41:45Limitations
- 41:59Sandbox environment
- 42:25Subscription support
- 43:16Questions
related talks
49mTaking your users’ money: In-app billing from start to best practices
44mTaking your users’ money: In-app billing from start to best practices
34mTesting In App Billing the Easy Way
23mIn-App Subscriptions for all Android devices
35mIn-App Billing Version 3
19mMigrate to Google Play Billing
36mGrow and optimize your subscriptions with new Google Play features
23mCoroutine-Driven Android Billing- Use Cases, Fallbacks, and Functional Programming