Release is live, build in the stores — and you realize you want to tweak the balance: increase resource cost, lower boss damage, adjust spawn frequency. Without Remote Config this means a week-long cycle: patch, Apple/Google review, waiting. With it — edit a value in the console and instantly apply it to the right segment of players. Average delivery time for changes is 1–2 seconds after publishing. Over 8 years working on gamedev projects, we've implemented Remote Config in more than 20 games, from hyper-casual to RPG. Patch time savings — up to 90%, QA cost reduction for A/B tests — up to 60%. Our experienced team guarantees a smooth integration.
Firebase Remote Config — not just a key-value store. A well-designed parameter schema turns it into a full-fledged A/B testing and Managed Rollout tool. According to the documentation, default caching is 12 hours. Remote Config is 10x faster than traditional patching.
Why is Remote Config critical for live-ops?
A typical mistake in self-integration — putting all parameters into one Default Config without structure. After three months of active balance work, the Firebase console accumulates 80+ parameters with names like enemy_dmg_2, enemy_dmg_2_new, enemy_dmg_final. No namespacing, no documentation, parameters duplicate. In 95% of beginner projects we find this issue.
Second problem — ignoring the cache. remoteConfig.fetchAndActivate() caches values for 12 hours by default. In production that's fine, but in development mode the team loses hours not understanding why console changes don't apply. The minimum interval for dev environment is set via remoteConfig.settings.minimumFetchIntervalMillis = 0, and this must be done using #if DEVELOPMENT flags, not forgotten before release.
Third — lack of fallback values on the client. If Remote Config is unavailable (offline, network error), the game should work with embedded defaults, not crash or return zero balance values.
How to design the parameter schema?
For a mid-sized mobile game with several unit classes and several game modes, a JSON structure inside a single parameter is optimal instead of a hundred flat keys. One parameter balance_config contains JSON with nested structure:
{
"enemies": {
"goblin": { "hp": 120, "dmg": 15, "spawn_weight": 0.4 },
"troll": { "hp": 400, "dmg": 35, "spawn_weight": 0.1 }
},
"economy": {
"coin_multiplier": 1.2,
"ad_reward_gems": 10
}
}
On the client, JSON is parsed once at session start and placed into a ScriptableObject or static config class. This is more convenient than 40 separate remoteConfig.GetValue("key") calls.
Conditions and personalization. Firebase Remote Config supports conditions by platform, app version, audience (via Firebase Analytics), country. Typical scenario: parameter first_purchase_bonus returns 50 for new users (audience new_user in Analytics) and 20 for others. This is not an A/B test — it's segmented configuration, and it's set without client code changes.
A/B tests via Remote Config. Google Optimize is deprecated, Firebase A/B Testing is natively integrated. Create an experiment directly in the console: variant A — spawn_interval: 8.0, variant B — spawn_interval: 5.0, metric — D1 retention. 50/50 split, run on 10% of the audience. Client code doesn't know about the experiment — it just reads the spawn_interval parameter. Our certified Firebase professionals ensure accurate setup.
How does Managed Rollout work?
Managed Rollout — gradual configuration rollout: first to 1% of the audience, then increase to 5, 20, 50, 100%. If at any stage metrics (retention, revenue, crash rate) drop, automatic rollback to the previous stable version occurs. This reduces the risk of bad settings and allows safe experimentation even with critical balance parameters.
What tools do we use?
On Unity projects we use Firebase Unity SDK 11.x. Initialization is asynchronous — we wait for FirebaseApp.CheckAndFixDependenciesAsync() before the first fetch. On Unreal projects, Firebase Remote Config is available via C++ SDK or the FirebaseFeatures plugin (Epic Marketplace).
For games on a custom server instead of Firebase, we set up GrowthBook or a custom solution on Redis + API: parameters stored in Redis with TTL, client fetches them via REST at session start, fallback — embedded JSON file in the build.
Work stages
- Audit current hardcoded values — find values in the project that should be configurable. Usually unit balance, economy parameters, feature flags, ad display intervals. Patch time savings — up to 90%.
- Schema design — parameter namespacing, JSON vs flat keys, config versioning.
- SDK integration — proper initialization, offline handling, dev/prod config intervals.
- Conditions and audiences setup — connect to Firebase Analytics for segmentation.
- A/B test pilot — configure first experiment, check events in DebugView.
- Schema documentation — parameter table with description, value ranges, owner (gamedesigner/programmer).
What is included in the result
Deliverables breakdown
| Component | Description |
|---|---|
| Parameter schema | JSON structure with namespacing, versioning, and fallback values |
| SDK integration | Correct initialization, offline handling, dev/prod configs |
| Conditions setup | Segmentation by country, version, Analytics audience |
| A/B experiment | Pilot test with retention/purchase metric |
| Documentation | Parameter table with owners, ranges |
| Access to Firebase project | Console setup and permissions |
| Training session | 2-hour online session for your team |
| Support | Consulting for 2 weeks after implementation |
| Task scale | Timeline |
|---|---|
| Remote Config integration into an existing project (up to 30 parameters) | 2–4 days |
| Schema design + integration + first A/B test | 1–2 weeks |
| Full system with segmentation, experiments, and documentation | 3–5 weeks |
Pricing is calculated individually after project analysis and current architecture review. Typical cost: $1,500 – $3,000 for a full setup. On average, clients save $5,000 in development time per month. Guaranteed 30-day satisfaction or full refund.
Common mistake: hardcoded value duplication. If there is already partial Remote Config integration, we often find: parameters duplicate hardcoded values in code (Remote Config value is ignored due to a typo in the key), conditions in console are misconfigured (audience percentage doesn't sum to 100), A/B test metrics are not pushed to Analytics. Fixing accumulated chaos takes longer than building a schema from scratch.
Contact us to assess your project. Request a consultation on Remote Config integration — our engineers will analyze the code and propose the optimal schema. Our Remote Config setup for games includes A/B testing and parameter management.