Firebase A/B Testing helps you optimize your app experience by making it easy to run, analyze, and scale product and marketing experiments. It gives you the power to test changes to your app’s UI, features, or engagement campaigns to see if they actually move the needle on your key metrics (like revenue and retention) before you roll them out widely.
About Firebase A/B Testing
Firebase A/B Testing is a component of the Firebase suite of tools for cross-platform application development.
- Test and improve your product experience
- Find ways to re-engage your users by using the Notifications composer
- Safely roll out new features
- Target "predicted" user groups
Using FCM, you can notify a client app that new email or other data is available to sync. You can send notifications to drive user reengagement and retention. For use cases such as instant messaging, a message can transfer a payload of up to 4KB to a client app.
How does it work?
When you create an experiment, you test out one or more variants of a testable action and measure how well the variants perform toward a goal that you want to achieve (such as boosting in-app purchases). Your targeted user group can be defined by multiple criteria chained with "AND" logic; for example, you could limit the group to users of a particular app version who belong to both an Analytics audience such as "crashing users" and a group created automatically by Firebase Predictions based on its likelihood to churn.
With Remote Config, you can experiment with changes to several parameters across multiple variants to alter the behavior and appearance of your app in a variety of ways across each variant group. You could use this for subtle changes like tinkering with the best color scheme and positioning of menu options, or for significant changes like testing a completely new feature or UI design. With the Notifications composer, you can experiment to find the right wording for a notification message.
Whether your experiment uses Remote Config or the Notifications composer, you can monitor your experiment until you have a valid set of results, and then identify the leader, the variant that best accomplishes your goal. You can start your experiment with a small percentage of your user base, and then increase that percentage over time. If your first experiment does not reveal a variant that accomplishes your goal better than your app does currently, you can start a new round of experimentation to find the best way to improve your app.
You can also track other metrics (app crashes, retention, and engagement) along with your goal so that you can have a better understanding of the outcome of your experiment and how it impacts the experience of using your app.
Related tags
firebase
firebase-cloud-messaging
firebase-predictions
firebase-analytics
firebase-remote-config