To amend a mobile app (even at a low extent, for instance, to change the name of a button), it’s necessary to develop a new version, upload it to the app market and wait for testing. This procedure can take a few days, which may negatively affect the project and mobile business. Remote Config helps to avoid this need.

Remote Config is intended for changing the app’s logic and design without its redevelopment. It’s one of the Firebase’s cloud services available for Android and iOS applications.

The use of Remote Config creates a set of various parameters that are assigned default values to and supposed to be changed in the future. Further on, a Firebase or API console helps pre-determine these values for all users or particular user segments. The app can independently control the need for updates and an update checking frequency (with the minimum use of device resources).

 

The main Remote Config features include:

  • Quick and convenient app amendment, e.g., changing the way certain elements are displayed, changing design, banners etc.
  • Setting the app for particular user segments (its personalization).
  • Launching A/B tests, e.g., checking improvements on a small percentage of users before implementing these improvements in the app.

A couple of examples of using Remote Config:

Content amendment. In one of our projects (NYMF mobile app), we resorted to Remote Config to implement timer control options (time left till the subsequent content update). For this purpose, we determined the following main values: update date and time, upcoming content preview (for subscribed users only), heading etc. The advantage of this implementation lies in the fact that there’s no need to independently develop a server code; all changes are quickly and conveniently made via the Firebase console; the users promptly get all updates.

Ad banner management. This implies enabling or disabling a special offer for a particular user segment, or in-app seasonal discount management. It is possible both to manage pre-set layout parameters, and to link to a ready-made banner in .jpg or .png.

Purchase screens A/B testing. To optimize and improve conversion, we suggest developing a few purchase screen option and determining the best one (with the highest conversion rate).

In-app ad display management. An in-app ad is a classic project monetization technique. To optimize the ad display (to show ads to particular segments, e.g., those that are unlikely to make a purchase) and manage it (to enable and disable separate placements, to control intensity), we suggest envisaging these parameters in Remote Config.

 

Remote Config Policy:

  • It’s inappropriate to use Remote Config for updating apps that need user authorization. Depending on parameters’ type and number, such apps may be considered unreliable.
  • Remote Config makes it possible to decode and store various parameter keyd, but it’s not recommended to store confidential data in parameters’ key or values.
  • Don’t try to circumvent the target platform requirements via Remote Config.

☝️Please be advised that Firebase can fit up to 2000 parameters and 500 conditions. The keys may be up to 256 characters long, have to start with an underline or an English letter (AZ, az), and can contain digits. The total length of parameter value lines is not supposed to exceed 800 000 characters.

For more details on how Remote Config works and can be connected to a mobile app, please visit Firebase official documents.