LaunchDarkly

What do you like best about the product?

The feature flag capabilities have been incredibly valuable for our team. They solve a wide range of business use cases by allowing us to control feature rollouts with precision, without requiring new deployments for every change. This has significantly improved our release velocity, enabling us to ship code more frequently while minimizing risk.

One of the biggest advantages is the ability to gradually roll out new features to specific user segments, perform A/B testing, and quickly disable problematic features if issues arise in production. This has given our team much greater confidence in releasing changes and experimenting with new ideas.

Overall, feature flags have streamlined our development and deployment workflow, reduced operational risk, and made it much easier to validate new features with real users before a full-scale rollout. They have become an essential part of our release strategy, helping us deliver value to customers faster while maintaining stability and reliability.

What do you dislike about the product?

Sometimes the support is not great especially during the times when the platform is down and offlate we are seeing a lot of cases where our company are seeing unreliable results

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

LaunchDarkly has solved several challenges that we previously faced around feature releases, testing, and risk management. Before adopting feature flags, releasing new functionality often meant coupling deployments directly with feature launches, making it difficult to test changes in production or quickly respond if something went wrong.

With LaunchDarkly, we can decouple deployments from feature releases, giving us much greater control over how and when new functionality is exposed to users. We can gradually roll out features to specific customer segments, perform A/B testing, validate new functionality with a limited audience, and instantly disable or roll back a feature without requiring a new deployment. This has significantly reduced the operational risk associated with releases.

The platform has also increased our development and release velocity. Our engineering teams can merge and deploy code more frequently without waiting for a coordinated product launch, while product and business teams have the flexibility to control feature availability independently. This has streamlined collaboration across teams and shortened the time it takes to deliver value to customers.

Overall, LaunchDarkly has become a key part of our release strategy. It has improved the reliability of our deployments, enabled faster experimentation and data-driven decision-making, reduced the impact of potential production issues, and allowed us to deliver new features to customers with greater confidence and agility.

What do you like best about the product?

We have a very flexible way to implement the features.

What do you dislike about the product?

It’s hard to manage when there are a lot of flags.

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

The biggest benefit for us is having a feature flag outside of the application.

What do you like best about the product?

easy understand UI, easy approve button, and clean surface

What do you dislike about the product?

last time the service of LD went down, my coworkers and I blocked for some time

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

easy func/rollout capability, no need to rebuild code

What do you like best about the product?

I use LaunchDarkly for safeguarding new features and cohort-based rollouts. It makes rolling out features super easy, and I appreciate that the UI is very clean and user-friendly. The bulk updates via JSON make it much more customizable, and I don't have to manage environments in helm files or local files, which would later require code merges and deployments. LaunchDarkly provides a make checker flow that makes it easy for me to add my counterparts in the loop when releasing features for a new cohort. The other person can approve and apply the changes I raised for review. It was really easy and quick to set up too. I definitely find it way better than the Harness feature flag service.

What do you dislike about the product?

One thing I think can be improved is the UI placement for adding a new rule. It does take some time to understand how to add a new rule. I think if an AI agent were there to create rules or update the flags, it would be the best, as I could pair up with an LD agent to create the rules and send them to me for approval. Makes life a whole lot easier.

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

I use LaunchDarkly for safeguarding new features and cohort-based rollouts. It makes feature management simple, with an easy UI and customizable bulk updates. I avoid managing environments in helm or local files. Approvals and changes are streamlined, improving feature release coordination.

What do you like best about the product?

The filtering options in LaunchDarkly session replay are top-tier. With so many granular filters available, cutting through the noise and finding specific user sessions takes virtually no time

What do you dislike about the product?

The session filtering can occasionally yield false negatives. When narrowing down by a single parameter such as 'URL' or 'exit page', it sometimes returns no results, even for sessions I know took place.

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

It has dramatically sped up our root-cause analysis. With live session tracking and clear log visibility, we can quickly isolate errors, understand the impact on users, and push fixes in real time, rather than guessing what went wrong.

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.