LaunchDarkly Reviews

We use the solution for risk-free releases, allowing us to control the blast radius when launching content to our customers. We also use it for targeted experiences, enabling us to reach specific customer segments with various features as they are rolled out. However, the company's main use case was extensive A/B testing to conduct experiments.

The application is highly intuitive. The UI offers robust controls, allowing you to set rules, schedule releases, and establish dependencies. For instance, if a particular flag depends on other flags or features that need to be deployed first, you can also configure that. The application provides a deep level of configuration options.

We built a powerful e-commerce platform and heavily used LaunchDarkly to launch features behind a flag. This allowed us to implement trunk-based development, significantly improving our development speed. We could continuously deploy everything behind a flag and enable features only when ready, which was incredibly helpful.

There are certain features we need to keep behind a flag. Typically, there are two ways to do this: using a property file or using LaunchDarkly. With property files, we had to deploy the feature in a lower environment, update the property, and then restart the server. 

LaunchDarkly, on the other hand, offers real-time changes and the ability to disable features if issues arise in production. This real-time capability is extremely beneficial.

Targeting rules have improved our deployment process. 

Our deployment process has become much faster. We are able to keep rolling out to production even if a feature isn't fully ready. We simply don't enable it until it's complete. LaunchDarkly also helps with certain business use cases that require time-sensitive run-time decisions.

For instance, during validation processes, both conditions need to be met, but the upstream system isn't ready. We can still provide support and, in the future, transition smoothly.

Imagine a scenario where you need to accept both five-digit and ten-digit order numbers, but your system isn't ready for ten-digit numbers yet. LaunchDarkly allows you to support both initially and then, when all other services are ready, enable the ten-digit feature. This makes the rollout seamless.

We use LaunchDarkly for managing feature flags. It helps manage the keys to control what users view on our screens.

By managing the feature flags, we can target users and control what needs to be visible on their screens.

Our developers are using LaunchDarkly. I am using it to turn on features.

Recently, I like this new update where we can see and manage everything through it. Also, from the development side, it allows us to manage multiple things. Additionally, I like the services provided, like managing through the internet on and off.

I have been working for the client Windstream, which is an enterprise platform where we develop an Appysuit application. We are testing new features without releasing them to all customers, instead releasing to selected customers. I use LaunchDarkly for feature enabling and disabling.

The main feature I value is the user-friendliness, especially the flag enabling and disabling. The API integration is also impressive. I appreciate the UI which allows easy enabling and disabling of flags.

LaunchDarkly is used for feature flag implementation. It allows me to control product release by deciding whether to show certain features to users. I can also control feature visibility remotely by toggling flag values.

LaunchDarkly helps avoid complete rollbacks when multiple features are released, and one causes an issue. We can simply turn off the problematic feature, saving on redeployment and testing cycles.

I have been using LaunchDarkly for more than one year due to the nature of my projects. Whenever we want to avoid multiple builds, we use a flag to enable future changes in the production environment.

LaunchDarkly allows us to control deployments without multiple builds. It enables us to show the status of tasks to clients when necessary, and when a task is not complete, we can prevent it from being visible by turning off the flag.