Angular Feature Flags vs. Optimizely Feature Experimentation

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.

Incentivized

Based on my experience with Optimizely Feature Experimentation, I can highlight several scenarios where it excels and a few where it may be less suitable. Well-suited scenarios: - Multi-Channel product launches - Complex A/B testing and feature flag management - Gradual rollout and risk mitigation Less suited scenarios: - Simple A/B tests (their Web Experimentation product is probably better for that) - Non-technical team usage -

Incentivized

• Allows for easy configuration of what you may define as features
• Allows for a customization layer to utilize Feature Flags

Incentivized

• Splitting traffic between variants and enabling you to scale up or down the amount of traffic in each one
• Giving a standardised report that you can share with a huge number of users
• Showing a large variety of results/metrics you can then dive into

Incentivized

• Would be nice if there were a built in route guard and more end to end solution out of the box I suppose

Incentivized

• Difficult integration if your data is not front end
• Costly MAU model needs to be based on experiments not on site visits
• It's not easy to understand how to build an Experiment
• Onboarding team is more focused on punching through their slides and not focused on your needs or understanding.

Incentivized

Competitive landscape

Incentivized

Easy to navigate the UI. Once you know how to use it, it is very easy to run experiments. And when the experiment is setup, the SDK code variables are generated and available for developers to use immediately so they can quickly build the experiment code

Incentivized

Support was there but it was pretty slow at most times. Only after escalation was support really given to our teams

Incentivized

It’s straightforward. Docs are well written and I believe there must be a support. But we haven’t used it

Incentivized

We still utilize Git as our source control system but Feature Flags allow us to use Git in a less complex and more efficient way for our development needs.

Incentivized

In previous companies I've used Monetate which is a similar A/B testing kind of feature experimentation engine that is very similar from my memory, but again, back to the point of these new features of the analytics engine and Opal, it kind of cuts it above Monetate from my experience. Obviously Monetate may have improved since when I lost use it, but from what I can see, yeah.

Incentivized

had troubles with performance for SSR and the React SDK

Incentivized

• 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.

Incentivized

• We have a huge, noteworthy ROI case study of how we did a SaaS onboarding revamp early this year. Our A/B test on a guided setup flow improved activation rates by 20 percent, which translated to over $1.2m in retained ARR.

Incentivized