How Facebook Returned A/B Testing To Mobile Apps
When Facebook rewrote its mobile applications and converted them from custom Web stacks to native development stacks, it lost the ability to perform A/B testing, or to simultaneously test multiple versions of its apps. The social network described how it regained the ability to A/B test in a post on its engineering blog.
When Facebook rewrote its mobile applications and converted them from custom Web stacks to native development stacks, it lost the ability to perform A/B testing, or to simultaneously test multiple versions of its apps. The social network described how it regained the ability to A/B test in a post on its engineering blog.
The blog post detailed the development of what came to be known as Airlock, first explaining the need for A/B testing:
Shipping our apps on iOS and Android requires developers from many different teams to coordinate and produce a new binary packed with new features and bug fixes every four weeks.
WORK SMARTER - LEARN, GROW AND BE INSPIRED.
Subscribe today!
To Read the Full Story Become an Adweek+ Subscriber
Already a member? Sign in