Define parameters
Add typed string, number, boolean, or JSON values, start from a template, or import a Firebase Remote Config file.
Remote config
Tune the live game without shipping a build.
Change rewards, feature switches, difficulty, and live event settings for the players who should see them, then publish, measure, and roll back from versioned history.
Illustrative config workspacev12 live
Overview
Audience
Messages
Delivery
Settings
Live workspace
starter_coins
Default
100Conditions
03Environment
ProductionCurrent flow
RamadanHijri month 9 · 200
QA phonesTest devices · 500
Rollout slice10% of players · 150
Example data for product illustration. Not customer performance.
Every live value deserves a version history.
Drafts, reviewed diffs, immutable versions, and rollbacks that never rewrite history let LiveOps move quickly while engineering can see exactly what changed and when.
How it works
From a draft value to every eligible device.
Target conditions
Match app version, OS, locale, country, time zone, test devices, a sticky percentage, a time window, or Hijri dates.
Review and publish
Compare the draft with the live version, publish now or schedule it, and optionally ask devices to refresh.
Measure and recover
Watch version adoption, experiment on values, and roll back to any earlier version as a new release.
Capability depth without the fine-print surprise.
Current and planned capabilities are labeled directly, so teams can evaluate PushHub without confusing vision for availability.
Versioned publishing
Edit one draft per environment, review the diff, publish now or on a schedule, and roll back without rewriting history.
Targeting and rollout
Combine device context, custom properties, test devices, sticky percentage slices, time windows, and Umm al-Qura Hijri dates.
Experiments and player overrides
Test parameter values against a goal event, or set one player's value from the dashboard, the API, or an event trigger.
Client SDKs, instant refresh, and signing
The Android SDK (Beta) and the JavaScript SDK (Preview) support instant refresh and signed responses. Engine SDKs are Preview on Android, and iOS support arrives with the next iOS SDK release.
In the game
Live changes players feel, without a store review.
Seasonal tuning
Raise rewards for Ramadan or Eid with Hijri date conditions evaluated in each player's time zone.
Safe feature launch
Add a kill switch, try the feature on QA phones, then widen a sticky rollout from 1 to 100 percent.
Maintenance and minimum version
Show a maintenance message during a time window, or ask players below a supported version to update.
Economy experiment
Compare starter coin values against purchases, then roll the winning value into the draft.
Fast changes still need guardrails.
Environments keep debug builds away from production values, roles decide who can publish, and every publish, schedule, rollback, override, and refresh is recorded in the audit log.
Environment isolation
A device reads the environment of the key it registered with, so development builds never fetch production config.
Immutable history
Published versions never change. A rollback republishes an earlier template as a new version.
Offline-safe values
The SDK starts from in-app defaults and keeps the last activated values, so a failed fetch leaves the game's current config in place.
Questions teams ask before they commit.
The native Android SDK is Beta and verified on devices. The JavaScript SDK is Preview, tested in CI and in a browser. Unity, Flutter, React Native, Godot, and Unreal are Preview on Android. iOS remote config arrives with the next iOS SDK release.
Build the next player return.
Start with one app, one meaningful moment, and one audience worth reaching.