LaunchDarkly

What do you like best about the product?

I like that LaunchDarkly gives me the ability to control things beyond simple one-off switches. I can use string flags or date-based components and even JSON for more advanced configurations to support our logic flows. It helps add switching logic based on more than a simple Boolean condition, letting me add more complicated, controllable flows in our product. The initial setup was quite easy, just requiring portal configuration and providing an SDK client for use in our code.

What do you dislike about the product?

Maybe a bit easier segment creation and grouping around managing flag targets

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

I use LaunchDarkly to merge new behavior behind flags and roll it out per company without redeploying, which is crucial for payroll changes like calculations needing controlled exposure and fast rollbacks.

What do you like best about the product?

I really appreciate LaunchDarkly's good design and developer experience. It's easy to find things and there's limited friction, which makes it well thought out. The interfaces for customization are good too. I mainly use it to ship software fast with quick rollbacks and to control runtime configs, and it handles feature-rich flag management really well with its rules and very good access controls. I find the flag evaluation metrics crucial for safe offboarding, and the guarded releases feature is pretty cool. The access controls at the resource level are amazing, and the initial setup was very easy, thanks to their minimal SDK.

What do you dislike about the product?

I wish LaunchDarkly had some state persistence managed by them. Having to construct complex user contexts is hard to do and requires a lot of engineering effort. Would love to leverage LaunchDarkly's infrastructure more for that.

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

I use LaunchDarkly to ship software fast with quick rollbacks, control runtime configs, and manage feature flags with rules and metrics. It offers great access controls and auto rollbacks, making releases safer and allowing reliable targeting and flag metrics.

What do you like best about the product?

The SDK integrations are fantastic. LaunchDarkly collapsed two major headaches—safe deployments and structured experimentation—into a single, unified workflow. The compounding time savings and the confidence it gives our engineering and on-call teams are immense.

The context tracking and intuitive UI make it easy to manage who sees what. The ability to run A/B tests and progressively roll out new UI elements to specific user segments without engineering intervention is brilliant

What do you dislike about the product?

There is definitely a learning curve for new team members when it comes to organizing and cleaning up flags. Once a project scales, managing multiple flags can become cluttered and performance could degrade if you don't stay on top of deprecation and maintenance

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

We primarily use it for continuous delivery and targeted rollouts. It allows us to test changes on small segments of real traffic before rolling them out widely. Rollbacks have become a simple toggle flip instead of a stressful, emergency fire drill

What do you like best about the product?

I like being able to toggle features on and off without redeploying, which makes managing rollouts across tenants super convenient from one place. Flag targeting per environment is straightforward and easy to manage. The initial setup was fairly easy; the SDK setup was quick, and the documentation was clear enough to get flags running without much friction.

What do you dislike about the product?

The UI can feel cluttered when managing a large number of flags, and cleaning up stale flags is more manual than it should be. Better filtering and search to find specific flags quickly when the list is long. Automatic flagging of stale or unused flags would help with cleanup instead of tracking them manually.

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

LaunchDarkly lets me manage feature rollouts across tenants easily, toggling features on and off without redeploying. I find flag targeting per environment straightforward, simplifying our workflow.

What do you like best about the product?

I think LaunchDarkly is very intuitive, easy to use, and clear for everyone. You don't need a specific domain expertise to use it, whether you're in customer success or product. I also found the initial setup to be very easy.

What do you dislike about the product?

I think part of it is a new feature, a capability that we expect LaunchDarkly to create. I would like LaunchDarkly to enable me to develop in a separate isolated environment my database, Kubernetes, and stuff like that. Then, all this would process in a different place, and once I'm done, it would help me merge back to my production.

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

I use LaunchDarkly for feature flags to manage releases for selected customers and for developing POCs efficiently. It helps me execute phased releases and refine our delivery approach to win POCs.

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