Remote Config in Android Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Remote Config in Android development?

Remote Config is a cloud service that lets you change your app's behavior and appearance without publishing an app update. You can update values remotely and your app fetches them to apply changes instantly.

beginner

How do you fetch and activate Remote Config values in Kotlin?

You call fetch() to get values from the server, then activate() to apply them. Usually combined as fetchAndActivate() for simplicity.

beginner

What is the purpose of setDefaults() in Remote Config?

It sets default values locally in your app. These values are used if fetching from the server fails or before the first fetch.

intermediate

Why is it important to cache Remote Config values?

Caching avoids frequent network calls, improving app performance and reducing data usage. Remote Config SDK manages caching automatically with a minimum fetch interval.

intermediate

How can Remote Config help in A/B testing?

You can create different parameter values for different user groups remotely. This helps test features or UI changes without releasing multiple app versions.

Which method fetches Remote Config values and applies them immediately?

A setDefaults()

B fetchAndActivate()

C activate()

D initialize()

fetchAndActivate() fetches values from the server and activates them in one call.

What happens if Remote Config fetch fails and no defaults are set?

A App uses last cached values or empty values

B App crashes

C App fetches again immediately

D App shows an error dialog

If fetch fails, the app uses cached values or empty values if no defaults are set.

Why should you avoid fetching Remote Config too frequently?

A It disables Remote Config

B It can cause app to freeze

C It deletes local data

D It wastes battery and network data

Frequent fetches waste battery and network data; Remote Config SDK enforces minimum fetch intervals.

Which of these is NOT a typical use case for Remote Config?

A Updating app logic code

B Showing different messages to users

C Running A/B tests

D Changing app theme colors remotely

Remote Config cannot update app code; it only changes parameters and UI behavior.

How do you set default Remote Config values in Kotlin?

A remoteConfig.activate()

B remoteConfig.fetch()

C remoteConfig.setDefaults(R.xml.remote_config_defaults)

D remoteConfig.initializeDefaults()

setDefaults() loads default values from a resource XML file or a map.

Explain how Remote Config helps you change app behavior without releasing a new version.

Think about how you can update app settings remotely.

Describe the steps to safely use Remote Config values in your Android app.

Consider what happens before and after fetching.

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