Paktor avoids a HUGE mistake by A/B testing before deploying
Paktor is an innovative mobile dating app targeting the Asia market that emphasizes simplicity and ease of use. With Paktor, finding a match is as simple as a swipe and a click.
The Paktor team was ready to implement a change to the app that they were pretty sure would increase engagement in the app by making it easier to like and dislike potential matches. Thankfully, they tested it first and avoided a mistake that would have cost them a 26% loss in month over month growth.
They tested these two variants. Can you guess which was the one that cost them users?
Read the full case study to find out.
Thanks for
reading!
More articles you might be interested in:
When to Use Multivariate Testing vs. AB Testing
Deciding between sequential and multivariate testing without knowing their advantages and limitations can pose significant challenges. If you’re looking to optimize your app’s conversion rate, sequential A/B tests, or experiments with two variants, usually do the trick. But in some...
Read MoreHow Segmentation Can Correct Misleading A/B Testing Results
When looking at A/B testing results, just seeing that one variant is statistically significantly better than another sometimes does not tell the whole story. As experimenters and business decision makers, what we really want to know is why. Did users...
Read More5 Easy Ways to Improve Your App with A/B Testing
Here are 5 ideas for relatively easy to implement tests to visual aspects of your app. You most likely won’t need to rework user flows or do a lot of complex coding. These are layout and design changes that can...
Read More