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
627 reviews
from
and
External reviews are not included in the AWS star rating for the product.
New LD customer
What do you like best about the product?
Having one place to manage feature flags and experiments.
What do you dislike about the product?
It can be hard for us to measure results using their onboard tools without a longer experiment adjustment period
What problems is the product solving and how is that benefiting you?
Deploying and managing tests more frequently
Good tool for managing feature flags.
What do you like best about the product?
1. Allowing business users to field-test new features in production before enabling them for clients.
2. Enabling gradual rollouts for high-risk features, minimizing potential impact if issues arise.
3. Decoupling feature releases from development and deployment, so developers can merge tested features while product teams control when they go live.
2. Enabling gradual rollouts for high-risk features, minimizing potential impact if issues arise.
3. Decoupling feature releases from development and deployment, so developers can merge tested features while product teams control when they go live.
What do you dislike about the product?
Nothing really. It does good job managing feature flags. We only use it for feature flags, so can't comment on other features.
What problems is the product solving and how is that benefiting you?
It allows the business to validate features in production environment before enabling such feature for Clients/Users.
It also ads the ability to deploy a new feature gradually, to beta tester clients first and then simply toogle the flag to enable that feature for other users.
Engineers don't need to worry about feature release schedule if a feature is behind a feature flag. This helps with continous integration/deployment practices. Business can decide when to enable features by managing feature flags.
It also ads the ability to deploy a new feature gradually, to beta tester clients first and then simply toogle the flag to enable that feature for other users.
Engineers don't need to worry about feature release schedule if a feature is behind a feature flag. This helps with continous integration/deployment practices. Business can decide when to enable features by managing feature flags.
Good and easy to use to improve efficiency and product quality
What do you like best about the product?
First thing I will go to when we need to roll out a feature or to control the access to a specific feature. The UI is also very easy to use.
What do you dislike about the product?
You cannot schedule the feature flag to turn on / off at a specific time (maybe there is a way but not with our subscription level?)
What problems is the product solving and how is that benefiting you?
Targeting users/clients for A/B testing. Selecting users in the beta test phase during the rollout. Last but not the least, target only users with certain permission to access specific feature. It helps save much time in developement and TTM.
Easy to use Feature Flag Management
What do you like best about the product?
User segments are very useful and powerful for targetting
Feature flag functionality works perfectly
Feature flag functionality works perfectly
What do you dislike about the product?
The web app can be a bit quirky and buggy sometimes
Deprecating flags is a little less straightforward than it should be
Deprecating flags is a little less straightforward than it should be
What problems is the product solving and how is that benefiting you?
Launching code into production and being able to control and manage its roll out
Running beta features
Running beta features
Separate your deploys from rollouts
What do you like best about the product?
The ease of use of creating flags that are separating our feature rollouts from deployment is the largest factor of our use case. Implementation is a simple library and we're able to integrate it into each of our apps easily.
What do you dislike about the product?
There are still some cultural issues of utilizing LD's flags when we probably didn't need to which adds more complexity to a system.
What problems is the product solving and how is that benefiting you?
The separation of features from deployment and understanding the reason for degredation or improvement is how it benefits us the most right now.
Lets us release and deploy software faster
What do you like best about the product?
- Ease of use via the SDK
- 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
- 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
What do you dislike about the product?
- Generally about feature flags: There is always technical debt to take care of
What problems is the product solving and how is that benefiting you?
- Faster deployments
- Feature Management - we create features earlier and enable them when customers are ready to accept them
- Feature Management - we create features earlier and enable them when customers are ready to accept them
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.
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.
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.)
showing 61 - 70