Control feature behavior without coupling every change to an app release.
1. Configuration defaults
Provide safe bundled defaults when Remote Config cannot fetch. Validate retrieved values against an allowlist so a bad parameter cannot choose arbitrary endpoints or unsupported models.
2. Versioned prompts
Treat prompt templates as versioned behavior. Associate evaluation results with each version and stage a rollout. A remote prompt edit can be as consequential as a code change.
3. Kill switch and fallback
An off switch should stop new inference work and expose the manual flow. Define what happens to in-flight requests and cached results when the feature is disabled.
Worked scenario
A misconfigured model name is fetched remotely. Validation selects the known bundled default and emits a diagnostic rather than crashing the screen.
Apply it
Implement enabled, model and prompt-version configuration. Test no network, invalid values and a feature disable during a request.
Check your understanding
The app has useful behavior when remote configuration and inference are both unavailable. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.