Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Full control of enabling/disabling product features at your fingertips
What do you like best about the product?
The ease and simplicity of rolling out features/services to customers enhances the product rollout and provides control of the where/when/how.
What do you dislike about the product?
It used to be I could see the notes/comments on the history without searching so I could easily find the specific account should an edit need to be made. Now that's been added to a Details tearsheet which means I have to search and click through each update
What problems is the product solving and how is that benefiting you?
Helps me manage product beta releases
- Leave a Comment |
- Mark review as helpful
Works well, but the cost is very high
What do you like best about the product?
Easy ability to manage flags across enviornments
What do you dislike about the product?
The cost is too high, so my company is migrating away from it.
What problems is the product solving and how is that benefiting you?
Across environment flag configuration
Launch Darkly For Complete App rewrite
What do you like best about the product?
We have used launch darkly to completely revamp our front end app using LaunchDarkly flags. We have
What do you dislike about the product?
The ordering of segments can be a little confusing. We ran into an issue where if we write an opt in segment using a query param, it HAS to be first in the rule set to work properly. Individual targetting tends to break things up.
What problems is the product solving and how is that benefiting you?
We were able to rewrite our app page by page using LD.
Pretty straightforward, but lacking in API reporting
What do you like best about the product?
It seems relatively straightforward to and helps streamline the feature flag process.
What do you dislike about the product?
The backend API is lacking for reporting purposes. It's very difficult to find out what segments have the feature flag enabled for example.
What problems is the product solving and how is that benefiting you?
It helps deploy new features selectively to segments of users. We can also immediately turn off a feature if there is a problem.
A flexible UX for controlling new features dynamically
What do you like best about the product?
When rolling out a new feature, whether customer-facing or not, it's important to dynamically enable that feature, on varying environments, and then, incrementally on "alpha", "beta", and then the entire customer base, in small batches at a time. We use LD for these scenarios -- the features can be defined as simple booleans or integers, or as JSON hash-values deliverying varying combinations of values in one query.
This LD-based incremental approach is especially useful for transitioning "old" code to new code, say where the new code is making network calls to a new microservice, which increases both performance and complexity, especially with error management.
We have successfuly mananged several such transitions with LD controls as we address tech-debt with modern, domain-based code, including increased use of varying languages across many internal microservices.
That these LD controls can be partitioned by team ownership helps with cross-functional collaboration.
Finally, using LD feature controls also enables stakeholders from non-Engineering treams, such as Product Managers, Customer Success, Developer Success, etc. to participate in the rollout and control of these new features, as needed.
This LD-based incremental approach is especially useful for transitioning "old" code to new code, say where the new code is making network calls to a new microservice, which increases both performance and complexity, especially with error management.
We have successfuly mananged several such transitions with LD controls as we address tech-debt with modern, domain-based code, including increased use of varying languages across many internal microservices.
That these LD controls can be partitioned by team ownership helps with cross-functional collaboration.
Finally, using LD feature controls also enables stakeholders from non-Engineering treams, such as Product Managers, Customer Success, Developer Success, etc. to participate in the rollout and control of these new features, as needed.
What do you dislike about the product?
The downsides to using LD controls for new features is that these controls can sometimes become "permanent", in that they work for many stakeholders, but are not actually within our own product controls, and thus incur a permanent cost.
These controls are also network-based, which in some circumstances adds latency to the simple act of controlling a feature.
These controls are also network-based, which in some circumstances adds latency to the simple act of controlling a feature.
What problems is the product solving and how is that benefiting you?
LD helps us transition from "old" code to new code gradually, incrementally, across multiple operating environments from the same UI.
We can deploy new code, without worrying about breaking existing production through the use of LD feature flags around the new code, and then, incrementally enable and test the new features in various environments.
This includes the eventual migration of processing from the old code to the new code, incrementally across customers.
Having LD features owned by various teams is also a very useful feature that helps our teams manage our own feature flags.
We can deploy new code, without worrying about breaking existing production through the use of LD feature flags around the new code, and then, incrementally enable and test the new features in various environments.
This includes the eventual migration of processing from the old code to the new code, incrementally across customers.
Having LD features owned by various teams is also a very useful feature that helps our teams manage our own feature flags.
Easy to use, full fledged system that works across tech stacks
What do you like best about the product?
It is reliable; the client frameworks have efficient caches built in and as a developer, I dont have to worry if adding a feature flag will have a performance impact.
What do you dislike about the product?
Obviously it is a cost that could be solved with an open source solution. But when your scale is so large that managing a feature flag system is a cost in itself, it makes sense to consider the already built solution.
What problems is the product solving and how is that benefiting you?
Managining features flags, gradual rollouts, etc.
Best tool to control feature releases
What do you like best about the product?
The UX of launch darkly is quite simple, which makes it really easy to use
What do you dislike about the product?
The recent addition of predefined flags, I'd rather use them all as custom flags
What problems is the product solving and how is that benefiting you?
It allows me to control when to release a feature, and also prevent new bugs from happening. If there's a bug, I can turn off the flag immediately.
Experimentation simplified
What do you like best about the product?
The user experience is great and the layout is straightforward. You can configure experiments based on customizable attributes like user ID, email etc. to ensure only your target cohort sees the A/B test experience
What do you dislike about the product?
If you want to update a flag in multiple enviornments you need to go into configurations for each enviornment and update them separately. Would be nice to have tabs or a way to navigate on the same screen between different environments
What problems is the product solving and how is that benefiting you?
Running experiments for feature launches
Amazing product
What do you like best about the product?
An amazing product with lots of functionality and features. It's easy to use, friendly, and the live updated are an amazing added bonus. We use this product a lot.
What do you dislike about the product?
Nothing really, don't hesitate to switch.
What problems is the product solving and how is that benefiting you?
Releasing features gradualy without risks. Great control on who sees the feature and who's not.
Works, but ui is very confusing and misleading
What do you like best about the product?
That it works...........................
What do you dislike about the product?
The ui is very confusing. You need to simplify it a lot for LaunchDarkly to be well-understood.
Other then that - better understanding of your architecture will be appreciated (how the agent in the app effects scaling)
Other then that - better understanding of your architecture will be appreciated (how the agent in the app effects scaling)
What problems is the product solving and how is that benefiting you?
avoiding deployment for reverting new changes
showing 11 - 20