Best Practices

Create with intent: Always define the purpose of a flag before adding it.

Name consistently: Use clear, descriptive keys such as checkout_experiment_v2, not flag123.

Expire old flags: Remove flags once an experiment or rollout is complete.

Track ownership: Assign teams or individuals to maintain each flag.

Use different OAuth2 clients and client secrets for development, staging, and production.

Never reuse production credentials in development or testing.

Validate flag behavior in staging before rollout to production.

Send only attributes required for evaluation.

Use privateAttributes to protect sensitive fields from logs.

Define consistent context schemas across your services.

Start with percentage rollouts before enabling flags globally.

Use targeting by role, plan, or region for safer incremental launches.

Monitor errors, latency, and adoption during rollouts.

Always provide a default value when evaluating a flag.

Handle common exceptions such as FlagNotFoundException or AuthenticationException.

Configure retry options and sensible timeouts in IntelliToggleOptions.

Initialize the SDK once, early in your application lifecycle.

Use caching and polling to reduce API calls in high-throughput apps.

Prefer streaming updates where supported for near real-time flag changes.

Document the purpose of each flag in your team’s knowledge base.

Regularly review active flags to avoid clutter.

Implement naming conventions such as teamName_featureName_experiment.

Link flags to issue tracker IDs or change requests for traceability.

Add logging hooks to record flag evaluations.

Track flag decisions in analytics for feature adoption insights.

Correlate flag rollouts with monitoring dashboards.

Avoid evaluating flags directly inside widget build methods; prefer FutureBuilder or Provider.

Keep UI fallbacks simple; do not rely on flags for critical rendering paths.

Test flag variations with QA before production rollout.

Never hardcode OAuth client credentials in source code; use environment variables or secret managers.

Rotate credentials regularly.

Review Security & Privacy for more guidance.