LaunchDarkly

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?

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.

What do you like best about the product?

LaunchDarkly is widely considered the industry standard for feature management and progressive delivery. It excels at decoupling code deployments from feature releases, giving engineering teams granular control over how and when new features reach users.

What do you dislike about the product?

While the UI is generally clean, the platform's depth can feel overwhelming to non-technical users or beginners who just need simple toggle management.

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

- Granular Targeting & Progressive Rollouts: LaunchDarkly allows you to roll out features to specific user segments, beta testers, or a percentage of your audience. This minimizes the blast radius of bugs and lets teams catch issues early before a full-scale release. - The "Instant Kill Switch": One of its most praised capabilities is the ability to instantly disable a problematic feature in production without rolling back the entire deployment or writing new code. - Beyond Simple Toggles: It handles complex use cases, such as A/B testing different LLMs (routing requests to different models in specific proportions) or targeted experimentation.

What do you like best about the product?

Very transparent and easy to use, user friendly and helpful I feel is very useful tool

What do you dislike about the product?

Sometime the plarform feels a little bit slow

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

The easyness to separe flags for different features and locations

What do you like best about the product?

I like that you can block features at two levels, app-wise or customer-wise, which has made it easy to create bespoke experiences for our customers.

What do you dislike about the product?

While LaunchDarkly is powerful, the pricing model can scale up quickly as monthly active users increase. Additionally, managing flag lifecycle hygiene requires continuous effort to prevent technical debt from stale flags in the codebase, and the UI has a bit of a learning curve for non-technical users.

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

We previously struggled with high-risk software deployments that required complex rollbacks whenever issues arose. LaunchDarkly allowed us to separate code deployments from feature releases, enabling us to test new features safely in production with specific user groups. We can now perform gradual percentage rollouts and instantly kill buggy features with a single toggle, which has significantly reduced deployment anxiety and shortened our release cycles.

What do you like best about the product?

Feature flag control in like production. While LaunchDarkly is a premium tool and priced on the higher side, the business value easily justifies the cost. The time saved avoiding major production outages, rolling back buggy releases instantly without code redeploys, and running controlled canary releases pays for itself.

What do you dislike about the product?

Feature flag cleanup, this can be improved with the help of AI.

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

Risky Code Deployments: Traditional deployments push code and toggle features simultaneously, making updates high-risk for system-wide downtime or critical bugs.

What do you like best about the product?

I especially like its functionality and UI. It is much easier to use compared to other tools like Firebase Remote Config, which is free, but the level of functionality of LaunchDarkly is much easier to manage. It is also easy to view.

What do you dislike about the product?

I would like the Scheduling part to be improved. Some time ago it worked correctly, and now it is not entirely clear how to schedule a turn on, a turn off of a feature pack. Also, for the mobile part, the configuration has not been so simple because there is not much documentation about it, especially with libraries like React or Flutter.

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

LaunchDarkly helps us manage new features and limit the visibility of others for certain users. I like its functionality and UI, and it allows us to innovate in areas of business intelligence.

What do you like best about the product?

It's reliable! We depend heavily on LD for feature rollouts, operational toggles, split testing, etc., across multiple apps, and I've never had to think twice about whether I can count on the system to work. In terms of LD's specific features, I love its DD integration, its flag history, its SSE approach so client changes propagate instantly, and session replay for investigating user bug reports.

What do you dislike about the product?

I haven't been a huge fan of the UI updates in the past year or two. The configurable tag/bubble-looking presentation for selecting which environments are shown atop the flag page is particularly unintuitive.

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

Feature rollouts are pretty much frictionless, and we can target the rollouts by so many different attributes. We build entire GTM strategies around this capability. Secondarily, features like session replay are helping us during incident investigations.