Remote Config

Remote Config lets you control your app's behavior from the server without releasing an update. Use it for feature flags, pricing experiments, onboarding flows, and more.

Overview

Remote Config values are resolved per-user based on targeting conditions. The server evaluates rules and returns the resolved values for the current user.

Fetching Config

iOS

// Config is resolved server-side based on the authenticated app context.
// Platform/appVersion/country are inferred by the SDK.
let configs = try await AppActor.shared.loadRemoteConfigs()
print("Loaded config items: \(configs.items.count)")

// Access typed values
if AppActor.shared.getRemoteConfigBool("show_holiday_banner") == true {
  showHolidayBanner()
}

if let maxRetries = AppActor.shared.getRemoteConfigInt("max_upload_retries") {
  setMaxRetries(maxRetries)
}

// Read raw value if needed
if let raw = AppActor.shared.getRemoteConfig("welcome_message") {
  print(raw)
}

// Last loaded snapshot (no network call)
if let cached = AppActor.shared.cachedRemoteConfigs {
  print("Cached items: \(cached.items.count)")
}

Android

Coming Soon

Android SDK is currently in development.

Flutter

Coming Soon

Flutter SDK is currently in development.

React Native

Coming Soon

React Native SDK is currently in development.

Targeting Conditions

Config values can be targeted based on:

Condition	Operators	Example
Platform	eq, neq, in, not_in	Only show on iOS
App Version	eq, gt, gte, lt, lte	Enable for v2.1.0+
Country	eq, neq, in, not_in	Different config for US vs EU
Entitlement	has, not_has	Show upsell only to free users

Example Rules

[
  {
    "type": "country",
    "op": "in",
    "value": ["US", "CA", "GB"]
  },
  {
    "type": "app_version",
    "op": "gte",
    "value": "2.0.0"
  },
  {
    "type": "entitlement",
    "op": "not_has",
    "value": "premium"
  }
]

This config value would only be returned for users in US/CA/GB, running app version 2.0.0 or later, who do not have the "premium" entitlement.

REST API

Request

GET /v1/remote-config
Authorization: Bearer pk_live_your_key_here

Query Parameters:

Parameter	Required	Description
app_user_id	No	User ID for entitlement-based targeting
app_version	No	App version (e.g., "2.1.0")
country	No	ISO 3166-1 alpha-2 code (e.g., "US")

Platform is derived from the authenticated app context (your API key is tied to a platform).

Response

{
  "data": [
    {
      "key": "show_holiday_banner",
      "value": true,
      "valueType": "boolean"
    },
    {
      "key": "max_upload_retries",
      "value": 5,
      "valueType": "number"
    },
    {
      "key": "welcome_message",
      "value": "Happy holidays!",
      "valueType": "string"
    }
  ],
  "requestId": "req_abc123"
}

Caching

The response includes cache headers:

Cache-Control: private, max-age=900
ETag: W/"abc123"

The SDK caches config values and uses ETags to avoid unnecessary data transfer. A 304 Not Modified response means the cached values are still valid.

Next Steps

• Experiments — A/B test different config values