LaunchDarkly

What do you like best about the product?

I like LaunchDarkly because it makes it easy to release new features safely, manage feature rollouts, and quickly turn features on or off without deploying new code. Overall, it helps reduce risk and makes the software release process smoother and more controlled.

What do you dislike about the product?

It can be expensive for smaller teams, and some of the more advanced features take time to learn. Managing a large number of feature flags can also become difficult without proper organization.**

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

LaunchDarkly helps me manage feature releases safely without having to deploy new code each time. It reduces release risk, speeds up deployments, makes testing easier, and lets me fix issues quickly by turning features on or off instantly.

What do you like best about the product?

LaunchDarkly has made it much safer to test new features in production by rolling them out to a small percentage of users first, rather than deploying changes to everyone at once. Being able to toggle features on or off instantly without redeploying code has sped up testing cycles significantly, especially when validating changes to trip flow or platform functionality before a full rollout. The targeting rules for controlling exactly who sees a given feature, whether by user segment or percentage, have made testing much more precise than relying on separate staging environments alone. The dashboard makes it easy to monitor flag status and adjust rollouts on the fly without needing a developer to make code changes for every adjustment.

What do you dislike about the product?

Managing a growing number of feature flags over time requires discipline to clean up ones that are no longer needed, otherwise the codebase accumulates unnecessary complexity. Pricing scales with usage and seats, which can get expensive as the number of flags and monthly active users grows. The initial setup for integrating flags cleanly into existing code took some restructuring, especially for parts of the codebase that weren't originally built with feature flagging in mind. Some of the more advanced targeting and experimentation features have a learning curve before getting full value out of them.

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

LaunchDarkly has let us test new features on a small subset of real users before a full rollout, catching issues early without risking a broken experience for everyone on the platform. This has made deploying changes to core functionality, like trip flow updates, much safer, since we can instantly disable a feature if something goes wrong instead of needing an emergency rollback and redeploy.

What do you like best about the product?

This tool makes feature flag management incredibly straightforward, letting teams release, test, and roll back features without redeploying code. With real-time control over flags, progressive rollouts, experimentation capabilities, and robust SDK support, it helps reduce deployment risk while enabling faster, more confident software releases.

What do you dislike about the product?

The platform comes with a learning curve for teams that are new to feature flagging, particularly when setting up advanced targeting rules and managing multiple environments. In addition, some reporting and experimentation capabilities are limited to higher-tier plans, and the pricing can get expensive for organizations that need to manage a large number of feature flags.

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

It separates feature releases from code deployments, so teams can test new functionality safely, roll it out gradually, and instantly disable problematic features without needing emergency deployments. This approach lowers release risk, supports more frequent deployments, speeds up product experimentation, and helps engineering teams ship new features with greater confidence and stability.

What do you like best about the product?

Release features without exposing them
Instant rollback (Kill Switch)

What do you dislike about the product?

high cost
feature flag technical debt
increase testing efforta

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

LaunchDarkly is a feature flag management platform that separates deployment from feature release.

What do you like best about the product?

It’s very easy to install and use. Helpful product

What do you dislike about the product?

Long learning curve. But is doable with some experience.

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

Helping in my data analysis and evaluation of methods used

What do you like best about the product?

*Deploy safer + faster*
- *Separate code deploys from releases*: Ship code to production multiple times a day, but only turn features on when product is ready. No more “big bang” releases.

What do you dislike about the product?

I don’t dislike anything about launchdarkly

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

The kill switch instantly turns off a problematic feature without a code roll back

What do you like best about the product?

I appreciate the ease of variation configuration in LaunchDarkly, which allows me to use a lot of data from the invocation point to decide on the variation. This makes it easy to test or guard specific logic changes in the code depending on the service, client, or percentage. I find it valuable for gradual rollouts and implementing kill switches without the need for code deployment, as well as testing different approaches without constantly having to change the code.

What do you dislike about the product?

We recently had a downtime and it was not very clear when it ended. It also didn't start working without resetting the services. Although it was communicated, we would like a constant push for as high uptime as possible.

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

I use LaunchDarkly for feature flags, allowing gradual rollouts and testing different approaches without redeploying code. It offers kill switches and client-based variability, making it easy to test or safeguard logic changes.

What do you like best about the product?

What I like best is how easy it is to do controlled rollouts without shipping separate builds. Being able to target by environment/tenant, gate risky changes behind flags, and then cleanly turn features on (or keep them off) in production/dev environments.

What do you dislike about the product?

I have to set up a full rule, but I’d like to keep it simple. I want to be able to choose orgs from a dropdown and disable the flags.

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

LaunchDarkly helps us separate deployment from release. We can ship code, validate it in lower environments, and then gradually enable it by tenant or environment without needing another deploy. This reduces the blast radius for risky changes, makes rollbacks as simple as flipping a flag, and lets us run experiments or phased rollouts without maintaining long-lived branches. For us, that translates into faster delivery with more confidence, and fewer emergency hotfixes when something misbehaves in production.

What do you like best about the product?

I like environment saperation and progressive deployment

What do you dislike about the product?

the complexity and somewhat UI is little hard to navigate

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

it provides each developer with saperate environement so they can build their own stuff

What do you like best about the product?

Ability to control released features, A/B testing, ability for dev teams to continue to release to prod without making the feature generally available which minimizes tech debt and speeds release cycles.

What do you dislike about the product?

It took some trial/error to learn how to deploy in a way that didn't unnecessarily add more feature flags than needed. Back end/ front end feature flags were a bit confusing for the team to learn how to properly manage at first.

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

rapid development, limiting tech dept, beta and A/B testing capabilities. fail fast, learn, and pivot