TrustRadius Insights for LaunchDarkly are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Business Problems Solved
LaunchDarkly is a versatile software that has been utilized by a variety of users to tackle different challenges and improve their development processes. One of the primary use cases is implementing and testing features without full deployment, which reduces risk and increases user acceptance. Users have found that LaunchDarkly allows them to address individual problems by introducing new features and ensuring they meet needs and resolve issues. By hiding incomplete features from end users, the software enables more frequent code deployment, reducing code conflicts.
Another common use case for LaunchDarkly is facilitating Trunk Based / Continuous Deployment workflows and targeting specific user segments. Users rely on the software to run UI experiments and determine the optimal customer experience. It has been particularly valuable for software development teams in managing released features in customer-facing products. Feature flags are used to hide large feature sets until they are complete, documented, and ready for customer use. Additionally, LaunchDarkly enables the rollout of new code variants and passing new features to a limited number of users before a full release, thanks to its ability to set up targeting based on different values.
Despite its wide-ranging benefits, some users have mentioned that the limited number of seats for engineers has slowed down the adoption of LaunchDarkly. However, those who have integrated it into their workflows have observed significant improvements in their product development process. The software has allowed development teams to deploy code faster and with more confidence, ultimately improving quality standards by enabling selective feature rollouts to internal testing accounts before broader releases.
In addition, LaunchDarkly has proved invaluable for feature flagging, testing, and hiding of features, allowing for constant deploys without affecting production systems. It ensures stability during structural changes and enables effective management of feature rollouts across different teams or platforms. Testing features in production has been beneficial for identifying issues that may not have been caught in QA. Furthermore, LaunchDarkly serves as an environment for CI/CD pipelines, providing control over what is seen live without mimicking a live environment on staging.
Notably, LaunchDarkly's ease of use has been widely appreciated by users, contributing to improved team productivity. The software allows for controlled rollouts to different user groups and helps manage new feature development effectively. With its ability to speed up time to delivery by deploying changes behind feature flags until ready for customer exposure, engineers have found it to be an invaluable tool. Feature flags also allow for showing specific customers specific features, further enhancing the flexibility provided by LaunchDarkly.
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.
Pros
Easy to use
Feature flag management is very helpful.
Integration with other products.
Cons
Add more security features when we deal with production code.
Focus more on testing part for API
We need a facility to use common feature flag with the team, when same code has to be deployed. We need that smooth duality while moving the code to production.
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.
VU
Verified User
Professional in Engineering (Information Technology & Services company, 1001-5000 employees)
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.
Pros
Easy automated way to flip the state of a toggle in production.
Easy access to the state of a toggle in production.
Ability to run A/B tests using a toggle in production.
Cons
The framework needs to support an easy way to remove toggles in the code and 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.
VU
Verified User
Manager in Engineering (Computer Software company, 1001-5000 employees)
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
Pros
Separate Flags by Deployment Environment
target specific users or user groups with flags
allows us to subscribe to changes in feature flags while a session is ongoing
Cons
better splitting by user group
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
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.
Pros
Feature toggling
A/B
User segmentation
Cons
NodeJS SDK is very poor
Way less logging in NodeJS than in C# SDKs
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
VU
Verified User
Team Lead in Engineering (Gambling & Casinos company, 1001-5000 employees)
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.
Pros
Feature management
A/B and multivariate testing
Segmentation
Cons
More support for Edge-side solutions
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.
We are building a new customer-facing platform that spans all products in the company and has multiple teams working on features. LaunchDarkly allows us to manage our rollout of new features by different teams so they can be deployed independently and slowly released to the interested beta users. Having features wrapped in flags has allowed us to test in production before anyone sees it. This has allowed us to find issues that we could not have seen with QA data.
Pros
Easy to implement by engineers.
Easy to set up flags.
Segments that allow us to group users to easily open up new features to a select set.
Cons
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.
Likelihood to Recommend
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.
VU
Verified User
Manager in Engineering (Marketing & Advertising company, 51-200 employees)
We are using it in my department as a part of deploying and releasing chat application features. We are still in early phases of adoption, but it is currently helping us with controlling access to beta testing features.
Pros
Easy to use dashboard UI.
Supports a wide array of SDKs.
Well articulated documentation.
Cons
Improve documentation around serverless setups.
Likelihood to Recommend
From my experience it is well suited for web applications, and serverless services and API's. I haven't encountered a scenario where it is less appropriate.
VU
Verified User
Team Lead in Engineering (Information Technology & Services company, 201-500 employees)
We use it for rolling new variants of our code out and passing new features to production to limited people before sending it out for the whole user base. Knowing that we can set up targeting based on many different values allows us to be precise on who we send out the feature for.
Only downside is limited seats for engineers to use, which makes adopting it slower than I would like.
Pros
Targeting and segments.
Feature creation.
Quick setup.
Cons
Limited seats on account.
Cost for every other feature.
Forcing customers into enterprise level accounts.
Likelihood to Recommend
Do you have continuous deploys and a website/app that is being updated by a large team? Use feature flags.
It is being used with the Software Development department to test the value of features in small iterations, ensure implementations are working as expected before rolling out to all customers, to perform A/B tests of features and to have kill switches to enable/disable functionality on a permanent basis. Data gathered by the ability to use feature management in this way informs business decisions and the priority of the work being undertaken.
Through being able to decouple a deployment of code to the release of a feature the development teams and business teams can more effectively decide when, how and to whom a feature is being enabled. This makes work easier to implement and the value of the feature can be understood more effectively.
Pros
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.
Cons
Some areas of the Experimentation functionality aren't as feature rich as other analysis platforms.
Managing specific permissions, roles and the teams sometimes requires configuration within LaunchDarkly itself rather through another system (such as through Azure AD).
Likelihood to Recommend
Decoupling a deployment of new code from the release of a feature.
A/B and/or Multi Variant testing.
Rolling out a feature to a percentage of customers or to certain groups.
VU
Verified User
Manager in Engineering (Gambling & Casinos company, 501-1000 employees)