Remote Config
Remote config delivers key/value settings to the app via a single unauthenticated endpoint.
Endpoint: GET /wp-json/omobile/v1/config
Response:
json{
"maintenance_mode": false,
"min_supported_version": "2.1.0",
"feature_checkout_v2": true,
"support_url": "https://example.com/support"
}
Managing config — OMobile admin → Remote Config tab. Key/value pairs with type (string, boolean, number, JSON).
Feature Flags
Feature flags support per-device rollout percentages for gradual releases.
Endpoint: GET /wp-json/omobile/v1/flags?install_id=<uuid>
Response:
json{
"checkout_v2": true,
"new_onboarding": false,
"dark_mode_beta": true
}
How rollout % works: The device's install ID is hashed; the result modulo 100 is compared against the flag's rollout percentage. Same device always gets the same result (deterministic, no database per-device state).
Config Snapshots
OMobile auto-saves a config snapshot before every save. Go to Remote Config → Snapshots to view history and roll back to any previous state.
bashwp omobile config list # List all config keys
wp omobile config set key value # Set a key
wp omobile config rollback 3 # Roll back to snapshot ID 3