{"id":67607,"date":"2021-07-29T11:11:27","date_gmt":"2021-07-29T10:11:27","guid":{"rendered":"https:\/\/www.prodpad.com\/?post_type=pp_resource&p=67607"},"modified":"2023-05-03T15:26:56","modified_gmt":"2023-05-03T14:26:56","slug":"feature-flag","status":"publish","type":"pp_glossary","link":"https:\/\/www.prodpad.com\/glossary\/feature-flag\/","title":{"rendered":"Feature Flag"},"content":{"rendered":"\n
\n
\n
<\/div>\n\n\n\n
\n

What is a feature flag?<\/h2>\n\n\n\n

A feature flag is an ability to turn features on and off in an application so that product teams can experiment and learn. Product teams can use feature flags to decide whether a feature is available for their users – either all users, a proportion of users, or no users. It’s a way of launching a new feature in a controlled way, in order to learn whether it works correctly “in the wild” – i.e. it is valuable and useful for the user base.<\/p>\n\n\n\n

What are the benefits of feature flags?<\/h2>\n\n\n\n

Feature flags allow for use cases where there is a need to have several different versions of the product live at the same time without impacting each other. They can co-exist peacefully on separate branches or servers, and allow the product team to test out new flows or features before deciding which one is good enough to release globally. <\/p>\n\n\n\n

Feature flags are also commonly used by large organizations when rolling out updates or changes of any kind. Instead of releasing code globally at once, these changes are only turned on one user at a time over an unspecified amount of downtime depending on your testing needs. This allows you to gather real-world user feedback before you release something globally – it’s all about reducing risk.<\/p>\n\n\n\n

They are particularly useful for product teams who wish to work in a lean way and use experimentation to discover the risks of launching a new feature or product.<\/p>\n\n\n\n

Feature flags have been used for years at companies like Google and Facebook but are only just now starting to come into their own for smaller companies.<\/p>\n\n\n

\n
\"Feature
Feature flags help with lean experimentation<\/figcaption><\/figure>\n<\/div>\n\n\n

Are there any drawbacks to feature flags?<\/h2>\n\n\n\n

There is one major drawback when it comes to using feature flags and that\u2019s scaling. Typically, you would create a branch in your code for each flag that you could turn on or off in production from the UI via the command line interface (CLI). Unfortunately, this creates an unlimited number of branches that eventually leads to chaos as any change to the existing functionality might require multiple changes across all these branches.<\/p>\n\n\n\n

How do I use feature flags?<\/h2>\n\n\n\n

Services like LaunchDarkly<\/a> have started to bring feature flagging into the cloud which makes it easy for startups and small teams to try out their code before deploying it publicly. It also allows them to collect data on certain features that they can then use as a selling point in the future or simply use as a guide on what new features to build next.<\/p>\n\n\n\n

\nBack to The Product Management Glossary<\/a>\n<\/div>\n\n\n