Firebase Remote Update app

The ability to create great applications does not necessarily mean success in business, and there is still much work to be done, and it is no longer possible to announce a "knock-out" after simply releasing the application. You need to be able to quickly make adjustments based on user feedback, test new features, and provide users with the content they care about most.

Firebase remote configuration is the result of this. With Firebase remote configuration, you can change the look and feel of your app in the cloud to quickly respond to your users ' needs. In addition, you can use Firebase remote configuration to deliver different content to different users, enabling experimentation, progressive rollout, and even personalized content based on user interaction in the app.

Updating your app doesn't have to go too much.

We should all have had this experience: Soon after the app was released, we found that the app was in an imperfect place. Perhaps the application of inappropriate or difficult to understand the text, to the user to bring bad experience. Perhaps the game level set is too difficult for the player to pass through at all. Or maybe you just want to add an animation that takes a lot of time to create.

If you want to address these issues in a traditional way, you need to update the values in your app code, build and publish the new version of the app, and then wait for the user to download the new version.

However, if you use the remote Configuration feature in the Firebase platform for your app, you can quickly and easily change these values directly in the cloud. The next time the user launches the app, the remote configuration can download the new values to meet the user's needs, and you don't have to publish the new version of the app at all.

Provide the right content to the right users

In the Firebase remote configuration, you can use the "condition" to provide different configurations to different user groups, that is, to use positioning rules to provide specific values to different users. For example, you can send personalized remote configuration data to users who are in different countries/regions. Alternatively, you can send separate datasets to IOS devices and Android devices separately.

In addition, you can provide users with different values based on the audiences defined in Firebase Analytics for more complex targeting. If you want to change the look of an in-app store, and want to limit the affected users to players who have visited your store but have not purchased anything yet, create a remote configuration value for that subset of audiences to achieve the goal.

Conduct A/B testing and gradually launch new features

With remote configuration conditions, you can provide different values to the random user base. You can use this feature to conduct A/B testing or to progressively launch new features.

If you want to launch a new feature in your app, but aren't sure if the new feature will be popular with your audience, you can hide it in your code with a flag. You can then use the remote configuration to change the value of this flag to enable or disable this feature. For example, by defining a "new feature experiment" condition and setting this condition to open to 10% of users, you can first enable the new feature to a small subset of users and then open it to the rest of the user after making sure that this feature gives the user an excellent experience.

Similarly, you can conduct A/B testing by providing different values to different user groups. Want to know which effect is good when the "buy Now" and "checkout" are displayed on the in-app purchase button for promoting the purchase of items? You can easily find answers to similar questions with A/b test.

Now, if you want to track the results of these A/b tests, simply set a user attribute in Firebase Analytics based on your experimental intent. You can then use this property to filter all Firebase Analytics reports (for example, if the user starts the purchase process). New improvements to A/B testing are coming soon, so stay tuned for the latest updates.

Significantly increase customer viscosity

Fabulous is a healthy lifestyle habit developed by Duke University. The developer wants to experiment with the process of getting the user started, to see which methods are most effective in getting users to start using the app. In addition to A/B testing of pictures, text, and button labels, they also use remote configuration to test the entire novice onboarding process with A/b to determine what sequence of conversations should be displayed to the user.

Their experiments with remote configuration yielded impressive results: the number of users who completed the fabulous beginner process increased from 42% to 64%, and the daily retention rate increased by 27%.

Studies have shown that, on average, user churn in applications occurs primarily in the first 3 days. As a result, improvements to the application onboarding process, such as fabulous, and A/B testing to determine the effectiveness of the improvement measures are essential to ensure long-term success of the application.

Is your app already using remote configuration?

With remote configuration, all default values for the app are stored locally on the device, and only new values that differ from the default values are sent from the cloud to the user. As a result, you can flexibly configure all the values in your app with remote configuration capabilities, and the burden on the network is minimal because only changing values are sent. Turn out all your hard-coded strings, constants, and idle appconstants files (Nothing, everyone has such a file) and use remote configuration for them!

Firebase remote configuration is a feature on the Firebase platform and is free to use on both IOS and Android. To learn more, see our documentation and don't forget to explore all the features of the Firebase SDK.

View Firebase Remote Configuration documentation

Firebase Remote Update app