3 ms·
Mobile app case here: The app fetches its base configuration first from a known URL, before even loading anything except for the most essential parts. This is
by theshrike79 5y ago
Mobile app case here:
The app fetches its base configuration first from a known URL, before even loading anything except for the most essential parts.
This is where we can disable the most basic level of operations or do an emergency shutdown of the client (backend broken or front end exploit found for example)
Second level is a version-specific configuration, which can be used to disable all major features of the application.
Then there is a system that allows for A-B -testing of features on a client, which can also be used to completely turn off features. It's mostly used to slowly roll out features on the client that might stress the backend in unexpected ways if enabled in one go.
The A-B tests are either moved to the second level config feature flags, or permanently turned on or off in a subsequent release.