When to conduct A/B testing for your game
An A/B test enables you to compare two different versions or builds of your own game enabling you to see exactly how player experience changes with the build.
Here's how we make it work:
Start with version A: First, we'll set up a playtest for your initial version.
The first round works just like our standard playtests: players try your version A of the game, share their thoughts, and provide feedback through both gameplay recordings and surveys. Once these sessions are complete, you'll have a baseline of data to compare against version B.
Moving to version B: This gives you direct, player-to-player comparisons of the changes in the gaming experience. To prevent bias in the responses, the order in which the versions are shown to the players are alternated between different cohorts of players.
Why this approach works: Players can provide a comparative review of the different versions of the same game, noting specific improvements or changes that caught their attention. Plus, since they're already familiar with the basic concept of your game, they can focus more on the differences and how that affects their gameplay.
After both tests are complete, you'll receive:
Gameplay recordings showing how individual players approached each version
Survey responses that specifically address the comparative experience
Clear insights into which version performs better for specific aspects of your game
This structured approach to A/B testing helps you make data-driven decisions about your game's development. Whether you're testing different tutorial approaches, UI layouts, or game mechanics, you'll get clear evidence of what resonates better with your target players.
Interested in conducting an A/B test? Reach out to us at playtesting@lysto.io.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article