LaunchDarkly is used for feature flag implementation. It allows me to control product release by deciding whether to show certain features to users. I can also control feature visibility remotely by toggling flag values.
LaunchDarkly
LaunchDarklyExternal reviews
615 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Launch Darkly is a really good tool
What do you like best about the product?
I've heard engineers talk about how easy it is for them to put new features behind a feature flag in Launch Darkly. From the product side, its super easy to create segments of users. This has improved the way we manage our Alpha, Beta, and GA releases. I'm currently leading a huge intiative at the moment; I can not imagine doing this effectively without LD.
What do you dislike about the product?
Their zapier integration is limited. We were attempting to completely automate our beta process leveraging Launch Darkly + Hubspot forms. We failed to do so because LD's zapier integration doesn't support Segments. We are exploring leveraging their public API to build a custom solution.
What problems is the product solving and how is that benefiting you?
It has helped us do a few things better. 1. We manage alpha and beta releases more effectively. 2. We hav avoided massive outages by leveraging percentage based rollouts 3. It has helped us reduced the risk of launching large features or intiatives in our customer.
Effortlessly manage feature rollouts with remote control and suggest analytics integration
What is our primary use case?
How has it helped my organization?
LaunchDarkly helps avoid complete rollbacks when multiple features are released, and one causes an issue. We can simply turn off the problematic feature, saving on redeployment and testing cycles.
What is most valuable?
I appreciate that we can release any feature in production and maintain control over it. If something goes wrong, we can go to the portal, turn off the flag, and manage the situation remotely.
What needs improvement?
Fetching information about multiple flags in a single action would be beneficial. Additionally, incorporating some analytics on LaunchDarkly would enhance its functionality.
For how long have I used the solution?
I have been using LaunchDarkly for more than one year.
What do I think about the stability of the solution?
I have noticed stability issues in terms of backend performance, such as delays.
What do I think about the scalability of the solution?
LaunchDarkly is scalable; however, there are areas they could improve on to enhance scalability further.
How are customer service and support?
I haven't yet needed to use customer service, however, support is available for raising questions or queries if necessary.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Before using LaunchDarkly, we had custom services with config tables for feature control. These were difficult to maintain, and there were higher risks of causing issues in production. LaunchDarkly provides a more user-friendly interface and control.
How was the initial setup?
The initial setup process was straightforward, assisted by good documentation provided on their site.
What was our ROI?
The ability to avoid rollbacks saves a significant amount of time during deployments, leading to a more efficient development process.
What's my experience with pricing, setup cost, and licensing?
LaunchDarkly is a licensed version and not free. I am not aware of the specific costs or billing details.
Which other solutions did I evaluate?
We considered using Firebase. Ultimately we did not implement it.
What other advice do I have?
You can achieve smooth releases with LaunchDarkly while maintaining control over them. It helps avoid compliance issues by allowing feature adjustment at any time.
I'd rate the solution nine out of ten.
Improving task visibility control with error prevention features
What is our primary use case?
I have been using LaunchDarkly for more than one year due to the nature of my projects. Whenever we want to avoid multiple builds, we use a flag to enable future changes in the production environment.
How has it helped my organization?
LaunchDarkly allows us to control deployments without multiple builds. It enables us to show the status of tasks to clients when necessary, and when a task is not complete, we can prevent it from being visible by turning off the flag.
What is most valuable?
The ability to turn off a flag is crucial when a task is not complete, especially if there is an error in a commit. This feature ensures that uncompleted tasks are not shown to clients.
What needs improvement?
Right now, no improvements are needed. In the future, after further analysis, if I have any concerns, I may change my mind.
For how long have I used the solution?
I have been using LaunchDarkly for more than one year.
What do I think about the stability of the solution?
I have not faced any issues with the stability of LaunchDarkly.
What do I think about the scalability of the solution?
I just used it for one feature. I need to analyze fully in LaunchDarkly and review the documentation. If I have any concerns, I will let you know.
How are customer service and support?
I don't have an idea about the support team as I didn't have to contact them or open a ticket.
How would you rate customer service and support?
Neutral
How was the initial setup?
The initial setup was straightforward and not complex.
What's my experience with pricing, setup cost, and licensing?
I do not know the cost of LaunchDarkly as it was implemented offshore. I am not aware of its pricing or whether it is a free or paid source.
What other advice do I have?
I would recommend LaunchDarkly for projects with multiple builds. If you wrongly commit tasks, turning off the flag ensures features do not show up for the client.
I'd rate the solution seven out of ten.
Feature management simplified with intuitive UI and seamless integration
What is our primary use case?
I have been working for the client Windstream, which is an enterprise platform where we develop an Appysuit application. We are testing new features without releasing them to all customers, instead releasing to selected customers. I use LaunchDarkly for feature enabling and disabling.
What is most valuable?
The main feature I value is the user-friendliness, especially the flag enabling and disabling. The API integration is also impressive. I appreciate the UI which allows easy enabling and disabling of flags.
What needs improvement?
I have used LaunchDarkly for around two and a half years and I haven't faced any issues with it.
For how long have I used the solution?
I have been using it for two and a half years.
What do I think about the stability of the solution?
Performance-wise, it's very good. It has never gone down in the two and a half years of use. The server has been very stable.
What do I think about the scalability of the solution?
LaunchDarkly is very good for scalability and makes scaling up easy.
Which solution did I use previously and why did I switch?
I did not use any previous solution.
How was the initial setup?
The setup is easy. It is just a click and it provides three environments for development, UAT, and production. It's easy to manage all environments.
What's my experience with pricing, setup cost, and licensing?
Pricing is all handled by my project manager; I don't have any costing information.
Which other solutions did I evaluate?
I did not look into any alternatives.
What other advice do I have?
I would suggest using LaunchDarkly if the application is complex and you have to test many features for future purposes, particularly for enterprise applications. For small applications, I would not suggest using LaunchDarkly. It's easy to use, easy to integrate, and user-friendly.
I'd rate the solution eight out of ten.
Enables us to target users and control what needs to be visible on their screens but it sometimes breaks down
What is our primary use case?
We use LaunchDarkly for managing feature flags. It helps manage the keys to control what users view on our screens.
How has it helped my organization?
By managing the feature flags, we can target users and control what needs to be visible on their screens.
What is most valuable?
I like that it offers the ability to control the flags.
What needs improvement?
We need experience to use it, and the initial setup can be difficult. Also, sometimes it has breakdowns.
I would rate LaunchDarkly a seven out of ten.
For how long have I used the solution?
I have been using it for almost two years.
What do I think about the stability of the solution?
Sometimes it has breakdowns.
What do I think about the scalability of the solution?
It is easily scalable.
How was the initial setup?
The initial setup is a bit difficult.
What's my experience with pricing, setup cost, and licensing?
I consider the pricing to be high.
What other advice do I have?
I would recommend new users to use LaunchDarkly because of its advantages.
UI interface is very user friendly
What do you like best about the product?
The ease that I'm able to navigate around the UI and find what I want with having to search an alternate site. It's very easy to configure new settings.
What do you dislike about the product?
Nothing I can currently think of pertains.
What problems is the product solving and how is that benefiting you?
The team is able to hide features to prod which allows us to deploy to prod early and not have to hold back features in different branches.
Overall, experience clear benefits from the product
What do you like best about the product?
My team releases firmware for an embedded product with a relatively slow cadence (months between releases). LaunchDarkly allows us to include riskier features faster with the option to roll them out slowly and disable them or tweak operating parameters if issues are discovered. It's very nice to be able to make configuration changes via LaunchDarkly as well without having to release new firmware.
What do you dislike about the product?
There seem to be some gaps in the approval process for making production changes. It's possible this has been fixed and I'm not aware, but I know we've had issues in the past where we've enabled required approval for production changes to flags, yet users have been able to create brand new flags and bypass the approval process.
What problems is the product solving and how is that benefiting you?
LaunchDarkly helps us release features faster and with less risk of user impact. It also allows us to be more flexible in how we configure our software for different use-cases, including enabling features for different user-bases (beta testing, firmware versions, hardware platforms, etc.)
Launch Darkly is a great service to toggle any feature
What do you like best about the product?
1. It's a great tool for toggling features.
2. You can easily roll out or block a feature for specific customers without any hassle.
3. I use it daily, and it works smoothly with minimal impact on API latency.
4. Setting up a new LD flag takes only a minute.
5. It provides a rich SDK to integrate with Launch Darkly easily.
2. You can easily roll out or block a feature for specific customers without any hassle.
3. I use it daily, and it works smoothly with minimal impact on API latency.
4. Setting up a new LD flag takes only a minute.
5. It provides a rich SDK to integrate with Launch Darkly easily.
What do you dislike about the product?
Nothing as such. Segments and Release features can be simplified.
What problems is the product solving and how is that benefiting you?
I'd point out two major problems that LD solves for my case,
1. We don't need to think about beta release to a small portion of customers. Just need to put the feature behind LD flag and control the flag from LD dashboard. That's it.
2. When we launch a new feature, we always put that feature behind LD flags. So that if something goes wrong, we don't need rollback anything in a hurry. Just toggle the LD flag by a single click. That would do the job.
1. We don't need to think about beta release to a small portion of customers. Just need to put the feature behind LD flag and control the flag from LD dashboard. That's it.
2. When we launch a new feature, we always put that feature behind LD flags. So that if something goes wrong, we don't need rollback anything in a hurry. Just toggle the LD flag by a single click. That would do the job.
Easy Launchdarkly Feature Flags
What do you like best about the product?
We have been using Launchdarkly feature flags for about 3 years now. We have been using them to run experiments, or as kill switches for various features. I would say, that they are straightforward to use. One thing that I like is how LaunchDarkly creates an event stream with the user's browser, and the value of the feature flag gets updated on all the clients as soon as you update the value of the feature flag.
We use it for almost every new feature that we build in the product, and we have easily integrated it with our MobX Library that is used for global state management, and it makes the integration even more simpler for the developers.
We use it for almost every new feature that we build in the product, and we have easily integrated it with our MobX Library that is used for global state management, and it makes the integration even more simpler for the developers.
What do you dislike about the product?
The new UI that LaunchDarkly recently launched for feature flagging is not something that I like, I had built muscle memory for using the tool hence it has become a little tough for me to use it.
What problems is the product solving and how is that benefiting you?
- We use it to experiment with a new feature, and get analytics out of it before launching it for the entire user base.
- We are able to partially launch a feature to a subset of users, as we can very easily target to subset of users on the Product very easily using LaunchDarkly.
- Since LD uses an event stream, which modifies the value of the flag in the product as soon as it is updated from the LD Dashboard (without the need to refresh the page). We use use LD as a kill switch for features in which we not very confident about the implementation. With LD we are easily able to kill the code if anything goes south in real-time.
- We are able to partially launch a feature to a subset of users, as we can very easily target to subset of users on the Product very easily using LaunchDarkly.
- Since LD uses an event stream, which modifies the value of the flag in the product as soon as it is updated from the LD Dashboard (without the need to refresh the page). We use use LD as a kill switch for features in which we not very confident about the implementation. With LD we are easily able to kill the code if anything goes south in real-time.
Using Launch Darkly to Control Features
What do you like best about the product?
I personally like how clean the UI is. You're able to see multiple configurations for a given flag in a relatively easy to use UI
What do you dislike about the product?
It's difficult to see different evaluations on a given feature flag between different configurations
What problems is the product solving and how is that benefiting you?
It is allowing us to rollout features on a percentage basis, allowing us to incrementally increase load on a new flow without the risk of a small bug causing huge widespread issues
showing 101 - 110