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.

Reviews from AWS customer
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Easy to use Feature Flag Management
Feature flag functionality works perfectly
Deprecating flags is a little less straightforward than it should be
Running beta features
- Mark review as helpful
LaunchDarkly is a good tool for some
Separate your deploys from rollouts
Feature Flag Galore
Lets us release and deploy software faster
- Ability to easily do A/B testing
- Deploy software faster while our QA teams catch up to testing
- Target different market segments efficiently with user profiles
- Feature Management - we create features earlier and enable them when customers are ready to accept them
Shorter time to production for new features
Launch Darkly is a really good tool
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
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.