LaunchDarkly vs. Split

If a new feature should be added but unsure of how it will actually work or how users will accept the new enhancement or change, this tool allows you test and measure initial results. This saves so much time and energy knowing the results before it is deployed and might have low user adoption or acceptance.

Incentivized

• A/B or Multi Variant Testing as a methodology to gather insight from customer usage. Experimentation as a feature within LaunchDarkly offers information around the success of one variant over another and whether the experiment has reached statistical significance.
• Being able to decouple deployment of code from the release of a feature is hugely valuable.
• Development teams are empowered to manage features within their production applications for reliability or testing purposes.

Incentivized

• Limited number of users on cheaper plans that is limiting our ability to audit log who is making changes.
• Some of our engineers are confused between flags and segments and have set up items incorrectly.
• Better documented support for React with Typescript.

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

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

LaunchDarkly stood out to us because it put control of the application within the hands of our engineers. We didn't want to allow business users to manipulate the production site via a third-party tool. Instead, our focus was on delivering faster as an engineering team.

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