When the system has an excessive number of feature flags, managing them can become cumbersome. It would be helpful to have UI elements that make this easier, such as tracking feature flag usage, the duration that feature flags have been open, and generating reports. You need some experience to get used to it. There's a bit of a learning curve, but it is easier for people with a technical background,
LaunchDarkly currently lacks multi-region support. I strongly believe they need to develop a strategy for handling situations where LaunchDarkly goes down. They should have a backup URL and collaborate with other engineers to ensure availability. There should be a fail-over strategy in place. My understanding is that a multi-region real-time solution isn't available yet. Another future enhancement I envision is having the entire application property load through LaunchDarkly. This integration would be advantageous but needs to be designed to be very user-friendly and serviceable. I use a dashboard. I see some improvements happening, but it's a little bit cluttered. It even needs to be improved because certain kinds of levels of fields are added. So they need to make it very user-friendly, that kind of thing. So, LaunchDarkly really has to play around and make it very user-friendly. I expect certain behavior from the tool, but it gives me false results. I know I need to play around with all the properties, and then I can go to what it takes. It's not a tool that a non-technical person can use. Like, whoever is a non-technical person can also easily able to understand what they want to do; that kind of thing used to be taken as part of the dashboard (cloud dashboard), which is wherever we are enabled with your feature, like, so because If you go inside the plans, it has, like, a certain level of conditions and operations. So sometimes it works well, sometimes it doesn't work. So everyone has to understand. So, that needs to be very precise.
Build Automation streamlines software development by automating tedious tasks such as compiling code, running tests, and packaging applications. It enhances productivity, enabling developers to focus on innovation and quality improvement.This category of solutions is essential for teams that aim to improve efficiency in their software delivery pipelines. It minimizes errors and optimizes workflows by automating repetitive processes that are crucial in modern software development. Leveraging...
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.
As of now, I do not see much room for improvement. The feature where one feature flag is dependent on another could be explored more for our usage.
When the system has an excessive number of feature flags, managing them can become cumbersome. It would be helpful to have UI elements that make this easier, such as tracking feature flag usage, the duration that feature flags have been open, and generating reports. You need some experience to get used to it. There's a bit of a learning curve, but it is easier for people with a technical background,
LaunchDarkly currently lacks multi-region support. I strongly believe they need to develop a strategy for handling situations where LaunchDarkly goes down. They should have a backup URL and collaborate with other engineers to ensure availability. There should be a fail-over strategy in place. My understanding is that a multi-region real-time solution isn't available yet. Another future enhancement I envision is having the entire application property load through LaunchDarkly. This integration would be advantageous but needs to be designed to be very user-friendly and serviceable. I use a dashboard. I see some improvements happening, but it's a little bit cluttered. It even needs to be improved because certain kinds of levels of fields are added. So they need to make it very user-friendly, that kind of thing. So, LaunchDarkly really has to play around and make it very user-friendly. I expect certain behavior from the tool, but it gives me false results. I know I need to play around with all the properties, and then I can go to what it takes. It's not a tool that a non-technical person can use. Like, whoever is a non-technical person can also easily able to understand what they want to do; that kind of thing used to be taken as part of the dashboard (cloud dashboard), which is wherever we are enabled with your feature, like, so because If you go inside the plans, it has, like, a certain level of conditions and operations. So sometimes it works well, sometimes it doesn't work. So everyone has to understand. So, that needs to be very precise.