A/B Testing From The Ground Up
summary
Yelp’s Android experimentation platform uses repeatable bucketing by hashing an identifier with an experiment-specific salt to avoid correlated assignments, supports parameterized experiments via Firebase Remote Config or Facebook PlanOut to simplify complex UI combinations, and persists client events to a tape queue + job manager (flush every 30s or 20 events, immediate flush on background) for delivery; internal analysis exports to BigQuery, and measured delivery loss is about 0.3%, an accepted trade-off.
AI-written summary · about
chapters (12)
- 0:00Introduction to A/B testing
- 1:22Why run A/B tests
- 5:34Key A/B testing infrastructure
- 9:04Bucketing system pitfalls
- 11:12Bucketing system implementation
- 13:17Parameter-based experiments
- 17:08On-device logging principles
- 24:07Event deliverability challenges
- 29:59Analyzing experiment results
- 33:08Internal vs third-party metrics
- 37:14Takeaways and resources
- 39:17Q&A session
related talks
55mHow to Improve Your Game's Retention & Monetization Through Data-Driven Experimentation
28mOptimizing your A/B testing roadmap
24mMobile Experimentation
33mAndroid Benchmarking and other stories
25mMake a Difference with Simple A/B Testing
29mAndroid Benchmarking and other stories
43mLean QA: Automation, Monitoring, Experiments
34mA\B Test Best Practices and Fun Case Studies from Deliveroo
