LaunchDarkly Reviews & Product Details

The biggest advantage of LaunchDarkly is the way wherein it's ability to separate deployment and release in a real prod environment. We use it in our stack (Node.js backend + React frontend in most cases) to control feature rollouts without redeploys.

We can turn on features for internal users first, then for certain customers all e and finally roll out in percentage based releases. This has made biweekly releases a lot safer, especially for high impact changes.

The integration of the SDK was simple and once implemented it became a core part of our release workflow. It also gives product and QA teams control over feature exposure without relying on engineering, which increases overall velocity. Review collected by and hosted on G2.com.

Feature flag management can become or becomes a problem if not managed as per best practices. In our case, stale flags started piling up after multiple releases, and without strict cleanup which we have every quarter helps us fix this

Pricing is another concern, it scales quickly as usage grows. During renewal, we didn’t receive the same level of discount that was initially discussed during onboarding, which made cost planning a bit more harder. Review collected by and hosted on G2.com.

LaunchDarkly makes it easy to create and manage feature flags. When creating a new feature flag, it is created and configured across all of our environments at the same time. We regularly create different rules in each environment that control who sees which value of each flag--it's very easy to see and manage the rules. We have even utilized the LaunchDarkly API to allow our customers to opt-in or opt-out of specific flags so they can try new features--it's fantastic! I'm amazed at how quickly feature flag changes propagate--if I have 3 tabs open to the same site, changing the feature flag value in one results in all three being updated within a few seconds. Review collected by and hosted on G2.com.

Using the UI is very straightforward. I was at a bit of a loss at figuring out how to integrate with the LaunchDarkly AP--I've never used an API quite like this before--but thankfully my AI assistant was able to handle it. Review collected by and hosted on G2.com.

LD's Feature Flag tools are so flexible and handle every situation that I encounter in my role as a PM of mobile apps. We regularly release new features behind a flag and use target segments to give select customers early access to beta test and provide feedback before full rollouts. Those segments can be used for multiple FFs, making it very convenient when managing multiple flags for android/iOS/etc. Review collected by and hosted on G2.com.

The only pain point I have right now is enforcement of rules around describing exactly how a given FF works. When managing flags that predate my time working on the app I have to go digging to confirm exactly how they are working. Review collected by and hosted on G2.com.

It makes releasing software both safer and faster by using feature flags, and it lets our team decouple deployment from release. That way, code can go live without immediately exposing changes to users. This reduces risk and supports gradual rollouts, quick rollbacks, and easier experimentation. I also like how it strengthens collaboration between engineering, product, and operations by providing controlled visibility and rollout decisions, without needing a full redeploy every time. Review collected by and hosted on G2.com.

There’s nothing in particular to dislike. It already has great features, and it sounds like even more are on the way. Review collected by and hosted on G2.com.

I like the target individual section. And the progressive rollout functionality, even though it's not super polished Review collected by and hosted on G2.com.

We can not use custom rules because we have to make sure that user and organization IDs are matched. For example, we can not match a user on a flag by their name because we can not guarantee that the name will be part of the metadata at all times. The target individual section helps with this, but it doesn't always propagate with all of the information, so sometimes, if it's a newly created account, for example, we can not find it there. We'll have to trust that the ID is right. Review collected by and hosted on G2.com.

I like how easy it is to navigate the UI, and that it lets me group flags, rollouts, and other categorizable resources however I want. It can be as simple or as complex as I need, depending on what I’m trying to do.

The change request approval system has been the biggest good change that I've used. It saves a lot of time that would otherwise be spent on private DMs on Slack. Review collected by and hosted on G2.com.

I'm not sure if it's a browser issue (I use Firefox), but sometimes pages load but the components themselves take some time to get rendered. I've also encountered a few hiccups with the search feature when I'm searching for specific flags; I have to be case-sensitive sometimes when I search for flags. Maybe it would be better if it was a bit more relaxed. Review collected by and hosted on G2.com.

I like LaunchDarkly's granular targeting capabilities such as user, region, and environment levels. This allows us to deploy code safely and then enable or disable features in real time without redeploying, reducing risk and improving rollout confidence. I also appreciate the ability to conduct A/B testing and controlled experiments, which helps us measure impact before a full rollout. The initial setup was straightforward; adding the SDK to the application was simple, and creating flags in the dashboard was intuitive. We were able to toggle features quickly without much friction, making onboarding smooth for simple use cases. Additionally, real-time feature toggling without redeployment is a significant benefit. Review collected by and hosted on G2.com.

Flag management can get messy over time like as more teams start using it the number of flags grows quickly. Without strict governance it becomes hard to know: which flags are in use, which ones can be removed, what impact a flag has. Review collected by and hosted on G2.com.

I use LaunchDarkly for feature flagging and basic configuration management. I really appreciate having an easy UI to manage access to certain features on our app. I like being able to fine-tune access for organizations, users, etc. The flag variations are very helpful, and I like that the flags are not just boolean but can be essentially any data type. Overall, it allows me to do more than just simple feature flagging, which is beyond what some competitors offer. Using LaunchDarkly in general is quite easy. Review collected by and hosted on G2.com.

One thing that was annoying was when I have a rule targeting a single user in addition to a rule targeting an organization that the user is in, the organization value overrides the individual value - it should be the other way around. Also, it would be nice if there was more in-depth TypeScript support since flags can have any shape, maybe generating types for flags similar to what Supabase does for schema types. Review collected by and hosted on G2.com.

I like LaunchDarkly for its ease of use and the agility it provides for continuous delivery, allowing me to quickly revert to a stable version if any issues arise. I also appreciate the real-time listeners that save us from constantly checking the flags and allow us to receive updates and respond faster. Review collected by and hosted on G2.com.

In my A/B testing, LaunchDarkly does not provide us with user segmentation. It would be very helpful to know which already identified users are being assigned each value and to be able to extract more precise metrics. It would be very useful to know which flag value is assigned to each device; it could be a custom ID in case the user is not identified, but if the user is identified, it would be good to have that information. Review collected by and hosted on G2.com.

I love how LaunchDarkly allows us to easily control new features by letting us deploy quickly with features behind flags, removing worries about causing issues in our production environment. It's great that I can also use it to selectively give access to specific users, whether for early beta testing or entitlement control. I really appreciate its quick and straightforward implementation. I can easily create a new flag, call that in the code, and use it to wrap features, plus the instant updates in the UI are fantastic, as I don't need to refresh. The LaunchDarkly extension in VSCode is also very useful for quickly toggling flags in dev environments. Setting up LaunchDarkly was pretty easy; I installed the launchdarkly-react-client-sdk and bootstrapped the LDProvider in our React app to use hooks for calling flag values. Review collected by and hosted on G2.com.

Some of the UX around controlling the more in-depth configuration and variations on flags can feel a bit clunky or burdensome. Review collected by and hosted on G2.com.