LaunchDarkly Reviews and Ratings

Use Cases and Deployment Scope

LaunchDarkly is a very good product, basically we use the feature flag from LaunchDarkly in implementing the feature driven software development at our organization. It is easy to use and delivers the best services. With use of LaunchDarkly we are able to manage the new feature development very effectively. It helps you in creating one code branch and use it with feature flag, that's how it improves the team productivity.

Likelihood to Recommend

LaunchDarkly is good in terms of feature flag management, it helps in driving the test and feature driven software applications. Feature flags are more effective in terms of managing our code base in many environments like locally, staging and production. Monitoring is good. But we need some notification based alerts while dealing with production environment.

Use Cases and Deployment Scope

LaunchDarkly is used for maintaining feature toggles for our production services. We have been using it for a year now and haven't had any issues so far. We have a toggle framework that abstracts away the complexity of Launch Darkly so we don’t actually interact with it directly. LaunchDarkly provides a clear insight into the state of your toggles in production.

Likelihood to Recommend

Suitable for feature toggle management at scale. It can be used to run A/B tests for your services. If your application or service only has a few simple feature toggles, then this is not the framework for you and you are better off using your own custom toggle management system.

Use Cases and Deployment Scope

We use LaunchDarkly to help hide incomplete features from end users. This allows us to deploy code to production more often, which reduces code conflicts and leads to a healthier codebase

Likelihood to Recommend

LaunchDarkly is great when you need to deploy frequently for teams that are experiencing growing pains because there are more and more developers beginning to contribute to the same code base. It is less important when you have very few users or very few developers. It is also less important when you deploy infrequently, because you are more likely to deploy fully complete and tested code to production in that case

Use Cases and Deployment Scope

We currently use it in a couple of ways:

1. Use for configuration values that are shared across multiple applications

2. Feature Flagging for new features can deploy and test while still being developed.

3. Used it as a feature kill switch if we need to disable a feature during peak traffic/season.

Likelihood to Recommend

1. It is not too hard to do LaunchDarkly if you need feature flags and scaling rollout. However, IF you have CDN in front of your application, it gets interesting.

2. Sharing configuration across multiple applications makes it easy.

3. Using it as a kill switch for components on your site, you can disable it during peak seasons (e.g. Black Friday) to improve the performance and stability of your site.

Use Cases and Deployment Scope

While LaunchDarkly delivers a huge set of features, we use it mainly as an environment. Our CI/CD pipelines push our code straight to live, with our new features encapsulated in a LaunchDarkly toggle. That gives us huge control over what can be seen on live without the overhead of having to mimic a live environment on staging.

Likelihood to Recommend

We found that it helps a lot with our CI/CD processes, helps with our time to market, and allows us to show progress in an easier way. We feel that it suits what we do perfectly. The only downside is the very high cost which makes all senior staff wonder about ROI. Apart from that, it's all good

Use Cases and Deployment Scope

We predominantly use LaunchDarkly to facilitate our Trunk Based / Continuous Deployment workflow, enabling us to deploy multiple times a day and target specific user segments. We also use it to run UI experiments that help us determine the optimal customer experience.

Likelihood to Recommend

It's hard to imagine building applications without LaunchDarkly - it's become an integral part of our deployment process. The frequency with which we can deliver to production wouldn't be possible without it. I highly recommend LaunchDarkly for any professional engineering team who wants to deploy often and simultaneously minimise risk.

Use Cases and Deployment Scope

Ours is a provider-facing application. We were needing a tool that could toggle between features that providers get to see. And on that search, we landed on LaunchDarkly for feature toggle management. One of the best tools that fit our use case. The ease of use is very straightforward. The support team is excellent in providing immediate support while setting up the tool and during development. I would highly recommend this for any organization that needs a feature toggle use cases. We currently use this tool across our organization.

Likelihood to Recommend

The best scenario is wherein you create a feature and would like to test it before it goes to production. You make use of feature toggles in lower environments, test them out thoroughly without impacting other features. Once verified, you may then publish the same to PROD environment for feature to be enabled.

Use Cases and Deployment Scope

We use LaunchDarkly to control features in our authenticated web and mobile applications. It allows us to test features in production, gradually rollout new features to users & gather feedback, and disable new features if there is a problem. We are currently using it in one department, but other departments have seen our success and are working on their own POCs.

Likelihood to Recommend

LaunchDarkly is well suited for any runtime decisioning within an application. This can be automated based on rules or manual. It's also a great way to separate business logic from application logic.

Use Cases and Deployment Scope

LaunchDarkly is being used by our Technology department to continuously deliver code that is off in production - customers are not impacted by code delivery. Their workflow is not interrupted. We then schedule when the code will be enabled and prepare our customers for the changes. This allows our Technology teams to continue to work without slowing down their schedule for our customers, who like more time to prepare for changes.

Likelihood to Recommend

It is a good fit for our company. Does exactly what we need.

Easy to teach, our teams quickly picked up how to add the code for feature flags.

Having the ability to schedule feature enablement has been very useful for our company.

Easy to teach even non-technical people how to use the tool.

Very user friendly UI.

Use Cases and Deployment Scope

We use LaunchDarkly to separate the Deploy and Release aspects of changes. The R&D team implements LaunchDarkly flags in code, and then by using the user targeting functionality the QA team can validate the changes with the flag on and off. The main point is testing with the flag off, as this means that the master can be deployed to production at any point with the flag remaining off, so we don't have to worry about breaking existing functionality by using these flags.

Likelihood to Recommend

It is well suited when you are making changes in areas that are already being used and do not want to impact existing customers in any way. Being able to hide all new code behind a flag means your master branch can be deployed even when your new code is not fully finished. It also means you can focus on testing when the flag is off and almost ignore when the flag is on to ensure the master is production-ready.