Remote Config : Dynamically Change your app’s Behavior - Huawei Developers

This is originally from HUAWEI Developer Froum
Forum link: https://forums.developer.huawei.com/forumPortal/en/home
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
Remote config is a feature that allows us to alter both the look and feel of our application without the need to publish any updates to the App Gallery. This works by allowing us to define in-app parameters that can be overridden from within the Huawei App Gallery Connect — these parameters can then be activated for either all or a defined selection of users.
This powerful feature gives us a range of new abilities when it comes to immediate updates, temporary changes or testing new features amongst users. Let’s take a dive and learn the what, why and how of Remote Config so we can learn how to use it to benefit both ourselves and our users
Use Cases
1. Releasing new functions by user percentage.
2. Display country/region-specific promotion content.
3. Personalized content recommendation based on Huawei Analytics.
4. Holiday theme adaptation.
Development Process
· Create sample application in android and configure into AGC.
· Enable Remote Configuration API.
· Download agconnect-service.json and add into app directory.
· Add remote config dependencies in the build.gradle file in app directory.
Code:
implementation 'com.huawei.agconnect:agconnect-remoteconfig:1.3.1.300'
· Open AGC select Demo project Growing->Remote Config Now enable Remote Config service
After enabling service, you will get option
· Parameter Management.
· Condition Management.
Parameter Management:
Within Remote Config we define key-value pairs which are known as parameters. These parameters are then used to define the configuration values that are to be used within our app.
· Key — The key is a String used to define the identify for the parameter
· value — The value can be of any other data type and is used to represent the value of our defined parameter.
· After saving parameter management details we can check ,you can add, modify, delete in existing parameters.
Condition Management
Conditions are a collection of rules that we can use to target specific app instances —for example based on gender we can update new changes.
The conditional value itself is also represented as a key-value pair, it’s made up of:
· condition — The condition to be satisfied for the value to be used
§ App version
§ OS version
§ Language
§ Country/Region
§ Audience, etc..
· value — The value to be used if the condition is satisfied
Let’s see code Implementation
· Create Instance for AGConnectConfig
Code:
AGConnectConfig config = AGConnectConfig.getInstance();
· Create config.xml file ,you can set default parameter values before connecting to remote config service.so that your app can run perfectly.
Code:
<?xml version="1.0" encoding="utf-8"?>
<remoteconfig>
<value key="version">1.0</value>
</remoteconfig>
· Call Api to pass default values this will effect immediately.
Code:
config.applyDefault(R.xml.remote_config);
· Fetching parameter values from Remote Configuration
Code:
config.fetch(fetchInterval).addOnSuccessListener(new OnSuccessListener<ConfigValues>() {
@Override
public void onSuccess(ConfigValues configValues) {
config.apply(configValues);
config.getMergedAll();
long remoteVersionCode = config.getValueAsLong("version");
if (currentVersionCode > remoteVersionCode) {
ShowUpdateAlert();
}
Toast.makeText(getBaseContext(), "RemoteVersionCode: "+String.valueOf(remoteVersionCode), Toast.LENGTH_LONG).show();
}
}).addOnFailureListener(new OnFailureListener() {
@Override
public void onFailure(Exception e) {
Toast.makeText(getBaseContext(), "Fetch Fail", Toast.LENGTH_LONG).show();
}
});
This is not the end. For full content, you can visit HUAWEI Developer Forum.​