LaunchDarkly Reviews & Product Details

I like how easy it is to navigate the UI, and that it lets me group flags, rollouts, and other categorizable resources however I want. It can be as simple or as complex as I need, depending on what I’m trying to do.

The change request approval system has been the biggest good change that I've used. It saves a lot of time that would otherwise be spent on private DMs on Slack. Review collected by and hosted on G2.com.

I'm not sure if it's a browser issue (I use Firefox), but sometimes pages load but the components themselves take some time to get rendered. I've also encountered a few hiccups with the search feature when I'm searching for specific flags; I have to be case-sensitive sometimes when I search for flags. Maybe it would be better if it was a bit more relaxed. Review collected by and hosted on G2.com.

LaunchDarkly has been critical for provisioning and managing access to a beta program at scale. It allows us to selectively enable features for specific customer cohorts without manual work or separate environments. This makes it much easier to run a structured beta, gather feedback safely, and iterate without impacting our broader customer base. Review collected by and hosted on G2.com.

There’s an initial learning curve when setting up flags and defining targeting rules, especially if multiple teams are involved. Clear ownership and documentation are important to get the most out of it. Review collected by and hosted on G2.com.

The experience, it's incredibly easy to use. The dashboard is super intuitive, easy to follow once you get familiar with it. The integration as well, is very easy and straightforward. Implementing flags in LD is about as easy as it gets. Just install the SDK, initialize with api key, and you're ready to use feature flags. Documentation is very detailed, just follow along when confused.

Favorite part about LD - how much better life is with testing. It very easy to manage flags based on environments. This is useful when testing and if ever in the event something is wrong in production, it's very easy to kill it with the flagging system. The targeting rules -- being able to segment users based on their attributes makes gradual rollouts very easy. Review collected by and hosted on G2.com.

There's really not much to dislike about LD. Review collected by and hosted on G2.com.

LaunchDarkly provides fine-grained control over features and configurations, allowing us to make changes without the need for redeployments or causing downtime. This flexibility lets us experiment safely, introduce updates gradually, and address issues as they arise in real time. Thanks to local flag evaluation and minimal impact on performance, we can innovate more quickly while still ensuring system stability and delivering a great user experience. Review collected by and hosted on G2.com.

While LaunchDarkly offers robust capabilities as a feature management platform, it can become challenging to handle as the number of flags and environments increases. Teams that are new to feature flagging may face a learning curve, and keeping flags well-organized demands consistent effort and discipline. Review collected by and hosted on G2.com.

The best part is the immediate 'Kill Switch' capability. If a new feature causes a spike in errors or crashes a service, we can disable it in under 200ms without having to redeploy code or restart applications. It’s the ultimate safety net for our production environment. Review collected by and hosted on G2.com.

My main concern is the inherent dependency risk. Because our release process is so heavily reliant on LaunchDarkly, any latency or outage on their infrastructure can impact our ability to manage features in real-time. We saw this firsthand during a recent AWS outage; because LD’s flag evaluation was affected, it trickled down to our end users. It serves as a reminder that you have to be extremely intentional about your 'fallback' values in the code to ensure the app remains functional even if the flagging service is unreachable. Review collected by and hosted on G2.com.

I like LaunchDarkly's easy-to-use interface. It took a minute to learn, but once you get the hang of it, it's easy. I appreciate having normal names for flags along with code-names, so our CRM can display which flags a customer is part of without it looking like code. I also like the segments feature because I can group customers into a segment and add them to feature flags, ensuring I've got them all. If needed, I can add a customer to the segment without having to edit a ton of different flags. Review collected by and hosted on G2.com.

I find it a bit annoying that when a new flag is created, we always have to name the true/false values. They used to be labeled enabled/disabled by default, so half our flags are one or the other. Also, when you turn it on, it's on for everyone by default. For our company, we usually do the opposite, so I'm always editing that right at the start to avoid accidentally turning it on for everyone. Review collected by and hosted on G2.com.

I think the UI of LaunchDarkly is just very clean, simple, and easy to use. Generally, it's really good. I love the targeting rules; you're able to just grab a random list of items from your DB or something, a bunch of IDs, and paste it in to create a new group yourself. Our LaunchDarkly is integrated with GitHub, so when we add flags to GitHub, it automatically creates them in LaunchDarkly. Overall, I've been very happy with LaunchDarkly. Review collected by and hosted on G2.com.

Sometimes in LaunchDarkly it's not clear which context keys I should be using (this is moreso of an issue with our management rather than the product) BUT it would be nice to have these auto generated based on which contexts are currently being provided to the flag in evaluations instead of some master list of context keys. Review collected by and hosted on G2.com.

I like how easy it is to roll out changes safely, targeting specific users, doing gradual rollouts, and instantly rolling back if something looks off. The UI is clear and the audit/history makes it easy to track what changed and why. Review collected by and hosted on G2.com.

Sometimes it can feel a bit complex at first especially with lots of flags and rules and it’s easy for flags to pile up if you don’t stay on top of cleanup. Review collected by and hosted on G2.com.

I like that LaunchDarkly is very configurable, allowing me to set values for feature flags across different environments like dev, QA, staging, and production etc. It also lets me configure various parameters that our UI or API works on, making it flexible. I appreciate that it can handle not just true or false values but also return string values and lists, which I find beneficial. Review collected by and hosted on G2.com.

At this moment, I think there is no external APIs allowed by LaunchDarkly to show the feature flag values. So our organization planned to build an internal app or page to let product managers and others see the feature flags and their values without giving everyone access to LaunchDarkly. We couldn't find an external API that supports this, as LaunchDarkly doesn't expose the endpoint for flag names and values. I think it is a limitation for my organisation's requirement. Review collected by and hosted on G2.com.

I like how easy it is to integrate LaunchDarkly into our app, even in a complex enterprise Angular application. The straightforward implementation and creation of new feature flags save us a lot of time and effort, allowing new feature flags to be created in just minutes. I appreciate the well-designed dashboard, offering plenty of metrics to evaluate statistics for each flag. It's clear to see the state of each flag at any given time, which helps avoid mistakes. The organization of the dashboard into projects makes it easy to manage a large number of flags. What I like most is the rapid toggling response; changes reflect in the app in just 3-5 seconds after saving. We've also had a smooth experience with no server downtime during tests. I first heard about LaunchDarkly from a teammate and found it to be incredibly likable from the start. The initial setup was straightforward, and with just a Confluence article and a short call, we had it fully integrated in under two days. I rate it a 10 for its time-saving feature flagging and other capabilities, even those I haven't explored yet. Review collected by and hosted on G2.com.

The only thing that comes to my mind is to improve the possibility to completely get rid of feature flags created by mistake. I've only found the options to archive or deprecate it. But in some projects could be dozens of flags, and not necessarily all of the are required... so it would be nice to be able to delete them. Review collected by and hosted on G2.com.