The joys and challenges of building a paywall with BillingClient 5
summary
Shows migrating from legacy SKU-style Billing Library 4 to Billing Library 5 where subscriptions become hierarchical: one subscription with multiple base plans and offers instead of six independent SKUs. Demo uses a Catflix app and a geo-tagged promo that unlocks a DroidCon offer via developer determined eligibility. Notes mandatory upgrade by November, Billing Library 6 removes pending order IDs and tweaks error codes, and the new server API drops transaction prices and changes payment states, so a backend or RevenueCat is often needed for reliable tracking and experiments.
AI-written summary · about
chapters (9)
- 0:00Introduction to paywall talk
- 3:29What is Google Play Billing
- 8:46Billing Library 5 key features
- 10:11Subscription model differences
- 14:04Demo of paywall with Billing 4
- 16:34Demo of paywall with Billing 5
- 19:25Challenges of Billing Library 5
- 21:10Opportunities with Billing Library 5
- 24:58Third-party solutions and resources
related talks
18mThe joys and challenges of building a paywall with BillingClient 5
16mThe joys and challenges of building a paywall with BillingClient 5
17mMigrating to Billing Library 5
30mWhat's new with Play Billing
19mMigrate to Google Play Billing
44mTaking your users’ money: In-app billing from start to best practices
49mTaking your users’ money: In-app billing from start to best practices
36mGrow and optimize your subscriptions with new Google Play features