Was this helpful?

Deprecated

Mobile Analytics is now App Monitoring and content about Mobile Analytics is deprecated. For documentation related to these features, please see App Monitoring content, such as Configuring app-specific features.

For information on migrating to App Monitoring, see Migrating from Mobile Analytics to App Monitoring.

You just added a new photo feature to your mobile application. When a user clicks a “Photo” button in the user interface, your app takes a photo. You tested the feature, but you’re not sure if users will like it. Furthermore, there’s always the possibility that the new feature might not work properly despite the testing you performed.

You can use Mobile Analytics to turn on the new feature, making it available in your app to users. But you can also make it easy to turn off the new feature if there are any problems. You can turn on or off the new feature by specifying an application-specific configuration for your app and then integrating the configuration into your code.

Step 1: Specify app-specific settings

Open the Default Configs page. This will apply the configuration to all devices running your app. Then in the Application Specific Configs section of the page, specify a category, key, and value for the new feature, for example:

Category Key Value
FEATURES enableCamera true

The category groups together configured features. What you include in each category is also up to you. In this example, FEATURES is a category that includes new features such as the photo feature.

The Key identifies a particular feature. In this case, enableCamera identifies the photo feature.

The Value controls the handling of the feature. In this example, the value ‘true’ for enableCamera means that the photo feature will be turned on in the app.

Step 2: Get the configuration

Add code to your app that enables Mobile Analytics to get the configuration for the new feature. For example, here’s the code you would need to write for the Android version of your app to enable Mobile Analytics to get the configuration for the enableCamera photo feature. The code also displays or hides the photo button based on the value of enableCamera:

protected void newFunctionality()
{
    String enableCamera = MAConfig.getValue("FEATURES", "enableCamera");
    
    LinearLayout cameraButton = (LineraLayout) findViewById(R.id.dashboard_photo_btn)
        
   //Toggles button
   if (enableCamera != null && enableCamera.equals("false"))
          ((LinearLayout)cameraButton.getParent()).removeView(cameraButton);
} 

For iOS, you will need to use the iOS application-specific configuration APIs. See the section “Optional: Enable application-specific configuration” in Add monitoring to your iOS application for details.

Step 3: Turn off the feature if needed

When the user runs your app, the camera feature will be initially turned on because the value of the feature is set to true in the application-specific configuration. If you need to turn off the feature, simply change its value to false in the Application Specific Configs.

Category Key Value
FEATURES enableCamera false

The next time a user runs your app, the camera feature will not be available and the camera button will not display.

Turn on/off features in a Beta Test or A/B Test

You can also turn a feature on or off for a smaller set of users. You can do this using a Beta Test configuration or A/B test configuration, and integrating the configuration into your code. For details, see Configure your app .

Help or comments?

  • Something's not working: See Apigee Support
  • Something's wrong with the docs: Click Send Feedback in the lower right.
    (Incorrect? Unclear? Broken link? Typo?)