Manages Firebase Remote Config templates, feature flags, loading strategies, and SDKs (Android, iOS). Use when downloading/deploying remoteconfig JSON templates, managing version history/feature flags, setting in-app defaults, fetchAndActivate(), real-time listeners, or SDK setup. Don't use for Firebase Hosting, Auth, Firestore, Data Connect, Crashlytics, or App Hosting.
Permissions
Files
Manages Firebase Remote Config templates, feature flags, loading strategies, and SDKs (Android, iOS). Use when downloading/deploying remoteconfig JSON templates, managing version history/feature flags, setting in-app defaults, fetchAndActivate(), real-time listeners, or SDK setup. Don't use for Firebase Hosting, Auth, Firestore, Data Connect, Crashlytics, or App Hosting.
This skill provides a complete guide for getting started with Remote Config on Android or iOS. Remote Config allows you to change the behavior and appearance of your app without publishing an app update by maintaining a cloud-based configuration template.
Version history
Provisioning Remote Config requires both a Firebase project and a Firebase app,
either Android or iOS. To manage the Remote Config template and conditions via
the command line, use the Firebase CLI. See the firebase-basics skill for
references on project initialization.
If npx -y firebase-tools@latest fails due to registry permissions (403 error):
firebase command directly if the
user confirms it is installed globally (npm install -g firebase-tools).If a command fails because "no active project is selected":
npx -y firebase-tools@latest login:list.--project <PROJECT_ID> to every subsequent command.To learn how to set up Remote Config in your application code, choose your platform:
Follow these guidelines and use the associated CLI tools to ensure efficient and safe use of Remote Config.
To optimize app performance and user experience, follow these recommended patterns (see Loading Strategies):
Use the following commands to manage your Remote Config template and version history through the terminal:
Get current template: Save the remote template to a local JSON file for auditing or modification.
npx -y firebase-tools@latest remoteconfig:get -o remote_config.json
Autonomous Editing & Discovery : Modify the local remote_config.json
directly. Determine the correct signal (e.g., device.country or percent) and
update the "conditions" array and "parameters" map accordingly.
MANDATORY: User Review and Verification : STOP and ask the user to verify your changes before proceeding to deployment.
Deployment Orchestration : To push changes, you must ensure the environment is configured for deployment.
{ "remoteconfig": { "template": "remote_config.json" } }
Deploy: Execute the partial deployment command
npx -y firebase-tools@latest deploy --only remoteconfig
Verification: After deployment, verify the update by listing the version history.
npx -y firebase-tools@latest remoteconfig:versions:list
The SDK provides a number of features to make your application dynamic and responsive to user segments.
In these kits
More from @firebase
Works with
Claude, Codex, Cursor & more