LaunchDarkly

What do you like best about the product?

I like LaunchDarkly for its ease of use, which makes setting up user segmentation for tracking app performance straightforward. It also simplifies cohort breaking as desired. The initial setup was simple, which made getting started quick and easy.

What do you dislike about the product?

I find it confusing to choose between similarly named features like "user - plan type" because there's no clear dictionary or guidance on how the data can be split based on the flag features we have. It would be helpful to have more clarity in this area.

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

I find LaunchDarkly makes cohort splitting easier for tracking app performance, which is simple. It's easy to use, but could use a better dictionary for data splitting based on flag features, especially for similarly named features.

What do you like best about the product?

I don't like anything about LD. I manage it; another team uses it. And collectively it's not great.

What do you dislike about the product?

LaunchDarkly has abysmal support and absolutely no strategy for retaining historical data during migrations. The ability to mass manage isn't there. As a system admin, this website is not ideal for management, and I don't recommend it.

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

As an admin, they've only created problems for me.

What do you like best about the product?

What I like best about LaunchDarkly is how much confidence it gives teams when releasing changes. Feature flags make it possible to ship code separately from releasing functionality, so we can merge work earlier, test in production-like conditions, and turn features on gradually for the right users or environments.

The targeting and rollout controls are especially valuable. Being able to enable a feature for internal users first, then a small percentage of customers, then broader segments, makes launches feel much less risky. If something behaves unexpectedly, the ability to toggle it off quickly without a redeploy is a huge operational safety net.

I also appreciate how useful it is beyond simple on/off flags. Experiments, user targeting, kill switches, and environment-specific flag management all fit into the same workflow, which helps product, engineering, and QA collaborate around releases instead of relying on ad hoc config changes or emergency hotfixes.

What do you dislike about the product?

The main downside is that LaunchDarkly can add operational overhead if teams are not disciplined about flag cleanup. It is easy for temporary release flags to become permanent clutter, and over time that can make the codebase harder to reason about.

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

LaunchDarkly solves the problem of risky, all-or-nothing releases. Before using it, every production deployment carried more pressure because a feature going live often meant the code was live for everyone at once. Now we can deploy code behind feature flags, release gradually, and turn features on for internal teams, beta users, or small customer segments first.

That has improved both speed and reliability. We can merge and deploy work earlier without waiting for every feature to be launch-ready, which reduces release bottlenecks and lets QA, product, and engineering validate behavior in real environments. Percentage rollouts and targeting rules also make it easier to catch issues before they affect the full customer base.

It also gives us a practical safety net. If a feature causes unexpected behavior, we can disable it quickly without rolling back an entire deployment or pushing an emergency hotfix. That shortens incident response time from a code-release cycle to a configuration change, which is a major benefit for customer-facing systems.

Another problem it solves is coordination across teams. Product managers can manage launch timing, engineers can keep risky changes isolated, and support teams can understand which customers have access to which experience. Overall, LaunchDarkly helps us release more frequently, reduce deployment risk, and experiment with less operational overhead.

What do you like best about the product?

I like feature flag enablement because it supports Boolean values and multivariate flags have more than two variations it can have strong number and json variations.

What do you dislike about the product?

I think during release process we have platform dependency where latency or outages can cause or impact our release

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

Right now it's solving control feature rollout deployments

What do you like best about the product?

LaunchDarkly's main purpose for me is to toggle new UI features without having to do another deploy. When you want to test a feature with QA or a select group of users before rolling it out to everyone, it's very helpful. Frontend integration is pretty easy and once your flags are created it makes releasing easy.

What do you dislike about the product?

Only negative is that there can easily be too many old flags if your team doesn't keep them cleaned up. Dashboard also has slight learning curve at first.

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

LaunchDarkly allows us to release frontend with less risk. We can quickly turn features off/on, test out changes on select users, and not have to deploy anything we don't need to. Allows for more control when releasing new frontend features.

Recommendations to others considering the product:

To improve the user experience, consider implementing a feature to automatically archive old flags after a certain period. Additionally, providing more intuitive onboarding tutorials could help new users navigate the dashboard more efficiently.

What do you like best about the product?

For me though, the biggest benefit of feature releases is that you can ship code without having to release that feature to everyone at the same time. We’ve used flags in cases where the feature was technically ready but we wanted to test with a smaller percentage of our users. It also comes in handy if something isn’t behaving how you expect in production. With feature flags you can simply turn off the feature without having to do another deployment. We have avoided a few panicked midnight releases because of that.

What do you dislike about the product?

The biggest downside once you start using feature flags a lot is that you have to stay organized. Dead flags can linger longer than they should, especially if noones responsible for cleaning up old flags. Another pitfall I’ve experienced is when targeting rules get more complex than you originally anticipate. Feature flags as a product are awesome, but you have to have some discipline with naming and deleting temporary flags.

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

Essentially feature releases remove the risk of releasing new functionality. We can roll out a feature gradually, observe how it behaves, and then increase exposure when we are ready. I don’t worry quite so much about whether a minor issue will cause us to do an emergency rollback, and I can easily test functionality with certain users.

What do you like best about the product?

I appreciate that LaunchDarkly allows us to roll out frontend features gradually, rather than making every change available to all users at once. Feature flags integrate seamlessly into React-based applications, enabling us to easily test UI changes, control access, and instantly roll back if a release has unexpected consequences.

What do you dislike about the product?

However, managing a large number of feature flags can become cumbersome if they aren't named carefully and maintained regularly.

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

LaunchDarkly allows us to decouple releases from deployments. We can safely deploy frontend changes, enable them for specific users, monitor their impact, and disable problematic features without needing a redeployment. This helps us minimize release risk and easily experiment with and update our UI.

Recommendations to others considering the product:

To improve the management of feature flags, consider implementing a naming convention and regular maintenance schedule. This will help keep the system organized and efficient.

What do you like best about the product?

I really appreciate how LaunchDarkly gives our teams control when we release features. Instead of simply switching a change on for every user at once, we have the option to gradually roll out features to specific test groups or instantly disable them completely if something goes wrong. Feature flags have greatly simplified communication between our developer, support, and operations teams.

What do you dislike about the product?

Feature flags can quickly become unmanageable when multiple teams create them without a naming convention or a strategy for removing them.

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

LaunchDarkly reduces release risk by decoupling code deployment from feature releases, allowing you to show new features to select users and respond quickly if a feature needs to be rolled back. Streamline your release process, minimize disruptions for your users, and provide your support team with greater visibility during releases.

What do you like best about the product?

So far the integration with agents have been really nice. Performance some been great and the UI and UX is also working nice better than expected AI is nice

What do you dislike about the product?

Well so far I need to sue it more but I like everything I have bused so is hard to say what I don't like, maybe that is hard to understand some of the features and what they are for.

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

flags and release management, before LD managing releases and pushing code out was crazy hard.

What do you like best about the product?

Decoupling deployment from release is a game-changer for maintaining a fast, trunk-based development workflow. LaunchDarkly makes implementing feature flags and gradual percentage rollouts seamless across multiple environments. The SDKs are well-documented and simple to integrate into both frontend frameworks and backend services. The real-time streaming architecture ensures that flag updates propagate across services in milliseconds without needing to redeploy code or restart servers. Having granular targeting rules based on custom user attributes enables running canary releases and dark launches effortlessly, while the instant kill-switch capability gives the engineering team complete confidence to push changes directly into production.

What do you dislike about the product?

Technical debt management can become challenging if the team does not enforce strict flag lifecycle governance; stale flags accumulate quickly in the codebase if not actively cleaned up. The pricing model can also scale up significantly based on Monthly Active Users (MAU) or client-side evaluations, which requires careful planning for high-traffic public-facing apps. Additionally, managing complex flag prerequisites and interdependent rules across multiple microservices can lead to an overwhelming UI view that takes time to audit.

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

It completely eliminates high-stress, all-or-nothing release days. Instead of managing long-lived feature branches and painful merge conflicts, code is merged continuously behind flags. If a new service or database migration introduces unexpected latency or errors, turning off the flag instantly reverts the behavior for affected users without requiring an emergency rollback or hotfix deployment. This drastically reduces the blast radius of new releases, shortens our delivery cycles, and allows for safe testing in live production environments.