LaunchDarkly Reviews & Product Details

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.

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 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.

I appreciate LaunchDarkly's ease of use and the additional features it offers. The UI is excellent and makes complex flag evaluation straightforward. The configurability of feature flagging is a significant improvement over the previous solutions we used, allowing much more control and flexibility. The ability to search for contexts by name is particularly useful, making the process of toggling feature flags for specific users, projects, or companies extremely easy directly from the browser. This capability has greatly enhanced our workflow, moving beyond a simple on/off solution to a more sophisticated and user-friendly interface. Overall, LaunchDarkly's feature flagging service is the most valuable aspect for us, and it's a primary reason for our continued use and affection for the service. Review collected by and hosted on G2.com.

I find the network calls erroring out while trying to stream data to be a problematic issue, even though it hasn't impacted functionality significantly. Additionally, I'm not satisfied with LaunchDarkly's observability feature—its lack of robustness and insight, coupled with the high cost, doesn't meet my expectations. The integration of Observability and Session Replay feels overly coupled, and I don't appreciate its interference with the console. Finally, the pricing model is complicated, especially the context counting method, which makes it difficult to forecast costs. Review collected by and hosted on G2.com.

I appreciate that LaunchDarkly offers a better UX compared to Taplytics, both in the SDK and the dashboard. I particularly like that when editing a flag, the change does not apply until I click 'save changes.' Taplytics, about 2 years ago, didn't have that feature and would apply my changes as soon as I made them. Review collected by and hosted on G2.com.

I think UX can be improved in managing many feature flags in an experiment. I don't think I can intuitively understand what experiment (a feature flag parent or group) this current feature flag I'm looking at is grouped with. With multiple feature flags being turned on, I would love to be able to see a diagram or graph that shows the entire branches of what flags we have set up and its traffic status. Review collected by and hosted on G2.com.

What I like most is how flexible and precise it is with feature gating. I use it to control access to different parts of our platform, and it’s easy to target features by individual users, email domains, or specific groups. That level of control lets us roll out changes safely, test things with the right audiences, and avoid unnecessary risk. It’s become a really valuable part of how we ship and manage features, and I’d absolutely recommend it. Review collected by and hosted on G2.com.

There isn’t much I dislike about LaunchDarkly. Like any tool, it can take some time to fully understand and use all of its capabilities, but once you’re familiar with it, it works very well. Review collected by and hosted on G2.com.

I’ve used several tools in this space, but LaunchDarkly stands out because of its absolute consistency. In our team, we rely on the high availability and accuracy of their SDKs; when we toggle a flag, it works instantly without any "flicker" or delay. The platform is very smooth to navigate, which makes it easy to manage multiple environments. It’s one of the few tools in our stack where everything just works exactly as it’s supposed to, every time. Review collected by and hosted on G2.com.

Honestly, there isn't much to complain about. If I had to pick something, the pricing model is definitely on the enterprise side, so you have to be mindful of your seats as your team grows. But given the uptime and accuracy we get in return, the value is clearly there. Review collected by and hosted on G2.com.

I appreciate the UI of LaunchDarkly, which is kind of easy to understand without having to read a manual, although some exploration and guides can be helpful. I like how LaunchDarkly allows us to roll out features to specific clients, using key attributes like ID or country, and even lets us filter hundreds of IDs in a segment. This makes it much easier compared to doing it manually in the codebase or with a database. Having a UI to manage features definitely makes things easier for us. Review collected by and hosted on G2.com.

If I'm not mistaken, once I set the key name for a feature, it cannot be changed. I shouldn't reuse the same key name as it will confuse future team members including me. I need to create a different feature to have a new key name. Review collected by and hosted on G2.com.

My favorite feature is the "Kill Switch" capability. It gives our team tremendous confidence to know that we can immediately disable a problematic feature in production without having to roll back code. The ability to separate deployment from release has truly transformed our workflow for the better. Review collected by and hosted on G2.com.

Dealing with "flag debt" can be quite challenging. Although there are tools available to help spot outdated flags, actually removing them from the codebase once a feature is fully released still demands significant manual effort and discipline from the engineering team. Review collected by and hosted on G2.com.