LaunchDarkly
LaunchDarklyExternal reviews
677 reviews
from
and
External reviews are not included in the AWS star rating for the product.
LaunchDarkly: Review of Feature Flag Management and Governance
What do you like best about the product?
This is the most critical feature for preventing "flag debt." LaunchDarkly's Flag Health dashboard and code reference detection (via integrations like GitHub) provide confidence when deleting flags.
Strong Audit Logging ensures accountability and compliance, showing flag creation, modification, and environment changes.
The ability to Archive and Restore flags is excellent for managing cleanup while retaining a safety net.
The intuitive Rules Engine allows complex, multi-variate targeting using visual blocks (the "if and elses").
LaunchDarkly uses a decentralized, CDN-based architecture to ensure low-latency flag delivery and high uptime, meaning flag checks don't slow down your application.
The platform integrates flag delivery with statistical analysis, making it easy to turn a feature rollout into a measurable experiment.
Strong Audit Logging ensures accountability and compliance, showing flag creation, modification, and environment changes.
The ability to Archive and Restore flags is excellent for managing cleanup while retaining a safety net.
The intuitive Rules Engine allows complex, multi-variate targeting using visual blocks (the "if and elses").
LaunchDarkly uses a decentralized, CDN-based architecture to ensure low-latency flag delivery and high uptime, meaning flag checks don't slow down your application.
The platform integrates flag delivery with statistical analysis, making it easy to turn a feature rollout into a measurable experiment.
What do you dislike about the product?
While the flag configuration is easy, integrating the SDK across multiple programming languages and environments can still take time and careful planning.
This is a very common piece of feedback. While you get the final flag value, drilling down into why a specific user got that value requires digging or the information is not present/visible
This is a very common piece of feedback. While you get the final flag value, drilling down into why a specific user got that value requires digging or the information is not present/visible
What problems is the product solving and how is that benefiting you?
You can instantly turn off a buggy feature in production without rolling back code. This drastically reduces your Mean Time to Restore (MTTR) and prevents customer-facing outages, saving reputation and engineering time (especially at 2 a.m.).
Developers can merge and deploy code continuously (multiple times a day) into the main branch, keeping the feature hidden behind a flag. This reduces merge conflicts and allows Product/Marketing teams to choose the perfect business moment for the feature release, independent of engineering cycles.
You can safely test new code in production with a small, internal group (Canary Release) or a specific user segment. This reduces the "blast radius" of any bug and allows you to catch performance issues before they affect the general user base.
You can tailor the user experience by enabling features only for specific customer tiers, geographies, or subscription types. This allows for personalized product experiences and monetization (selling access to Premium/Beta features) directly from the platform.
Developers can merge and deploy code continuously (multiple times a day) into the main branch, keeping the feature hidden behind a flag. This reduces merge conflicts and allows Product/Marketing teams to choose the perfect business moment for the feature release, independent of engineering cycles.
You can safely test new code in production with a small, internal group (Canary Release) or a specific user segment. This reduces the "blast radius" of any bug and allows you to catch performance issues before they affect the general user base.
You can tailor the user experience by enabling features only for specific customer tiers, geographies, or subscription types. This allows for personalized product experiences and monetization (selling access to Premium/Beta features) directly from the platform.
Clear and Intuitive User Interface
What do you like best about the product?
The user interface is clear, making it easy to navigate, and the roll-out features are particularly convenient and useful. It's also very user-friendly to implement a feature flag.
What do you dislike about the product?
For operations not covered by the SDK (Java), the API SLOs aren't trustable.
What problems is the product solving and how is that benefiting you?
We are using progressive roll-out feature and feature flag to protect our features launches.
Easily Manage Feature Flags, Needs Bulk Rule Import
What do you like best about the product?
I really enjoy using LaunchDarkly for its feature flags, which make it incredibly easy and user-friendly to enable or restrict access to features for specific clients or user groups. As a product manager, the user interface is intuitive, which significantly simplifies my workflow. I'm especially fond of the custom segment role capability that LaunchDarkly offers, allowing us to apply very specific, bespoke client setups and manage rules at a granular level. This feature is particularly beneficial for our needs as we often require detailed configurations, and it helps our teams target people, user groups, or roles with minimal hassle. Overall, the customization options within LaunchDarkly empower us to meet our unique workflow requirements and deliver tailored services to our clients.
What do you dislike about the product?
While LaunchDarkly's capability to create highly specific rules is invaluable and meets many core needs, scaling this process is quite cumbersome. Setting up these custom rules is currently a manual process, which is time-consuming when done at scale. Implementing a feature to import bulk files of these rules would be highly beneficial and time-saving. Additionally, there seems to have been an issue with the initial setup, potentially due to setting up two separate projects for the product, which might not have been the optimal choice.
What problems is the product solving and how is that benefiting you?
I use LaunchDarkly to apply feature flags for new features, enabling or restricting access at a granular level, which simplifies client management and is user-friendly. However, scaling the process is tedious without bulk import capabilities.
Essential Tool for Safe Feature Releases
What do you like best about the product?
I appreciate the good SDK and developer experience that LaunchDarkly offers, which is crucial for a smooth development process. The use of feature flags to coordinate releases, such as acting as a kill switch for critical parts, enhances operational safety by reducing incidents and response time. Additionally, I value its ability to facilitate friendly user testing of new beta features, allowing for safer experimentation. It enables us to expose beta features to specific customers or internal testers, gather feedback, and roll back instantly if something doesn't work as expected. Furthermore, LaunchDarkly allows us to safely ship code at any time without impacting users until the feature is toggled on.
What do you dislike about the product?
.
What problems is the product solving and how is that benefiting you?
We LaunchDarkly for decoupling deploy from release, safer experimentation, and operational safety. It allows us to ship code safely, conduct beta testing efficiently, and reduce incidents with kill switches for critical components.
Easy to get started & almost perfect
What do you like best about the product?
It's easy to get started and to add new flags, and it doesn't take up much of my time.
What do you dislike about the product?
I wish the diff viewer handled complex flags with JSON configurations better.
What problems is the product solving and how is that benefiting you?
Our organization manages hundreds of feature flags. We primarily use them to ship new feature experiments quickly, and targeting based on different context attributes makes it easier to measure whether the feature works as intended.
Safe, Confident Feature Deployment with LaunchDarkly
What do you like best about the product?
I use LaunchDarkly for launching new features safely, utilizing feature flags and gradual rollout features. The ability to deploy code to production with feature flags turned off, and turning them on gradually increases my confidence in releases by making it easier to rollback in case of any regression. I find percentage rollouts and targeted rollouts, which are enhanced by custom rules and contexts, incredibly useful. These features help in catching bugs and edge cases early before they escalate into incidents. The easy enable and disable functionality of feature flags significantly aids in quickly mitigating issues. Additionally, the initial setup of LaunchDarkly is very easy, contributing to a seamless integration into my workflow.
What do you dislike about the product?
There is a bit of a learning curve for the complex features in LaunchDarkly. Understanding rule precedence and creating complex custom rules requires time and practice, which can initially be challenging.
What problems is the product solving and how is that benefiting you?
I use LaunchDarkly to safely launch new features with feature flags and gradual rollouts, enhancing confidence in releases. It helps catch bugs early and manage issues quickly with easy enable/disable options, boosting overall deployment safety.
Exceptional Support and Quick Responses from the LaunchDarkly Team
What do you like best about the product?
The LaunchDarkly team responded to my questions on Slack in under a day, which shows they are eager to assist. Their replies were thorough and provided a lot of useful information.
What do you dislike about the product?
Unfortunately, some features required for my workplace were not supported by LaunchDarkly. As a result, I had to take an effort to develop a custom solution on my end.
What problems is the product solving and how is that benefiting you?
This tool is useful for managing feature flags, which supports agile development processes.
Effortless User Access Control with LaunchDarkly
What do you like best about the product?
I really appreciate LaunchDarkly's simplicity and ease of use. The interface is incredibly user-friendly and makes navigating tasks uncomplicated, which is a big advantage for me. I particularly enjoy the flags feature as it allows us to customize our systems and processes effectively, ensuring that specific projects are managed with ease while keeping an accurate count on production. Switching to LaunchDarkly from phpadmin proved beneficial as it offered specific features that better catered to our needs, including secure login features that we value highly. Additionally, the initial setup of LaunchDarkly was very straightforward, which made the transition smooth. Having the platform integrated with our system enhances overall efficiency as well.
What do you dislike about the product?
I like the ease of LaunchDarkly, however, it did take some practice adjusting to its interface from our last platform that we used for similar tasks.
What problems is the product solving and how is that benefiting you?
I find LaunchDarkly simplifies user access management, streamlining our moderation processes and enhancing feature control for our website. Its user-friendly interface and flag features also help individualize systems while maintaining accuracy in production counts.
Reliable, Fast Deployment with Easy Setup
What do you like best about the product?
I really appreciate LaunchDarkly's comprehensive tooling system, which offers far more features with minimal maintainability compared to our previous key-value store solutions. The API documentation is outstanding, enabling us to integrate and test in both local and development environments seamlessly, leading to going live swiftly in just a couple of weeks. The environment feature in LaunchDarkly is particularly useful, as it allows us to test and develop applications more rapidly. I love how it aids in faster product iteration and launch, offering the ability to quickly disable features if they underperform. The features I find most valuable include blue-green deployments, feature flags, and the capability for iterative or phased rollouts of features and A/B testing. These functionalities notably enhance our deployment speed and iteration cycles. Ultimately, LaunchDarkly is reliable, fast, and easy to use once it's set up, making it an indispensable tool in our arsenal.
What do you dislike about the product?
I experienced some challenges with the initial setup of LaunchDarkly, particularly around the initialization configurations which were somewhat confusing. Choosing between connection methods like streaming versus polling was not straightforward. Additionally, I encountered a significant downtime issue tied to an AWS us-east-1 outage, which, although not directly caused by LaunchDarkly, affected its service. Furthermore, I find the cost for service connections to be high, and I would appreciate a reduction in those costs.
What problems is the product solving and how is that benefiting you?
LaunchDarkly provides a comprehensive tooling system with more features and less maintenance than key-value stores. It helps us iterate and launch products faster, test and develop efficiently, and turn off features if needed, ultimately enhancing our deployment and iteration cycles.
Easy Feature Flagging with Usability Concerns
What do you like best about the product?
I appreciate LaunchDarkly's ease of use and the additional features it offers. The UI is excellent and makes complex flag evaluation straightforward. The configurability of feature flagging is a significant improvement over the previous solutions we used, allowing much more control and flexibility. The ability to search for contexts by name is particularly useful, making the process of toggling feature flags for specific users, projects, or companies extremely easy directly from the browser. This capability has greatly enhanced our workflow, moving beyond a simple on/off solution to a more sophisticated and user-friendly interface. Overall, LaunchDarkly's feature flagging service is the most valuable aspect for us, and it's a primary reason for our continued use and affection for the service.
What do you dislike about the product?
I find the network calls erroring out while trying to stream data to be a problematic issue, even though it hasn't impacted functionality significantly. Additionally, I'm not satisfied with LaunchDarkly's observability feature—its lack of robustness and insight, coupled with the high cost, doesn't meet my expectations. The integration of Observability and Session Replay feels overly coupled, and I don't appreciate its interference with the console. Finally, the pricing model is complicated, especially the context counting method, which makes it difficult to forecast costs.
What problems is the product solving and how is that benefiting you?
I use LaunchDarkly for feature flagging, making our process more configurable with a helpful UI and easing complex flag evaluations, improving workflow by easily searching contexts for toggling flags for specific users or projects.
showing 31 - 40