LaunchDarkly

What do you like best about the product?

LaunchDarkly provided centralised feature management. It also decouples code deployment from feature release. This enables rolling out new features through canary launches and also rolling back buggy features without an extra deployment.

What do you dislike about the product?

To be honest, there aren't a lot of cons when it comes to LaunchDarkly. Probably, cost can be a factor for small-scale teams. Also, technical debt (i.e., ownership of flags) in large-scale teams can be problematic but this can be made easier through careful planning

What problems is the product solving and how is that benefiting you?

The most important benefit we have observed so far is ease of high-risk feature releases coupled with quick rollbacks (if necessary). Delivery cycle is made smoother through the canary launch strategy. Production versions are stable and downtime can be minimised

What do you like best about the product?

I find LaunchDarkly very convenient as it's always on and never down, which is great. The UI is very straightforward and easy to use, making it easy to implement. I've used LaunchDarkly both in my current position and at previous jobs, where I was responsible for implementing it. It's also helpful because even nontechnical people, like product and UI staff, can easily create and manage feature flags.

What do you dislike about the product?

Like, sometimes the UI displays for environment staging and production. I don't know. It's, sometimes a bit confusing.

What problems is the product solving and how is that benefiting you?

I use LaunchDarkly to control our gradual release process, manage feature visibility, and use a kill switch for issues. It allows us to merge to production behind feature flags, ensuring changes are not visible to customers prematurely.

What do you like best about the product?

I have been using this LaunchDarkly for about a year, and I really like the UI and how easy it is to use across different environments. It also offers all the possible flag combinations, so we can target specific users and features more precisely.

What do you dislike about the product?

Sometimes it’s hard to find the right combination of scenarios, but it totally depends on the setup we’ve done.

What problems is the product solving and how is that benefiting you?

Every sprint, we release new features. We use this to hide a feature behind a feature flag, so we can roll it out based on the target and our planning instead of releasing everything at once. This lets us plan the release and ship in a more controlled way.

What do you like best about the product?

We use it for region specific rollout and for private beta release. Once we had a situation where a new dashboard feature caused confusion for a specific customer segment - we caught it at 8% rollout and pulled back before it became a support escalation. That kind of controlled exposure is genuinely hard to replicate otherwise.

What do you dislike about the product?

It would be helpful if we could schedule when an approved flag should be applied. I’d also like a clean way to share a rollout summary with the customer success team without having to give them full dashboard access.

What problems is the product solving and how is that benefiting you?

We now do account-level targeting for every major feature, specific customers get early access, give feedback, and we iterate before general availability. Our GA timelines have tightened by about 30% because we're not doing big reveal launches anymore, just gradual confident expansions.

What do you like best about the product?

First-class feature flag management with granular audit controls

What do you dislike about the product?

Nothing comes to mind. Everything just works

What problems is the product solving and how is that benefiting you?

Allows the team to ship safely and experiment with features. Their SDKs provide ease of implementation

What do you like best about the product?

Ability to release darkly in Prod, and test in Prod (trunk based approach)

What do you dislike about the product?

1) Once the product is released, you need to clean up the code from the old FF.
2) LD has timing issues sometimes (delays), so you need to tune for it.

What problems is the product solving and how is that benefiting you?

As I said earlier: launching dark behind FF, before release (different concept) and close to the trunk-based approach of development.

What do you like best about the product?

technical performance (in memory cache of flag)

What do you dislike about the product?

Just the interface and context which is not typed. Sometimes its easy to break it.

What problems is the product solving and how is that benefiting you?

Feature Flags

What do you like best about the product?

I like LaunchDarkly because it's simple and straight to the point. I appreciate the release channels and the option to control exactly who gets an upgrade and when. It looks pretty simple to set up, which suggests it is user-friendly.

What do you dislike about the product?

It's a bit confusing that we manage tenants by UUID and not by string name or more friendly names.

What problems is the product solving and how is that benefiting you?

I use LaunchDarkly for the gradual rollout of features, managing different release channels, and stopping rollouts when needed.

What do you like best about the product?

My team ships confidently because we never go from 0 to 100%, we start at 5-10% traffic, watch metrics, expand. AI & Agent Control lets us update ML parameters without a full deploy, saving 3-4 hours per change. The UI is clean enough that non-engineers can check flag status independently.

What do you dislike about the product?

Flag debt accumulates with no real enforcement to retire old flags. The A/B testing module feels underbaked for the price point. Non-critical support tickets move slowly.

What problems is the product solving and how is that benefiting you?

Bad deploys can affect real payroll and other data points, LD removes that risk. Dark launching, gradual rollouts, instant kill switches. MTTR on bad releases down ~60%. QA cycle on major features cut by 2 weeks. At our shipping pace, that compounds fast.

What do you like best about the product?

I like how user friendly LaunchDarkly is for someone who's non-technical. It's really quick to get your head around and really quick to make changes. It's also really clear on who's getting what experience and why, so you don't feel any nervousness around releasing something.

What do you dislike about the product?

Nothing

What problems is the product solving and how is that benefiting you?

LaunchDarkly provides a simple interface to manage complicated rollouts. I can set up segments and flags myself, reducing reliance on engineers. It offers visibility over access, making the process straightforward and efficient.