Firebase Remote Config is a cloud service that lets you change the behavior and appearance of your app without requiring users to download an app update. You can use Remote Config to deliver different features or content to different segments of your user base, such as showing a different app theme to users in other countries or regions. You can also use Remote Config to run A/B tests, which are experiments that compare two or more variants of a feature or content to see which one performs better. A/B testing helps you optimize your app for your business goals, such as increasing user engagement, retention, or revenue.
Let’s look at how to set up a Remote Config in Firebase.
After login Firebase, from the left side menu, under Project shortcuts, there is Remote Config option.
Click this option would navigate the user to the remote config config page. Notice this Add parameter button at the right side of the screen on the top of search bar.
Click this Add parameter will take the user to the Create parameter page.
Here is the place for the user to either create a Remote config(Remote feature toggle), with or without any condition or experiment
Now, Let’s look at different scenarios:
Scenario #1- Remote Config/ Remote feature toggle
Like the screenshot displayed, here, we created a remote config by adding
- parameter name: for instance, my_remote_config
- Data type: Boolean
- Condition
Now, about how to set up condition,
In the above screenshot
- Name: give the condition a name, for instance, `version check`
- Applies if: are those conditions that need to use. Here you can specify a platform and app version to use this condition when the condition value is satisfied.
Scenario #2- A/B Test
From the above Edit parameter screen, click Add new , the menu pops up and Experiment is the middle option.
Click Experiment and the following screen shows up for you to set up your experiment.
- Experiment name: give a name for the experiment. For instance, here I am having
Experiment_remote_config
- Targeting is the audience that you want this experiment to experiment on. Here is the place to determine the percentage of the app users that will be involved in this experiment, the maximum is 100%.
- Now the last is variants and it is the interesting bit.
- In order to commence a A/B or A/B/C test, you will need to set
- Variants: 1> Baseline, 2> V1(Variant A), 3>V2(Variant B) as below screenshot , for instance. The value for each section will be used to determine the feature/UI variation.
- Variant weights: this is the place where you can adjust the audience size
When all the above settings are finalized, a remote config will need to be published to be able to take place.
In the app, the relevant feature toggle code will be matching with the remote config parameter’s value and then the app will behave differently based on the config.
That will be all for now.
Thanks for reading.
If you found this article useful please clap and follow me. I’d appreciate it your support and producing more useful content.