LaunchDarkly
LaunchDarklyExternal reviews
705 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Easy Rollbacks and Targeted Feature Releases with LaunchDarkly Flags
What do you like best about the product?
We can roll back the feature easily using the LaunchDarkly flag. This approach is particularly useful for releasing new features to selected companies or trial users.
What do you dislike about the product?
Nothing at the moment. It might be because of the high pricing that our organization has limited access to LaunchDarkly
What problems is the product solving and how is that benefiting you?
Target specific users and deploy code to production without exposing the feature, and use the flag to conduct various types of testing.
LaunchDarkly Makes Feature Flag Management Fast, Easy, and Powerful
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
LaunchDarkly is giving us the flexibility we need to have multiple teams working independently on a single large codebase to create features that can be deployed to the production server but not released to customers until we're ready. It's even giving us the ability to allow our customers to opt-in to in-progress experiences so we can get early feedback. The fact that the feature flags are "live" and don't require a recompile or redeploy is wonderful! The same feature flags are available to our front-end code as well as our back-end code, so we can completely control the availability of a feature.
Easy and Reliable Feature Control
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
I use LaunchDarkly to control experimental features, reverting to safe versions if there are errors. It gives us agility in continuous delivery and confidence to revert to a stable version. Additionally, I like its ease of use and the real-time listeners that allow us to respond quickly to changes.
Flexible Feature Flags and Target Segments That Streamline Mobile Releases
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
LD helps hugely in feature rollouts, especially as we often develop features for one platform before another but roll them out at the same time. I haven't yet hit a limit on our workflows thanks to the flexibility.
Screen Recordings Make Debugging Complex TypeScript Apps Effortless
What do you like best about the product?
It lets me watch a recording of the user’s screen while they’re using my app, so I can pinpoint the exact issue and understand whether it was user error or an actual system problem. For example, my app is a TypeScript app with lots of different features—AI integration, plenty of chat in the UI, 3D rendering, and other things that are hard to troubleshoot using only the console.
What do you dislike about the product?
Sometimes it breaks when the session is really long and has a lot of logs. It gets the memory usage of my chrome tab really high and it just break causing an OOM issue
What problems is the product solving and how is that benefiting you?
It lets me view user sessions easily and follow the execution timeline. It also integrates with Slack, which helps me get answers faster. The AI feature is useful for understanding issues that might otherwise feel ambiguous.
Easy to Use with Strong Environment Management and a Consistent 2PR Review Process
What do you like best about the product?
Ease of use. Ability to manage by environments and the review process to ensure 2PR is always followed.
What do you dislike about the product?
Intelligence in identifying duplicate or related rules and simplifying them.
What problems is the product solving and how is that benefiting you?
Feature roll outs by customer, region, organization or environment.
Intuitive and Efficient for Feature Management
What do you like best about the product?
I find LaunchDarkly very intuitive and easy to navigate. You can create flags easily, and editing them is just as simple. Even new users can quickly understand how it works. Being able to easily add or remove functionalities on a live product is invaluable. We release new features at least twice a month, and having the agility to turn flags off for various reasons in a very efficient way makes LaunchDarkly the best partner for software development. It was our first go-to and it keeps rocking it.
What do you dislike about the product?
One thing that could be improved is the archived flags- right now there is no fast way to bulk reactivate flags.
What problems is the product solving and how is that benefiting you?
LaunchDarkly lets me toggle features in our product interface, adding or removing them easily on a live product. This efficiency is critical since we release new features regularly, ensuring we can manage flags swiftly.
Instant Kill Switch Control Without Redeploys—A Production Safety Net
What do you like best about the product?
The best part is the immediate 'Kill Switch' capability. If a new feature causes a spike in errors or crashes a service, we can disable it in under 200ms without having to redeploy code or restart applications. It’s the ultimate safety net for our production environment.
What do you dislike about the product?
My main concern is the inherent dependency risk. Because our release process is so heavily reliant on LaunchDarkly, any latency or outage on their infrastructure can impact our ability to manage features in real-time. We saw this firsthand during a recent AWS outage; because LD’s flag evaluation was affected, it trickled down to our end users. It serves as a reminder that you have to be extremely intentional about your 'fallback' values in the code to ensure the app remains functional even if the flagging service is unreachable.
What problems is the product solving and how is that benefiting you?
Operational Peace of Mind: You can ship code at 2 PM on a Friday because you know the feature is hidden behind a flag. If anything breaks, you have a 200ms kill switch rather than a 30-minute rollback process.
The "Big Bang" Release Risk: Traditionally, deploying code meant releasing it to everyone at once. If there was a bug, you had to scramble to roll back the entire deployment.
The "Big Bang" Release Risk: Traditionally, deploying code meant releasing it to everyone at once. If there was a bug, you had to scramble to roll back the entire deployment.
Effortless Feature Testing with LaunchDarkly
What do you like best about the product?
I really like LaunchDarkly for its easy-to-use interface, which makes targeting certain user segments a breeze. It's super convenient for confirming that the flag values are being served to users using the evaluations tab. Plus, the initial setup was very easy, which I really appreciated.
What do you dislike about the product?
There seems to be a bug when you clone a flag that does not copy the full targeting configuration for the previous flag and you get an error that says 'Too many requests'.
What problems is the product solving and how is that benefiting you?
I use LaunchDarkly for releasing FE web features, allowing protected testing in production environments.
Feature Flag Management with LaunchDarkly
What do you like best about the product?
I think the UI of LaunchDarkly is just very clean, simple, and easy to use. Generally, it's really good. I love the targeting rules; you're able to just grab a random list of items from your DB or something, a bunch of IDs, and paste it in to create a new group yourself. Our LaunchDarkly is integrated with GitHub, so when we add flags to GitHub, it automatically creates them in LaunchDarkly. Overall, I've been very happy with LaunchDarkly.
What do you dislike about the product?
Sometimes in LaunchDarkly it's not clear which context keys I should be using (this is moreso of an issue with our management rather than the product) BUT it would be nice to have these auto generated based on which contexts are currently being provided to the flag in evaluations instead of some master list of context keys.
What problems is the product solving and how is that benefiting you?
LaunchDarkly lets me roll out features gradually, test on a small user set first, and minimizes launch risks.
showing 1 - 10