Angular Feature Flags User
Use Cases and Deployment Scope
Angular Feature Flags are being used in our newly re-written internal staff portal application. We are in the process of porting over each section of the portal into the new code base. Different teams are coding and responsible for different domains and each section of the staff portal is a window into that domain. We have the ability through the use of a custom route guard to disable navigation to any subsection of the portal. Each subsection is treated as a feature essentially and allows us to develop the portal with a less complex branching strategy as a result of Feature Flags disabling access to certain areas of the app. Otherwise each feature area would have to be developed in a different git branch and there's enough overlap between domains and use of shared code which would make that branching strategy much more complex and unwieldly.
Pros
- Allows for easy configuration of what you may define as features
- Allows for a customization layer to utilize Feature Flags
Cons
- Would be nice if there were a built in route guard and more end to end solution out of the box I suppose
Likelihood to Recommend
Feature Flags are well suited for apps which are being developed across numerous teams in order to extend and basically enable/disable whatever areas of the app you want. It's not really necessary for an individual developer or perhaps even a single team of developers, depending.
