You can use Firebase Remote Config to define parameters in your app and update their values in the cloud, allowing you to modify the appearance and behavior of your app without distributing an app update.
This guide walks you through the steps to get started and provides some sample code, all of which is available to clone or download from the firebase/quickstart-ios GitHub repository.
Add Remote Config to your app
Install the Firebase SDK for iOS.
Create the singleton Remote Config object, as shown in the following example:
This object is used to store in-app default parameter values, fetch updated parameter values from the service, and control when fetched values are made available to your app.
During development, it's recommended to set a relatively low minimum fetch interval. See Throttling for more information.
Set in-app default parameter values
You can set in-app default parameter values in the Remote Config object, so that your app behaves as intended before it connects to the Remote Config service, and so that default values are available if none are set in the service.
- Define a set of parameter names, and default parameter values using an NSDictionary object or a plist file.
- Add these values to the Remote Config object using
setDefaults:. The following example sets in-app default values from a
Get parameter values to use in your app
Now you can get parameter values from the Remote Config object. If you later set values in the Remote Config service, fetch them, and then activate them, those values are available to your app. Otherwise, you get the in-app parameter values configured using setDefaults:. To get these values, call the configValueForKey: method, providing the parameter key as an argument.
Set parameter values in the service
Using the Firebase console or the Remote Config REST API, you can create new service-side default values that override the in-app values according to your desired conditional logic or user targeting. This section walks you through the Firebase console steps to create these values.
- In the Firebase console, open your project.
- Select Remote Config from the menu to view the Remote Config dashboard.
- Define parameters with the same names as the parameters that you defined in your app. For each parameter, you can set a default value (which will eventually override the in-app default value) and you can also set conditional values. To learn more, see Remote Config Parameters and Conditions.
Fetch and activate values from the service
- To fetch parameter values from the Remote Config service, call the fetchWithCompletionHandler: or fetchWithExpirationDuration:completionHandler: method. Any values that you set on the Remote Config service are fetched and cached in the Remote Config object.
- To make fetched parameter values available to your app, call the activateFetched method.
For cases where you want to fetch and activate values in one call, use
This example fetches values from the Remote Config service (not cached
values) and calls
activateWithCompletionHandler: to make them available to
Because these updated parameter values affect the behavior and appearance of your app, you should activate the fetched values at a time that ensures a smooth experience for your user, such as the next time that the user opens your app. See Remote Config loading strategies for more information and examples.
If an app fetches too many times in a short time period, fetch calls may be
throttled. In such cases, the backend returns
You are recommended to catch this error and retry in exponential backoff mode,
waiting longer intervals between subsequent fetch requests.
During app development, you might want to refresh the cache very frequently
(many times per hour) to let you rapidly iterate as you develop and test your
app. To accommodate rapid iteration on a project with numerous developers, you
can temporarily add a
FIRRemoteConfigSettings property with
a low minimum fetch interval (
MinimumFetchInterval) in your app.
The default and recommended production fetch interval for Remote Config is 12 hours, which means that configs won't be fetched from the backend more than once in a 12 hour window, regardless of how many fetch calls are actually made. Specifically, the minimum fetch interval is determined in this following order:
- The parameter in
- The parameter in
- The default value of 12 hours
If you haven't already, explore the Remote Config use cases, and take a look at some of the key concepts and advanced strategies documentation, including: