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

• It is easy to use any of our product owners, marketers, developers can set up experiments and roll them out with some developer support. So the key thing there is this front end UI easy to use and maybe this will come later, but the new features such as Opal and the analytics or database centric engine is something we're interested in as well.

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

• Would be nice to able to switch variants between say an MVT to a 50:50 if one of the variants is not performing very well quickly and effectively so can still use the standardised report
• Interface can feel very bare bones/not very many graphs or visuals, which other providers have to make it a bit more engaging
• Doesn't show easily what each variant that is live looks like, so can be hard to remember what is actually being shown in each test

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

When Google Optimize goes off we searched for a tool where you can be sure to get a good GA4 implementation and easy to use for IT team and product team. Optimizely Feature Experimentation seems to have a good balance between pricing and capabilities. If you are searching for an experimentation tool and personalization all in one... then maybe these comparison change and Optimizely turns to expensive. In the same way... if you want a server side solution. For us, it will be a challenge in the following years

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