Connor Wybranowski, Software Engineer | Siggi Jonsson, Staff Software Engineer | Keith McKnight, Staff Software Engineer | Juzheng Li, Engineering Manager
In this section, we’ll discuss how we address our specific needs around remote configuration and decoupling experience delivery from app releases. We suggest reading our first article to gain a holistic overview of our experimentation platform before continuing here. Once you’re ready, let’s dive in!
A lot of work can go into creating a new feature for Tinder. Product Managers and Designers need to figure out what the feature should do and how it should look and feel. Engineers need to write the code that makes it work. Quality Assurance needs to test things to make sure that everything is working properly and that the feature doesn’t create trouble in other parts of the app. …
Written by: Kenneth Yeh | Jinqiang Han | Juzheng Li
Data influences all of the decisions we make at Tinder. We are often faced with decisions focused on which updates to make within the Tinder experience and how we present features to our members. Experimentation plays a vital role in making these decisions.
At Tinder, we’ve built an in-house tool, Phoenix, to manage and optimize all of our experiments. We’re excited to share how we’ve done so, and this is the first part of our three-part series highlighting our Phoenix experimentation platform. First, we will cover the key concepts and design considerations. Second, we will cover Levers, our treasured mechanism for decoupling experiments from app release cycle. …