C. Remote Config

Firebase Remote Config

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. When using Remote Config, you create in-app default values that control the behavior and appearance of your app. Then, you can later use the Firebase console to override in-app default values for all app users or for segments of your userbase. Your app controls when updates are applied, and it can frequently check for updates and apply them with a negligible impact on performance.

Key functions

Function	Description
Quickly roll out changes to your app's userbase	You can make changes to your app's default behavior and appearance by changing server-side parameter values. For example, you could change your app's layout or color theme to support a seasonal promotion, with no need to publish an app update.
Customize your app for segments of your userbase	You can use Remote Config to provide variations on your app's user experience to different segments of your userbase by app version, by Firebase Analytics audience, by language, and more.
Run A/B tests to improve your app	You can use Remote Config random percentile targeting with Firebase Analytics to A/B test improvements to your app across different segments of your userbase so that you can validate improvements before rolling them out to your entire userbase.

How does it work?

Read Google original documentation here.

Implementation path

Step	Description
Instrument your app with Remote Config	Define which aspects of your app's behavior and appearance you want to be able to change using Remote Config, and translate these into the parameters that you will use in your app.
Set default parameter values	Set the in-app default values for Remote Config parameters using RemoteConfig.setDefaults();.
Add logic to fetch, activate, and get parameter values	Your app can safely and efficiently fetch parameter values from the server and activate those fetched values. So, you can write your app without worrying about the best time to fetch values, or even whether any server-side values exist. Your app uses RemoteConfig.getValue method to get the value of a parameter, similar to reading the value of a local variable defined in your app.
(As needed) Update server-side default and conditional parameter values	You can define values in the Firebase console to override in-app default values. You can do this before or after you launch your app, because the same get method access in-app default values and values fetched from the server.

Policies and limits

Note the following policies:

• Don't use Remote Config to make app updates that should require a user's authorization. This could cause your app to be perceived as untrustworthy.
• Don't store confidential data in Remote Config parameter keys or parameter values. It is possible to decode any parameter keys or values stored in the Remote Config settings for your project.
• Don't attempt to circumvent the requirements of your app's target platform using Remote Config.

Remote Config parameters and conditions are subject to certain limits. To learn more, see Limits on parameters and conditions.

Get started with Firebase Remote Config in AdobeAIR

• Parameters and Conditions
• Add Remote Config ANE to your project
• How to initialize Remote Config in your AdobeAIR app

---

DISCRIMINATION: Firebase SDKs are developed by Google and they own every copyright to the Firebase "native" projects. However, we have used their "compiled" native SDKs to develop the ActionScript API to be used in AdobeAIR mobile projects. Moreover, as far as the documentations, we have copied and when needed has modified the Google documents so it will fit the needs of AdobeAIR community. If you wish to see the original documentations in Android/iOS, visit here. But if you are interested to do things in AdobeAIR, then you are in the right place.