Have Your Cake and Eat It Too with A/B Testing
summary
Capital One Wallet runs A/B tests with Firebase Remote Config and Swerve, reporting small wins like 5–10% higher push opt‑ins and an 8% lift in notification clicks after swapping text. The talk explains SDK initialization limits (push handling when app isn’t running), content hosting choices (embedded filenames vs URLs for images), Firebase’s Analytics/Remote Config disconnect and the workaround of sending variant IDs, and Swerve’s built‑in conversion vs engagement modes that enforce one‑time conversions and simplify QA and rollouts.
AI-written summary · about
chapters (12)
- 0:00Introduction to A/B testing
- 3:21What is A/B testing?
- 8:09Third-party A/B testing platforms
- 11:16SDK initialization and caching
- 14:43Content management and hosting
- 22:44Analytics and reporting
- 24:50User segmentation and targeting
- 30:15Running A/B tests
- 36:50Scalability and flexibility
- 38:15Extra features to consider
- 41:54QA and testing A/B tests
- 42:56Summary and recommendations
related talks
46mTweaking and AB Testing Your App on the Fly
17mIterate your way to a delightful app experience using Firebase Remote Config and A/B Testing
21mOptimize your app's revenue with Firebase
29mLeverage Firebase to Optimize Your App’s Monetization Strategy
34mA/B Testing You'll Like
25mGrowth Hacking with Firebase
13mPersonalization and A/B Testing: How to create better experiences for users
38mEngage and Keep Your Users in Your App with Firebase