LaunchDarkly

What do you like best about the product?

I really liked how easy it was to use the session feature to prepare for a customer meeting. Being able to quickly find customer sessions and anticipate their questions made my preparation much better. The ability to see what customers did in the app is priceless for our support and engineering teams. Integration of the SDK into our codebase was straightforward, and every question we had was answered promptly by the LD team—excellent support.

What do you dislike about the product?

Except for a single minor caveat (was quickly resolved), the session experience has been smooth. Logs and network request tools are still largely unexplored internally, and we plan to expand usage once Flutter observability becomes available for mobile.

What problems is the product solving and how is that benefiting you?

Gradual feature rollout and continues delivery of work in progress features guarded by feature flags.
With observability features - identifying errors before reported, better inside into user journey and preparation for client meetings

What do you like best about the product?

• Easy setup of feature flags with a developer-friendly interface
• Powerful targeting rules and progressive rollout capabilities
• Useful for A/B testing and internal testing scenarios
• Good documentation and SDK support across multiple platforms

What do you dislike about the product?

• Flag cleanup and lifecycle management can be painful. As flags accumulate over time, tracking unused or deprecated ones becomes tedious. There are features and integrations in launch darkly that make this easier but still requires user interactions to make it a safe process.

What problems is the product solving and how is that benefiting you?

LaunchDarkly allows us to get features into production in smaller chunks and allows us to internally test features before releasing it for public consumption. It allows us to move faster and feel safer when launching new features.

What do you like best about the product?

Ease of use, being able to rollout new features on the fly

What do you dislike about the product?

It is expensive compared to alternatives due to per seat pricing model

What problems is the product solving and how is that benefiting you?

Launching new features using feature gates that can be enabled to a certain set of users for our product.

What do you like best about the product?

The key handling for each environment and predefined endpoints at LaunchDarkly makes it easy to get started.

What do you dislike about the product?

The user experience is confusing. In which menu I can find things is not intuitive. The rule set works but I can't point a customer here since a customer will need a separate UI with simple toggles, maybe an idea could be to be able to generate custom UIs from rule sets. I also want to be able to have a key casing convention for UPPER_SNAKECASE which is the most common one used for environment variables, since I want to be able to replace environment variable settings with feature flags if they exist. The "hello world" setup for Launch Darkly is not something you would want to use in production, so it would be good is there was more framework related setup done. The setup in ASP.NET core for reading in feature flags as options could have been provided by I library for ease of use, instead of me having to develop the code myself. There also seems to be a lack of tutorials on YouTube which gives the impression that this is not a product commonly used. When entering the webpage I would expect to get online help interactivly showing what the product can do, instead of just showing unfamiliar terms in my face. I do not like the need to wait for sampled data from the user before being able to setup a rule against that user, I would want to be able to have a predefined rule sets even without anyone having made a call to Launch Darkly. My favorite environments keep disappearing so I have to add them again every time I login.

What problems is the product solving and how is that benefiting you?

Its helping me allow customers to try out features in production by toggling them on and off.
It is probably overkill and It would be beneficial to be able to configure the actual features I am able to see since most will never be used.
It would also be good to be able to show the customer a simpler interface with the limited ability to just toggle features, that was adaptable to mobile screens etc.

What do you like best about the product?

The ability to enable or disable feature flags at the cluster level.

Fine-grained control to toggle feature flags at the namespace level within a cluster.

Role-based authorization, allowing admins to define who can manage flags in environments like pre-prod and prod.

Support for multiple targeting rules per flag, enabling more complex rollout strategies.

Well-defined default states for flags, ensuring predictable behavior when rules don’t match.

The ability to tag flags by feature or team, making them easier to organize and manage.

What do you dislike about the product?

The search experience for feature flags could be improved. Currently, if I need to search for multiple flags, I have to open multiple sessions or tabs. The interface doesn't allow simultaneous searches unless the flags are already tagged or filtered together.

It would be helpful to enable bulk editing or bulk tagging of feature flags across multiple environments.

When a flag has multiple rules, the UI can become cluttered. A more intuitive rule builder or rule grouping would improve usability.

What problems is the product solving and how is that benefiting you?

In our project, LaunchDarkly provides critical control over feature enablement across different clusters and namespaces, allowing us to:

Quickly enable or disable features in specific clusters or namespaces without requiring new deployments.

Use RBAC (Role-Based Access Control) to control who can manage feature toggles in environments like dev, pre-prod, and prod, enhancing governance and security.

Integrate with our CI/CD pipelines to automate flag updates as part of the deployment process, reducing manual effort and human error.

Run experiments and A/B tests within targeted namespaces to validate new features before a broader rollout.