Stackpane Stackpane
Download

Remote Config

Manage Remote Config parameters, conditions, and version history with rollback support.

Overview

The Remote Config interface lets you manage Firebase Remote Config parameters directly from Stackpane. View all parameters, edit their values and types, set up conditional values, manage conditions, and browse version history with rollback support.

Prerequisites

Stackpane uses the Firebase Remote Config API to power this feature. It must be enabled in your Google Cloud project.

gcloud services enable firebaseremoteconfig.googleapis.com --project YOUR_PROJECT_ID
  • Required IAM roles: Firebase Remote Config Viewer (roles/cloudconfig.viewer) for read access, or Firebase Remote Config Admin (roles/cloudconfig.admin) for read/write access
  • Cost notes: Remote Config is free. There are no charges for storing or fetching configuration values. API rate limits apply (write operations are limited to 5 per minute per project).

Parameter Table

Navigate to Remote Config from the sidebar. Parameters load automatically and display in a table:

  • Key — the parameter name used in your application code
  • Default Value — the value served when no conditions match
  • Type — the value type (String, Number, Boolean, JSON)
  • Description — a description of the parameter’s purpose

Click a parameter to edit it, or use the context menu to delete it.

Creating Parameters

  1. Click New Parameter in the toolbar.
  2. Enter a unique parameter key (e.g., maintenance_mode, feature_banner_text).
  3. Select the value type: String, Number, Boolean, or JSON.
  4. Enter a description explaining the parameter’s purpose.
  5. Enter the default value.
  6. Click Create to add the parameter and publish the updated template.

Editing Parameters

  1. Click a parameter in the table to open the editor.
  2. Modify the default value.
  3. Change the value type if needed (Stackpane validates the value against the type).
  4. Edit the description.
  5. Toggle Use in-app default to skip setting a server-side value and let the app’s built-in default take effect.
  6. Add or modify conditional values (see below).
  7. Click Save to update and publish.

Conditional Values

Conditional values let you serve different parameter values based on conditions:

  1. In the parameter editor, add a conditional value.
  2. Select a condition from the list of defined conditions.
  3. Enter the value to serve when that condition is met.
  4. Add multiple conditional values for different conditions.

Conditions are evaluated in order. The first matching condition determines the value served.

Managing Conditions

Conditions define targeting rules for conditional parameter values:

  1. Scroll to the Conditions section below the parameter table.
  2. Click New Condition to create one.
  3. Enter a name (e.g., “Beta Users”, “iOS Users”).
  4. Enter the expression using Firebase’s targeting syntax.
  5. Select a tag color for visual identification (Blue, Green, Orange, Red, Purple, Brown, Cyan, Teal).

Edit or delete existing conditions from the condition list. Deleting a condition removes all associated conditional values from parameters.

Version History

Click the History button in the Remote Config toolbar to view all configuration versions.

Each entry shows:

  • Version number — a sequential identifier for the configuration change
  • Updated — the timestamp of the change
  • Updated by — the user or service account that made the change
  • Update type — how the change was made (e.g., console, REST API, rollback)

Rollback

If a configuration change causes issues, roll back to a previous version:

  1. Find the target version in the history table.
  2. Click Rollback on that version entry.
  3. Confirm the rollback in the dialog.
  4. The configuration template is immediately reverted to the selected version.

The rollback itself creates a new version entry in the history, so you have a complete audit trail. Remote Config retains up to 300 versions of your template.

Usage Insights

The Usage Insights feature analyzes your Remote Config data to identify:

  • Never-changed parameters — parameters that have the same value since creation and may be candidates for hardcoding
  • Stale parameters — parameters that have not been updated in a long time
  • Unused conditions — conditions that are not referenced by any conditional values

Publishing

When you save a parameter change, Stackpane publishes the updated Remote Config template immediately. The new values take effect the next time your client apps fetch the config.

Tips

  • Use descriptive parameter keys that match your code’s config references
  • Add descriptions to every parameter so team members understand their purpose
  • Use conditions to gradually roll out features to specific user segments
  • Review version history after making changes to confirm your updates were published correctly
  • Use rollback as a fast recovery mechanism during incidents rather than manually reverting individual parameters
  • Periodically review Usage Insights to keep your configuration lean