Values that change without releasing.
WHAT REMOTE CONFIGURATION PROVIDES
Values fetched at runtime, changed without a release.
WHY THAT MATTERS ON MOBILE
Releases take days to reach users, and some never update.
WHAT TO USE IT FOR
Feature flags, enabling and disabling features Endpoint addresses Thresholds and limits Messages shown to users Minimum supported version enforcement
WHY FEATURE FLAGS MATTER MOST
A feature causing problems can be disabled without a release.
WHAT THAT PROVIDES
The ability to recover from a defect in hours rather than weeks.
WHAT TO ALWAYS PROVIDE
Sensible defaults, used when configuration cannot be fetched.
WHY
The first launch may be offline.
WHAT TO BE CAREFUL WITH
Flags accumulating and never being removed Configuration that changes behaviour in untested combinations Trusting remote values without validation
WHAT TO REMOVE
Flags for features fully released.
WHAT TO NEVER PUT IN CONFIGURATION
Secrets.
WHY
They are delivered to the device and are readable.
WHAT TO TEST
Behaviour with each flag in each state.
