// problem · rebuild tax
Every typo costs you two weeks of review.
A wrong drop rate, a broken French string, a price that should have been $1.99 instead of $19.99 - none of these should require Apple's review queue. But without remote config and live localization, they do. Players churn while you wait.
// without KalmForge
- Tweaking a number means a new build and 1–2 weeks of review.
- Translation fixes ship with the next release. Maybe.
- Seasonal events require coordinating a release window.
- Store catalog changes are locked to release cycles.
// with KalmForge
- Push a remote-config value. Live on the next session.
- Edit the string in the dashboard. Players see the fix immediately.
- Schedule live events with start/end windows, no rebuild.
- Author IAP bundles and offers as data; update on demand.
// how it works
The mechanics
01
Remote Config
Feature flags, balance values, version gates - rolled out to cohorts with safe defaults if the network is down.
Read the doc →02
Localization
20+ languages, AI-assisted translation, CSV import/export. Strings update without a build.
Read the doc →03
Live Events
Define limited-time events with start/end windows. The SDK reads them at session start.
Read the doc →// what changes
Real outcomes
- Critical fixes go live in minutes, not weeks.
- No more 'wait for the next release' for content edits.
- Designers iterate on tuning live without engineering involvement.
- Seasonal events ship on calendar, not on review queues.
// questions
FAQ
- What happens if the player is offline?
- The SDK caches the last known config and serves it locally. You define the safe defaults.
- Can I roll out gradually?
- Yes. Define cohorts and roll values out to a percentage before going to 100%.
- Is there an audit log?
- Every config change is timestamped and attributed to the editor in the dashboard.
Stop stitching. Start shipping.
14-day free trial. Full Studio-tier access. No card required.
Start free trial