Overall Satisfaction with Angular Feature Flags
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.
- I would say a large ROI considering the reduction in branching and merging we need to perform and also the ability to use common, up to date code across teams. There's a lot of shared code we make use of, particularly with identity and authentication and our entire identity platform which is essentially used by each feature.
Do you think Angular Feature Flags delivers good value for the price?
Are you happy with Angular Feature Flags's feature set?
Did Angular Feature Flags live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Angular Feature Flags go as expected?
Would you buy Angular Feature Flags again?
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.