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.
LaunchDarkly
LaunchDarklyExternal reviews
705 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Feature management simplified with intuitive UI and seamless integration
What is our primary use case?
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.
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.
Great for mitigating risk for big rollouts and for experiments
What do you like best about the product?
Big launches could be done in percentage rollouts, reducing risk of breaking key functionality in production. We use it for every new feature release.
What do you dislike about the product?
The recent UI redesign made it less user friendly, unclear what the benefit of that redesign was.
What problems is the product solving and how is that benefiting you?
We need to release big features with confidence, but also mitigating risk at the same time. Percentage rollouts help a lot with this.
Deliver timely software with the least amount of risk
What do you like best about the product?
Many of our software deployments are behind LaunchDarkly's feature flags to ensure that the consumers of our APIs have consistant experience. Due to many dependencies, we are unable to guarantee when the clients can update their software. Often when there are issues it will be up to our backend teams to resolve.
What do you dislike about the product?
While the positives outweigh the negatives, the flexibility and risk mitigation is favored over the technical debt of cleaning up older flags.
What problems is the product solving and how is that benefiting you?
Launch Darkly allows us the flexibility to turn on and off features, as well as silently deploying features for the future.
Excellent so far, the new UX is way better and modern. Enables our company to ship with confidence.
What do you like best about the product?
The UX - That's really the big value add for me. All the data you can get to help you take informed decisions.
The rollout functionality is a real game changer for us, especially as we scale.
The rollout functionality is a real game changer for us, especially as we scale.
What do you dislike about the product?
More like a feature request really - because we use Launch Darkly SDK in all our products, it would be nice to have a way to let our customers turn on and off some flags so they can beta try new features.
What problems is the product solving and how is that benefiting you?
* Launch with confidence - the stagged roll out is really helping there
* Powers our A/B testing engine - we augment data with our own tools but LD provides the base.
* Let customer self serve some flags so they can try out beta feaatures
* Powers our A/B testing engine - we augment data with our own tools but LD provides the base.
* Let customer self serve some flags so they can try out beta feaatures
Launch Darkly Feature Flags
What do you like best about the product?
The ease of creating and processing feature flags in Launch Darkly. They make it easy to protect our work before releasing to production. Love being able to see different environments all at once.
What do you dislike about the product?
At first I disliked how when turning flags on/off it wasn't as easy before. Now I have gotten use to it.
What problems is the product solving and how is that benefiting you?
We are able to protect our development work from being released to different environments before we are ready to be released.
New update enables comprehensive feature management
What is our primary use case?
Our developers are using LaunchDarkly. I am using it to turn on features.
What is most valuable?
Recently, I like this new update where we can see and manage everything through it. Also, from the development side, it allows us to manage multiple things. Additionally, I like the services provided, like managing through the internet on and off.
What needs improvement?
As of now, I do not see much room for improvement. The feature where one feature flag is dependent on another could be explored more for our usage.
For how long have I used the solution?
I have used it for almost two years.
What do I think about the stability of the solution?
Sometimes it breaks down. Only last week, we were getting a 500 error.
What do I think about the scalability of the solution?
Users can easily scale up or down.
How are customer service and support?
I have not contacted their support team for any reason.
How was the initial setup?
The initial setup is easy.
What's my experience with pricing, setup cost, and licensing?
I am not sure about the pricing or setup costs. It is all handled by our organization.
What other advice do I have?
You can manage through the reach of flags for different credential regions. You can turn on or off features for different environments. This is pretty useful.
I'd rate the solution nine out of ten.
showing 111 - 120