LaunchDarkly
LaunchDarklyExternal reviews
680 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Excellent platform for feature management
What do you like best about the product?
We found LaunchDarkly very helpful to organize Continuous Delivery by separating deployments and feature releases. It also allows to better isolate concurrent WIP done by different teams. We often use LD for A/B-testing and gradual feature releases to end users.
What do you dislike about the product?
Nothing really to complain about, the tool does its work, without any customer support needed.
What problems is the product solving and how is that benefiting you?
The main problem LD helps us with is Continuous Delivery, as we have multiple teams working on large features.
Great tool
What do you like best about the product?
Launch darkly is a very useful tool for feature gating. The level of granularity of LD flags are impressive.
What do you dislike about the product?
I dont have any major complaints about LaunchDarkly.
What problems is the product solving and how is that benefiting you?
We use launchdarkly for feature management, esspecially for new features that we don't want to full release or for rolling back bad features. We also do some testing for certain features to see if they should be released to other clusters.
It’s a great tool to maintain release versions and while releasing a new features to early adopters.
What do you like best about the product?
The best thing about launch darkly is -
1. Ease of integration of the Launch darkly feature with code, since we have first party NuGet and SDK.
2. Changes are reflected instantly once published, didn't observed any lag which publishing the changes.
3. Segregation of user using segments, can have multiple segments in a LD flag.
4. Ability to create custom rules.
5. Easily implemented via DevOps pipelines.
1. Ease of integration of the Launch darkly feature with code, since we have first party NuGet and SDK.
2. Changes are reflected instantly once published, didn't observed any lag which publishing the changes.
3. Segregation of user using segments, can have multiple segments in a LD flag.
4. Ability to create custom rules.
5. Easily implemented via DevOps pipelines.
What do you dislike about the product?
The things which can be improved are -
1. Reading and editing the users in a segment or flag.
2. Its difficult to add users in a big segment when the users are GUID's, since the search functionality does not work properly and gives multiple suggestion in GUID's.
3. The settings and admin tabs can be made more cleaner and less chaotic.
4. Support to read segments using LDClient should be added in C# NuGet, right now only API support is provided.
1. Reading and editing the users in a segment or flag.
2. Its difficult to add users in a big segment when the users are GUID's, since the search functionality does not work properly and gives multiple suggestion in GUID's.
3. The settings and admin tabs can be made more cleaner and less chaotic.
4. Support to read segments using LDClient should be added in C# NuGet, right now only API support is provided.
What problems is the product solving and how is that benefiting you?
1. Maintaining release versions across different environments and ease of deployment by switching the release versions.
2. Releasing new features version to early adopters by maintaining cohorts using segments.
2. Releasing new features version to early adopters by maintaining cohorts using segments.
Easy to use dynamic feature flag solution
What do you like best about the product?
It's easy to use and supoport different types of values like Boolean, String, Number and even JSON. The SDKs are there to integrate in almost all the technologies. We use a lot of feature flags in different places like frontend and backend and it works seamlessly.
What do you dislike about the product?
The user's (IDs) can be set in the interface. Hence our IDs are UUIDs, they are not identifiable after adding them to the feature flag. Ideally, we should be able to put a "display text" along with the IDs.
What problems is the product solving and how is that benefiting you?
We do continous delivery of various features but need to control who can see/use these features. So we expose the feature for the internal users first and release it to public. LauchDarkly helps to solve this issue in each stage like exposing it to the developers first, then the internal teams and to the public at the end.
Best feature management software
What do you like best about the product?
With lauch darkly we decoupled for deployements from feature releases. This gave product fine grained control over when to release a feature. It also helped with targeting a population and running experiements. It also gives control over schduling releases. It helps co-ordinate multiple feature releases.
What do you dislike about the product?
Launch darkly UI application can be unintutive for product managers. It also needs a better visual representaion of targeting for feature flags.
What problems is the product solving and how is that benefiting you?
Helps in Beta testing. Experimentation. It helps Engineers for pushing through code with inceremental software delivery.
Robust and user friendly
What do you like best about the product?
PMs, QA, and engineers alike can easily navigate the UI. I also like that we can do controlled releases by percentage and easily roll back if needed.
What do you dislike about the product?
Our mobile client continuously has problems with evaluating feature flag values which I believe is due to network connectivity. This is frustrating because the flag may be evaluated as false even though it should be true.
What problems is the product solving and how is that benefiting you?
My team is able to deliver features in a controlled way with feature flags, instead of relying on aligning deployments with marketing releases.
Highly Recommend LaunchDarkly
What do you like best about the product?
It is very easy to manage feature flags.
What do you dislike about the product?
Sometimes finding support on the website is difficult.
What problems is the product solving and how is that benefiting you?
Being able to manage feature flags.
Easy toggle management
What do you like best about the product?
What I really appreciate about LaunchDarkly is its ability to let us update and test new features directly without the need to constantly push out new code versions with changes or reverting changes. It's super useful because it means we can experiment with different features, see how they perform, and make necessary adjustments in real time. This way, we can make sure everything works perfectly for a small group of users before we roll it out to everyone.
What do you dislike about the product?
The pricing might be a bit on higher side, though it worth for a real CI/CD environment. The SDKs could be a bit better.
What problems is the product solving and how is that benefiting you?
LaunchDarkly helps to safely deploying and manage new features in real-time by providing a reliable toggle service. It help by enabling gradual rollouts, facilitating A/B testing, and allowing for quick reversions without needing to redeploy the entire application. This approach minimises risk, enhances deployment speed and enables personalised user experiences.
Extremely feature rich, intuitive, fast and customisable
What do you like best about the product?
Launch Darkly has a very robust and feature rich platform. Beyond just feature flagging, you have the ability to deeply control how and when features are delivered to your customers, with tools to automate stale flags and code cleanup. They have integrations with all the software that we use which has made integrating that much simpler.
Beyond that, we have a very custom implementation which takes into account cache affecting feature flags on our edge compute platform. The Launch Darkly team have been there to answer our questions and provide hands on support every step of the way. They even took on the task of training our experimentation team on how to use the software.
We have very strict requirements on our edge platform to return results in a tiny timeframe, the Launch Darkly API is incredibly fast, reliable and suitable for this usecase.
Beyond that, we have a very custom implementation which takes into account cache affecting feature flags on our edge compute platform. The Launch Darkly team have been there to answer our questions and provide hands on support every step of the way. They even took on the task of training our experimentation team on how to use the software.
We have very strict requirements on our edge platform to return results in a tiny timeframe, the Launch Darkly API is incredibly fast, reliable and suitable for this usecase.
What do you dislike about the product?
It's very difficult to find things I dislike, but if I had to dig deep I would say that it would be useful to have the ability to separately handle a "holdout" group percentage for each flag, along side an active and inactive state. The process to do this at the moment is farily manual and involves creating a prerequisite flag alongside the experiment.
Due to our custom implementation, it would be an advantage to be able to fetch the "tags" associated with the flags in the same fetch. Currently, we have to handle this ourselves (due to a strict requirement to return results within a tiny timeframe).
Due to our custom implementation, it would be an advantage to be able to fetch the "tags" associated with the flags in the same fetch. Currently, we have to handle this ourselves (due to a strict requirement to return results within a tiny timeframe).
What problems is the product solving and how is that benefiting you?
Our website receives over 400 million user sessions every year, so releasing features can be a risky endevour! Launch Darkly helps you reduce the risk and measure the impact of releasing features in production. Since metrics can be fed directly into Launch Darkly, you can setup automatic safety mechanisms which switch features off when a relevant metric falls below acceptable thresholds. We closely measure our DORA metrics, and Launch Darkly has helped us improve these, especially with Mean Time to Recovery.
Before we had implemented Launch Darkly, our experimentation team had little to no autonomy when it came to changing percentages for slow rollouts. Infact, it was a long and drawnout process which involved a lot of steps and a lot of waiting between those steps. Now that we have our Launch Darkly implementation in place, once an experiment has been created, the experimentation team need only log into the Launch Darkly dashboard and make the changes directly themselves which are then reflected instantly in production.
Before we had implemented Launch Darkly, our experimentation team had little to no autonomy when it came to changing percentages for slow rollouts. Infact, it was a long and drawnout process which involved a lot of steps and a lot of waiting between those steps. Now that we have our Launch Darkly implementation in place, once an experiment has been created, the experimentation team need only log into the Launch Darkly dashboard and make the changes directly themselves which are then reflected instantly in production.
Intuitive platform, enables experimentation teams, great support from account execs
What do you like best about the product?
The platform is easy to use, and is very practical in allowing different teams to have controls over specific parts of the release process. Experimentation can have their roles separately from engingeering and these permissions allow multiple parts of the business to align on feature rollout. There looks to be loads of potential for metrics tracking in the web app, which will be very useful in taking the grunt-work out of analysis. The account team / customer support is great, all of the memebers are very helpful and keen to work together to help you get the most out of the platform and the relationship.
What do you dislike about the product?
LaunchDarkly is very dependent on initial integration and the choices made in set up. It is vital to ensure experimentation are involved when first setting up the platform, if they are to be end users, else the setup choices may hinder experimentation capabilities and create tech debt.
What problems is the product solving and how is that benefiting you?
LaunchDarkly allows the experimentation team to control the rollout of AB tests, as opposed to being bottlenecked by pipelines within the tech stack, creating a much shorter time-to-launch for expeirments - it is essentially the click of a button! Likewise, the control being handed over to the experimentation team allows us to intervene much quicker if a feature/experiment is not going in the direction expected - with an almost instant turn off. The platform makes it easy to create, manage, and have visibility of experiments as well as maintaining accountability through logging changes.
showing 251 - 260