Remote Config in Android Kotlin

Introduction

Remote Config lets your app change its behavior and appearance without updating the app. You can update settings or features remotely.

You want to change app colors or text without releasing a new version.

You want to enable or disable features for some users remotely.

You want to run A/B tests by changing values for different user groups.

You want to fix small bugs or tweak settings quickly without app store approval.

You want to personalize app content based on user location or preferences.

Syntax

Android Kotlin

val remoteConfig = Firebase.remoteConfig
val configSettings = remoteConfigSettings {
    minimumFetchIntervalInSeconds = 3600
}
remoteConfig.setConfigSettingsAsync(configSettings)
remoteConfig.setDefaultsAsync(R.xml.remote_config_defaults)

remoteConfig.fetchAndActivate().addOnCompleteListener { task ->
    if (task.isSuccessful) {
        val welcomeMessage = remoteConfig.getString("welcome_message")
    }
}

Use fetchAndActivate() to get and apply remote values.

Set default values in XML to have fallback if fetch fails.

Examples

Simple fetch and activate remote config values.

Android Kotlin

val remoteConfig = Firebase.remoteConfig
remoteConfig.fetchAndActivate()

Set default values programmatically instead of XML.

Android Kotlin

remoteConfig.setDefaultsAsync(mapOf("welcome_message" to "Hello!"))

Get a string value from remote config.

Android Kotlin

val message = remoteConfig.getString("welcome_message")

Sample App

This app shows a message from Remote Config on screen. It sets a default message, fetches remote values, and updates the text.

Android Kotlin

import android.os.Bundle
import androidx.appcompat.app.AppCompatActivity
import com.google.firebase.ktx.Firebase
import com.google.firebase.remoteconfig.ktx.remoteConfig
import com.google.firebase.remoteconfig.ktx.remoteConfigSettings
import android.widget.TextView

class MainActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        val textView = TextView(this)
        setContentView(textView)

        val remoteConfig = Firebase.remoteConfig
        val configSettings = remoteConfigSettings {
            minimumFetchIntervalInSeconds = 3600
        }
        remoteConfig.setConfigSettingsAsync(configSettings)
        remoteConfig.setDefaultsAsync(mapOf("welcome_message" to "Welcome!"))

        remoteConfig.fetchAndActivate().addOnCompleteListener { task ->
            if (task.isSuccessful) {
                val message = remoteConfig.getString("welcome_message")
                textView.text = message
            } else {
                textView.text = "Failed to load message"
            }
        }
    }
}

Important Notes

Remote Config values are cached locally for the minimum fetch interval.

Always set default values to avoid empty or null results.

Test remote config changes carefully before releasing to all users.

Summary

Remote Config lets you change app behavior without app updates.

Use fetchAndActivate() to get and apply values.

Always provide default values for safety.

Practice

1. What is the main purpose of Firebase Remote Config in an Android app?

easy

A. To manage user authentication and login

B. To store user data locally on the device

C. To change app behavior and appearance without releasing a new app version

D. To handle app crashes and error reporting

Solution

1. Step 1: Understand Remote Config functionality

   Remote Config allows developers to update app behavior remotely without requiring users to download a new version.

2. Step 2: Compare options with Remote Config purpose

   Options B, C, and D relate to other Firebase services, not Remote Config.

3. Final Answer:

   To change app behavior and appearance without releasing a new app version -> Option C

4. Quick Check:

   Remote Config = Change app behavior remotely [OK]

Hint: Remote Config updates app without new installs [OK]

Common Mistakes:

• Confusing Remote Config with local data storage
• Mixing Remote Config with authentication features
• Thinking Remote Config handles crash reports

2. Which Kotlin code snippet correctly fetches and activates Remote Config values asynchronously?

easy

A. remoteConfig.fetchAndActivate().addOnCompleteListener { task -> if (task.isSuccessful) { applyConfig() } }

B. remoteConfig.fetch().activate()

C. remoteConfig.activate().fetch()

D. remoteConfig.fetchAndActivate { applyConfig() }

Solution

1. Step 1: Identify correct method chaining for fetch and activate

   The correct method is fetchAndActivate() which returns a Task to listen for completion.

2. Step 2: Check syntax for asynchronous handling

   remoteConfig.fetchAndActivate().addOnCompleteListener { task -> if (task.isSuccessful) { applyConfig() } } uses addOnCompleteListener properly to handle success and then apply config.

3. Final Answer:

   remoteConfig.fetchAndActivate().addOnCompleteListener { task -> if (task.isSuccessful) { applyConfig() } } -> Option A

4. Quick Check:

   fetchAndActivate() with listener = remoteConfig.fetchAndActivate().addOnCompleteListener { task -> if (task.isSuccessful) { applyConfig() } } [OK]

Hint: Use fetchAndActivate() with addOnCompleteListener [OK]

Common Mistakes:

• Calling activate() before fetch()
• Using fetch() and activate() separately without chaining
• Passing a lambda directly to fetchAndActivate()

3. Given this Kotlin code snippet, what will be printed if the Remote Config parameter "welcome_message" is not set remotely and default is "Hello"?

val welcome = remoteConfig.getString("welcome_message")
println(welcome)

medium

A. Hello

B. null

C. An empty string

D. welcome_message

Solution

1. Step 1: Understand getString behavior with default values

   If the parameter is not set remotely, Remote Config returns the default value provided in app defaults.

2. Step 2: Recognize default value is "Hello"

   The default for "welcome_message" is "Hello", so getString returns "Hello".

3. Final Answer:

   Hello -> Option A

4. Quick Check:

   Missing remote value returns default string [OK]

Hint: Missing remote key returns default value [OK]

Common Mistakes:

• Expecting null instead of default
• Assuming empty string if not set
• Confusing key name with value

4. What is wrong with this Kotlin code snippet for fetching Remote Config values?

remoteConfig.fetchAndActivate()
println(remoteConfig.getString("feature_flag"))

medium

A. fetchAndActivate() must be called on the main thread

B. feature_flag key must be an integer, not string

C. fetchAndActivate() requires a callback parameter

D. getString() is called before fetchAndActivate() completes

Solution

1. Step 1: Analyze asynchronous fetchAndActivate call

   fetchAndActivate() runs asynchronously, so calling getString immediately after may use old values.

2. Step 2: Identify missing completion handling

   Code lacks a listener or await to ensure fetchAndActivate finished before reading values.

3. Final Answer:

   getString() is called before fetchAndActivate() completes -> Option D

4. Quick Check:

   Must wait for fetchAndActivate() completion [OK]

Hint: Wait for fetchAndActivate() to finish before reading values [OK]

Common Mistakes:

• Assuming fetchAndActivate() is synchronous
• Not adding completion listeners
• Confusing key types

5. You want to show a special promotion banner only to 30% of your users using Remote Config. Which approach is best to implement this in Kotlin?

hard

A. Fetch a random number in app and show banner if number < 0.3

B. Create a Remote Config parameter "show_promo" with boolean true/false and use Firebase percentage rollout targeting

C. Use a local SharedPreferences flag to randomly enable banner for 30% users

D. Hardcode banner visibility in app and update app version for changes

Solution

1. Step 1: Understand Remote Config targeting features

   Firebase Remote Config supports percentage rollouts to control feature exposure to a subset of users.

2. Step 2: Choose parameter with percentage rollout

   Setting a boolean parameter "show_promo" with percentage targeting is the best practice for controlled rollout.

3. Final Answer:

   Create a Remote Config parameter "show_promo" with boolean true/false and use Firebase percentage rollout targeting -> Option B

4. Quick Check:

   Use Remote Config percentage rollout for user targeting [OK]

Hint: Use Remote Config percentage rollout, not local random logic [OK]

Common Mistakes:

• Using local random logic instead of Remote Config targeting
• Hardcoding feature flags requiring app updates
• Ignoring Remote Config's built-in user segmentation