Feature toggles are one of the most relevant mechanisms used to modify features in real-time without changing code. Developers can test different changes on a specific group of users before making them available to everyone, being essential in mitigating risks.
This article will provide an overview of how you can benefit from using a feature toggle and how you can implement it into your development or production environments.
What is a feature toggle?
It is a strategy that allows us to enable and disable resources and functionalities in our system in real-time without any changes on the published codebase.
Feature toggles allow defining whether or not such a feature should be connected in real-time, allowing Software Engineering Teams to release a new version of the application more continuously and connect resources and functionalities only when desired.
How to implement a feature toggle?
These two different options can be considered:
API: exposing an endpoint that controls all features and if they are enabled or disabled;
Frameworks: using frameworks like Firebase or Split to manage the features.
Actually did take a look at Theshortcutts.com a few times when researching the post. Unfortunately, Matt Cutts doesn’t spill the beans very often in his videos. To get this kind of info I had to do some digging, make a few phone calls, and bribe a few people. But it was worth it 🙂
Hey Brian, great reference guide — definitely my new go-to when people ask what to do for on-page.