LaunchDarkly Reviews & Product Details

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

I appreciate how LaunchDarkly has become an essential part of our software delivery process, allowing us to manage feature flags and perform progressive rollouts confidently. The setup process was very straightforward, with clear documentation and easy integration of SDKs. Using LaunchDarkly significantly enhances our release management and risk reduction strategies while facilitating cross-team collaboration. One of the standout benefits is the ability to roll out features gradually, test changes, and roll back instantly if needed without disrupting our customers or requiring a redeploy. I find the feature complete nature of the service for managing feature flags, along with its impressive analytics capabilities, extremely valuable. These features bolster our decision-making process, enabling us to make smarter decisions around feature availability and customer segmentation. Additionally, I find the ease of use of the platform compelling, and it significantly contributes to why I would consider buying LaunchDarkly again. Review collected by and hosted on G2.com.

I would add more capabilities to flag organization - having more filters available to keep flags organized across segments. Review collected by and hosted on G2.com.

I use LaunchDarkly for feature rollout plans, controlling a particular feature, and rolling back changes while on-call. It gives me an assurance about which feature broke something or didn't, making me feel safe in the head. I love the dependent flags feature because it eliminates the need to communicate with the other team about going live, as I can just make it a dependent flag. Additionally, authoring history is a must-have for me as it allows me to see who turned a feature on or off and investigate the associated ticket. The initial setup of LaunchDarkly was straightforward. Review collected by and hosted on G2.com.

I believe long back when using dependent flag, there was a small inconsistency that the parent flag had to be rolled out before my flag but not sure it maybe mentioned in the docs now. Other than that I have no issues. Review collected by and hosted on G2.com.

I greatly appreciate LaunchDarkly for its ability to efficiently manage feature flags for customer instances. It provides a quick and seamless way to enable or disable application functions, which is incredibly valuable for managing dynamic customer requests, such as enabling AI services. The feature history tracking is another fantastic aspect, allowing me to see past changes made to each feature flag, contributing to better management and oversight. Additionally, the initial setup was remarkably straightforward, thanks in part to the support provided by the LaunchDarkly team. Their guidance made the process smooth and hassle-free. Review collected by and hosted on G2.com.

There is nothing that I dislike about LaunchDarkly Review collected by and hosted on G2.com.

I really like how LaunchDarkly is super easy to use, especially with the change log for each feature flag. It's like a git repo, allowing us to see who's edited it and when, which is super helpful and intuitive for our workflow. It was also super easy to set up; our front-end engineer did it in a day. LaunchDarkly makes managing feature flags for our different customers very convenient. Review collected by and hosted on G2.com.

When I'm editing a feature flag, I always have to type the word 'production' or 'development.' For production, I feel like that's necessary, but for a dev environment, it doesn't seem like we should have to do that all the time. That's the main complaint. I also find LaunchDarkly a little difficult to navigate. Our entire organization uses LaunchDarkly, and finding our specific team's feature flags is a bit of a puzzle if I start at the beginning. Review collected by and hosted on G2.com.

One of the standout features is how flexibly and simplicity it lets teams manage releases, whether that's by targeting specific users or gradually rolling out changes to a set percentage of users. This level of control is a significant advantage. I also appreciate being able to add tags to feature flags, which makes it much easier to monitor how many feature flags each team is using.

Another highly valuable capability is tracking the evolution of feature flags evaluations over time. Additionally, having tags that indicate when a flag is ready to be removed or archived is extremely helpful for keeping things organized and tidy. Review collected by and hosted on G2.com.

There have been some recent changes to the UI related to the FF archiving process, which have introduced a bit of additional confusion. Other than that, I don't have many issues to report. Review collected by and hosted on G2.com.

I like that LaunchDarkly is really simple to utilize when it comes to adding or removing users from pilot groups. It makes segmenting users easy and scheduling releases is straightforward as well. I appreciate the quick updates that instantly take effect in our code. For someone like me who is not technically inclined, it's been really simple to use and understand. Additionally, my initial setup when I joined the user base was very simple, and I was able to grasp how it works easily. The layout seems simple too, which I find helpful. Review collected by and hosted on G2.com.

I find that there's a lot of extra typing needed when you have to retype the segment name to make something work. It feels like unnecessary copying and pasting when adding or removing users. It would also be nice if I could take our database and, instead of copying over a user number, associate it with an email ID. I'm not sure if that's a limitation of LaunchDarkly or how we set it up. Review collected by and hosted on G2.com.

The best part about LaunchDarkly is how easy it makes the feature flagging and gradual rollouts of features. It allows my team to work on multiple different features at the same time without worrying about risky deployments to production. I can push a new feature behind a flag and keep it OFF until the feature is ready to go live. I also liked how easy it was to integrate it with our existing codebase and tech stack. Really a game changer Review collected by and hosted on G2.com.

I think the main drawback which our team felt was the pricing plans. It felt a bit high especially considering for smaller teams. Also, sometimes the UI can be a bit confusing when handling a large number of flags in various different environment. It took a bit of time to get used to. But once we were familiar with it, it works well! Review collected by and hosted on G2.com.

I think the UI of LaunchDarkly is very intuitive and powerful, especially for feature flags. It makes it very easy to feature gate and customize each flag not only with boolean values like true or false, but also with custom values. This flexibility in configuring for different environments, like testing and production, is very valuable to me. Additionally, the onboarding process was very easy. Review collected by and hosted on G2.com.

I don't think of anything significant, but maybe more documentation and training and also on best practices would be good. I might have missed this if this already existed somewhere out there. Review collected by and hosted on G2.com.

I find LaunchDarkly extremely beneficial for our feature flagging needs, as it provides robust feature control and simplifies configurations. I love how easy it is to configure and use, making it straightforward for my team to implement any changes swiftly without much complexity. I particularly appreciate the ability to conduct gradual rollouts, which allows us to manage feature releases efficiently and minimize risk. This capability, paired with the power to gate releases and create targeted configurations, helps us isolate features to specific geographies or user segments, which is crucial for compliance and targeted user experiences. The functionality to create custom segments and tailor targeting rules empowers us to manage our user base with high precision. Additionally, our use of both client and server SDKs with LaunchDarkly enhances our flexibility in deployment across different environments. The initial setup also presented no hurdles for us, as it was pretty simple to understand, reinforcing the platform's user-friendly nature. Review collected by and hosted on G2.com.

I dislike the 10,000 user limit on Segments. Even though there is a feature for Big Segments, the migration and usage from standard Segments to Big Segments is not straightforward. Additionally, creating a persistent store in our infrastructure to support Big Segments is an overhead that I find burdensome. This additional requirement is something we just don't want to undertake. Review collected by and hosted on G2.com.