LaunchDarkly vs. Statsig

Great for rolling out features slowly for beta testing in production. I would say it is less well suited for toggling features permanently for users as this requires more integration with our backend and billing systems that would be a lot of work to set up.

Incentivized

Statsig is well suited for running straightforward a/b tests on frontend deployments. We've actually used it to log events on our backend and used the HTTP API to integrate with tools like Hubspot to evaluate email campaigns

Incentivized

• Feature Flag Management: It's like magic. With a flip of a switch, you can manage feature rollouts to visitors or accounts across the web and mobile applications!
• Segmentation: Create a segment of visitors or accounts and then use that to target a feature flag rule. Really easy to use and saves so much time.
• Ease of Use: Seamless copy/paste functionality, really clear status indicators so you can find what is on and for whom.

Incentivized

• Clear experimentation insights and details
• Experimentation health and performance ratings
• Statistical analysis of in flight work

Incentivized

• It would be nice to see a feature flag's settings against all environments at once.
• It would be to have a "array" type flag for related but different settings (eg, enableA and enableB could be enable: [a, b]).
• It would be nice have customizable columns on the Users page (eg, if I want to inject a new meta data).

Incentivized

• Complex data science focussed UI

Incentivized

It fits out business case

Incentivized

It's very easy to create new feature flags and set them properly. It is more difficult to get LaunchDarkly integrated within a distributed system so that flags can be used. Especially on stateless servers where gating features by user is not easy. Overall though, it is very easy to get started and I like how simple it is to use.

Incentivized

For the most part it is pretty easy to use. - There are some quirks with the javascript SDK (getExperiment().getValue?). - The Events vs. Metrics design pattern is complex, and creating new Metrics from Events can be frustrating if you are trying to use event metadata - It's really frustrating not to be able to link Static IDs (before a user signs up) to User IDs, in order to follow users all the way through onboarding, or to log events that occur for signed in users when you are exposing the experiment to users before they've signed up

Incentivized

No issue with availability at all

Incentivized

From what I have seen, LaunchDarkly integrates well with your code and also services you might have in your tech ecosystem. We use Jenkins for automation and we were able to use it to build pipelines to automate the control of LaunchDarkly toggles in our code.

Incentivized

The overall support is very responsive

Incentivized

Yes I do.

Incentivized

Rollout is another dedicated feature flag tool that can be used to manage features. LaunchDarkley offers all the features of an enterprise level tool, unlike Rollout, reserves the security features for the Enterprise plan. Out of box integrations are limited but they do have a well documented REST API.

Incentivized

Incentivized

The platform didn't go down since we implemented it

Incentivized

• Improved developer experience with some teams moving to Trunk-based Development.
• Increased deployment frequency due to smaller code releases.
• Validation of the technical and business value of work is achieved more quickly through smaller pieces of work and through experimenting with a small group of users before a feature gets to 100% of customers.

Incentivized

• We uncovered several feature releases that were causing a negative impact on our product activation rate by running exclusion experiments

Incentivized