aboutsummaryrefslogtreecommitdiff
path: root/_articles/2020-10-14-feature-flags-differences-between-backend-frontent-and-mobile.md
diff options
context:
space:
mode:
Diffstat (limited to '_articles/2020-10-14-feature-flags-differences-between-backend-frontent-and-mobile.md')
-rw-r--r--_articles/2020-10-14-feature-flags-differences-between-backend-frontent-and-mobile.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/_articles/2020-10-14-feature-flags-differences-between-backend-frontent-and-mobile.md b/_articles/2020-10-14-feature-flags-differences-between-backend-frontent-and-mobile.md
index 8b3b97a..c93ddd4 100644
--- a/_articles/2020-10-14-feature-flags-differences-between-backend-frontent-and-mobile.md
+++ b/_articles/2020-10-14-feature-flags-differences-between-backend-frontent-and-mobile.md
@@ -247,4 +247,5 @@ deleting/retiring a feature flags at the end of the development.
### Always rely on a feature flag on the app
Again, there is no such thing "too small for a feature flag". Too many feature
-flags is a good problem to have, not the opposite.
+flags is a good problem to have, not the opposite. Automate the process of
+creating a feature flag to lower its cost.