LaunchDarkly Reviews

LaunchDarkly has allowed us to deploy code into production on a regular basis and then enable release on demand to different segments of our customers (or all of them) on our schedule and not when the code is deployed. If something is wrong, instead of spending costly time rolling things back we can simply turn off the feature flag and hide the error from our customers and then fix it behind the scenes. This allow allows us to test it in production without impacting production. Highly recommend taking the steps needed to enable feature flags in your code and then utlizing LaunchDarkly to quickly manage who can see what in your applications.

The only thing that would be nice to have in LaunchDarkly would be a one click button after something was approved for rollback that would quickly undo what was done.

LaunchDarkly allows us to go to production quickly, enable a slow rollout to different customer segments, quicker rollbacks than rolling back code, and supportability - if we turn off the feature flag we can enable it for people to then go in and see what the actual problem was and fix any defects in real time without impacting our customers. It is amazing how many things are easier to fix if the problem still exists but it is now hidden vs rolled back and the developer is unable to see the logs / issue in action.

.controlling the features post release of software

failure tracking of the calls are not proper

Controlling the features post release incase of any regressions

User splitting is very clear and the dashboard is clean, easy to use, and the SDKs work well across platforms

Sometimes the SDK setup feels a bit complex, particularly with multiple environments and custom contexts. The documentation, while detailed, could be clearer with more real-world examples.

By using feature flags, we can test new features with specific users, run A/B tests, and turn off features instantly if something breaks. This means fewer production issues, faster feedback, and more control over our releases.

.Ease of use and the flexibility it gives us in engineering work

It's very expensive so certain features we debate keeping

Feature flagging new features and running

Runtime config change without need of deployment of a service

There is nothing that I dislike as such. However I think the number of org members are very limited. We can increase that to a much higher number

Runtime configuration change is the much needed feature for any application/service for fast mitigation or launching any feature

The "feature flags" creation for any design and development of the product. Each individual working on same project can crete their respective feature flag and that makes the development environment faster. .

Nothing as such. But by creating a different feature flag. Its good if we can create with their own respective ID. Because when we move to production we have to change the other peoples created feature flag into one single name.

Its keeps track of different features and changes in the design of the product with one single codebase branch. Its like a verison control system for the product featutre level. It helps the team to work on one sigle branch and avoid the conflicts.

It is easy to use, configure and integrate, supports almost every platform for integration and a big set of targets without major performance issues

With the new UI it was kind of hard to find my way around, but with time a get used to it.

M

We like the ability to manage our staging and production environemnts and to create different segments to manage the roll out of new features.

you do have to create the segments for each envornmnet instead of sharing them.

It allows us to work on new features with focus groups and get them right before we launch them to everyone.

LD is Easy, Practical and Functional All At The Same Time. You MUST have this at reach to help in you daily tasks, even if you're not a programer you are abke to create Complex Integrations with almost Any Softeare Out There creatong functional implementations esasyly. I use it ALMOST DAILY and our DEV Team surely uses it more frequently than me. Customer Support is easily at reaach and always respond fast.

Nothing... For Me Is PERFECT! I ALWAYS get the funtionality with a pair of mouse clicks thanks to the solid contruction of LD that let our Dev teams to build easy to use intgations and soft lauches of new functionalities of our software witth an easy to use interfase for us the final non technical users.

Our

I've heard engineers talk about how easy it is for them to put new features behind a feature flag in Launch Darkly. From the product side, its super easy to create segments of users. This has improved the way we manage our Alpha, Beta, and GA releases. I'm currently leading a huge intiative at the moment; I can not imagine doing this effectively without LD.

Their zapier integration is limited. We were attempting to completely automate our beta process leveraging Launch Darkly + Hubspot forms. We failed to do so because LD's zapier integration doesn't support Segments. We are exploring leveraging their public API to build a custom solution.

It has helped us do a few things better. 1. We manage alpha and beta releases more effectively. 2. We hav avoided massive outages by leveraging percentage based rollouts 3. It has helped us reduced the risk of launching large features or intiatives in our customer.