Remote Config in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

How does Remote Config update UI values?

You have a TextView showing a welcome message. After fetching Remote Config values, which code snippet correctly updates the TextView with the new value?

Android Kotlin

val welcomeMessage = remoteConfig.getString("welcome_message")
// Update TextView here

A textView.setText(welcomeMessage.toInt())

B textView.text = welcomeMessage

C textView.text = remoteConfig.getBoolean("welcome_message").toString()

D textView.text = null

💡 Hint

Remember, Remote Config values are strings and TextView.text expects a string.

Remote Config values are retrieved as strings. To update a TextView, assign the string value directly to textView.text.

❓ lifecycle

intermediate

When should you fetch Remote Config values?

In an Android app, when is the best time to fetch Remote Config values to ensure the app shows the latest configuration without delaying startup?

A Fetch Remote Config values in a background thread after initial UI is shown

B Fetch Remote Config values in onResume() and update UI after fetch completes

C Fetch Remote Config values only when the user clicks a refresh button

D Fetch Remote Config values in onCreate() and apply them immediately before showing UI

💡 Hint

Think about user experience and app responsiveness.

Fetching Remote Config in the background after UI shows avoids delaying app startup and allows updating UI when new values arrive.

🔧 Debug

advanced

Why does Remote Config fetch fail with a timeout?

You notice Remote Config fetch calls fail with a timeout error on some devices. What is the most likely cause?

A App is running in debug mode

B Remote Config keys are misspelled in the app code

C Remote Config values are not set in the Firebase console

D Device has no internet connection or poor network quality

💡 Hint

Timeout errors usually relate to network issues.

Timeout errors happen when the device cannot reach the Remote Config server due to no or poor internet connection.

🧠 Conceptual

advanced

What is the purpose of default Remote Config values?

Why should you set default values for Remote Config parameters in your app?

A To ensure the app has safe fallback values when Remote Config fetch fails

B To speed up Remote Config fetch calls

C To prevent the app from compiling without Remote Config keys

D To disable Remote Config features in production

💡 Hint

Think about what happens if the app cannot get values from the server.

Default values provide fallback settings so the app behaves predictably even if fetching Remote Config fails.

❓ navigation

expert

How to trigger navigation change based on Remote Config?

You want to navigate to a special promotion screen only if Remote Config parameter "show_promo" is true. Which code snippet correctly performs this navigation in an Android app using Kotlin?

Android Kotlin

val showPromo = remoteConfig.getBoolean("show_promo")
// Navigate if showPromo is true

A if (showPromo == "true") { startActivity(Intent(this, PromoActivity::class.java)) }

B if (showPromo.equals(true)) { startActivity(Intent(this, PromoActivity::class.java)) }

C if (showPromo) { startActivity(Intent(this, PromoActivity::class.java)) }

D if (showPromo != null) { startActivity(Intent(this, PromoActivity::class.java)) }

💡 Hint

Remember the type returned by getBoolean and how to check it.

getBoolean returns a Boolean, so a simple if (showPromo) check is correct. Comparing to string or using equals is incorrect.

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