LaunchDarkly Reviews

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 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.

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.

Fetching information about multiple flags in a single action would be beneficial. Additionally, incorporating some analytics on LaunchDarkly would enhance its functionality.

I have been using LaunchDarkly for more than one year.

I have noticed stability issues in terms of backend performance, such as delays.

LaunchDarkly is scalable; however, there are areas they could improve on to enhance scalability further.

I haven't yet needed to use customer service, however, support is available for raising questions or queries if necessary.

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.

The initial setup process was straightforward, assisted by good documentation provided on their site.

The ability to avoid rollbacks saves a significant amount of time during deployments, leading to a more efficient development process.

LaunchDarkly is a licensed version and not free. I am not aware of the specific costs or billing details.

We considered using Firebase. Ultimately we did not implement it.

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.

We use LaunchDarkly for managing feature flags. It helps manage the keys to control what users view on our screens.

By managing the feature flags, we can target users and control what needs to be visible on their screens.

I like that it offers the ability to control the flags.

We need experience to use it, and the initial setup can be difficult. Also, sometimes it has breakdowns.

I would rate LaunchDarkly a seven out of ten.

I have been using it for almost two years.

Sometimes it has breakdowns.

It is easily scalable.

The initial setup is a bit difficult.

I consider the pricing to be high.

I would recommend new users to use LaunchDarkly because of its advantages.

I have been using LaunchDarkly for more than one year due to the nature of my projects. Whenever we want to avoid multiple builds, we use a flag to enable future changes in the production environment.

LaunchDarkly allows us to control deployments without multiple builds. It enables us to show the status of tasks to clients when necessary, and when a task is not complete, we can prevent it from being visible by turning off the flag.

The ability to turn off a flag is crucial when a task is not complete, especially if there is an error in a commit. This feature ensures that uncompleted tasks are not shown to clients.

Right now, no improvements are needed. In the future, after further analysis, if I have any concerns, I may change my mind.

I have been using LaunchDarkly for more than one year.

I have not faced any issues with the stability of LaunchDarkly.

I just used it for one feature. I need to analyze fully in LaunchDarkly and review the documentation. If I have any concerns, I will let you know.

I don't have an idea about the support team as I didn't have to contact them or open a ticket.

Neutral

The initial setup was straightforward and not complex.

I do not know the cost of LaunchDarkly as it was implemented offshore. I am not aware of its pricing or whether it is a free or paid source.

I would recommend LaunchDarkly for projects with multiple builds. If you wrongly commit tasks, turning off the flag ensures features do not show up for the client.

I'd rate the solution seven out of ten.