I like how LaunchDarkly helps with production releases. We can just flip a flag and release a new feature to a beta group or to everyone. If there is an issue, we can easily just turn the flag off to hide the feature. I also find the UI easy to use, and it's clear what the state of the flag means and what environment I am applying the flag change to. Review collected by and hosted on G2.com.

Not much. I only use it for feature flags though. Review collected by and hosted on G2.com.

I love that LaunchDarkly lets us control access to new features and roll them out at whatever pace and to whatever audience we want. I really appreciate the good interface, which is intuitive and simple to use, as it means I don't have to waste time figuring out the interface or learning code to control feature flags as a product manager. I also find that the search functionality works well despite having many feature flags. Review collected by and hosted on G2.com.

Sometimes finding feature flags can be hard as we have so many. Review collected by and hosted on G2.com.

I like using LaunchDarkly to roll out features in phases and being able to test them on specific accounts. The ability to create segments is really handy because it allows me to create a data set and use it in rules at multiple places, which means I don't have to manually add rules every time. Instead, I can just add an existing segment. The initial setup was very easy as well; I was able to create the flag in the UI and quickly implement it within our code. Review collected by and hosted on G2.com.

Nothing, everything works great Review collected by and hosted on G2.com.

I like using LaunchDarkly for gradual rollouts of features, as it eliminates the need for feature flags in the code and redeploying for changes. The web app is easy to use, and I find the SDK easy to implement inside my code. Review collected by and hosted on G2.com.

It’s fine, no issues with it.

No ai or good documentation really Review collected by and hosted on G2.com.

I find LaunchDarkly easy to use because the interface is clean and intuitive. Creating flags, setting up targeting rules, and rolling out changes to only some percentage of targets takes just a few clicks. The initial setup was also very easy. Review collected by and hosted on G2.com.

Pricing is one of the big pain points; it gets quite expensive as we scale up the number of seats. The experimentation and metrics features are useful but feel less mature than the core flagging product. Finally, the UI gets quite cluttered once there are a lot of flags, and cleaning up is quite manual. 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 really appreciate the granularity of the flags and how easily you can tailor them to your exact needs. Review collected by and hosted on G2.com.

Sometimes the UI feels a bit overwhelming, and it can take extra effort to navigate. It’s also not the easiest to replicate an environment exactly without using the CLI. 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 like the flexibility of being able to configure a feature flag with different rules. Review collected by and hosted on G2.com.

For now, nothing to complain about. I really like the way Launch Darky works, and how easily you can use it on both the backend and the frontend. 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.