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.
Easy to Use
What do you like best about the product?
I am QA of my team and launch darkly give you easy way to access feature
What do you dislike about the product?
Sometime it takes more than usual time to integrate with Product
What problems is the product solving and how is that benefiting you?
Easy to maintain flag for multiple environments
- Leave a Comment |
- Mark review as helpful
LaunchDarkly is a very handy tool for feature flagging and experimantation
What do you like best about the product?
1. Easy to create feature flags in different environments
2. The feature flags can be configured differently in each environment
3. Segment is very useful
4. SDK is easy to use
5. Performance is exellent.
2. The feature flags can be configured differently in each environment
3. Segment is very useful
4. SDK is easy to use
5. Performance is exellent.
What do you dislike about the product?
1. At the beginning, the relationship between projects and roles was unclear.
2. Cannot filter contexts/users by the evaluation results.
2. Cannot filter contexts/users by the evaluation results.
What problems is the product solving and how is that benefiting you?
1. Running A/B testing to find the better solution to improve user expierence
2. Building new features behind a feature flag, so we can still merge code to main branch and deploy to production without impact on customers.
2. Building new features behind a feature flag, so we can still merge code to main branch and deploy to production without impact on customers.
LaunchDarkly is a great product with solid features.
What do you like best about the product?
LaunchDarkly provides a great set of features for managing feature flags, kill switches and configuration in a centralized location. It is usable by both technical and non-technical stakeholders to safely roll out new features, or roll them back, when necessary. The technology is fast and reliable in terms of getting the updates to the clients making it a dependable solution for production workloads.
What do you dislike about the product?
LaunchDarkly does its core use-case pretty well. While support for experimentation exists, this is not one of the areas where launch darkly is particularly strong. Better support for experimentation and user targetting would be welcome additions to the LaunchDarkly product line.
What problems is the product solving and how is that benefiting you?
We primarily use LaunchDarkly for feature flagging on new features and to act as a killswitch for new rollouts or risky changes. LaunchDarkly allows anyone on our team to easily see the status of our flags and make changes as needed during new product rollouts or feature launches. This is great because it means our engineers, product team and leadership can all use one view to understand the state of things and make updates without the need for a release/deployment.
LaunchDarkly is a great product, have been using it for the past few years.
What do you like best about the product?
Ease of use, ease of integration, nice UI.
What do you dislike about the product?
Context view is a bit too complex, the query control is a bit too complex.
What problems is the product solving and how is that benefiting you?
We leverage CD in our product, so when we push new code to production, we need to make sure they are behind feature-flag. LaunchDarkly is perfectly suited for that purpose.
Great product, with a few small wrinkles
What do you like best about the product?
It's great to see many more features added into launch darkly regularly. It's a product I regularly use.
I work in the growth team for my company as an engineer and create many experiments with this product.
I enjoy using the product for its feature flag and A/B testing features. For feature flagging there are many feature flags we use to show and hide features to a sample of users and launch darkly is great at capturing certain populations of a sample set.
I also use launch darkly for its A/B testing and experimentation. It's much more complex than the simple feature flag
I work in the growth team for my company as an engineer and create many experiments with this product.
I enjoy using the product for its feature flag and A/B testing features. For feature flagging there are many feature flags we use to show and hide features to a sample of users and launch darkly is great at capturing certain populations of a sample set.
I also use launch darkly for its A/B testing and experimentation. It's much more complex than the simple feature flag
What do you dislike about the product?
There are a few small opportunities that would go a long way in making LaunchDarkly a much better product. I hope this information is useful to your engineering, design, and product team.
One issue I see regularly is when I am not on a network and I need a feature to be on it isn't clear on how to set this a feature to toggle on by default. It would be great to see LaunchDarkly build logic and improve the intuitiveness around the offline case.
While it was great to see that LaunchDarkly has features for grouping certain population sizes. It would be great to see a better UX around labeling groups.
LaunchDarkly also lacks key experimentation features. Albeit, I see that more features are added regularly. Excited to see them!
One issue I see regularly is when I am not on a network and I need a feature to be on it isn't clear on how to set this a feature to toggle on by default. It would be great to see LaunchDarkly build logic and improve the intuitiveness around the offline case.
While it was great to see that LaunchDarkly has features for grouping certain population sizes. It would be great to see a better UX around labeling groups.
LaunchDarkly also lacks key experimentation features. Albeit, I see that more features are added regularly. Excited to see them!
What problems is the product solving and how is that benefiting you?
Feature flagging, experimentation, A/B testing, ramping for features for gaining samples and data for users using the product.
Easy to use and integrate, great availability
What do you like best about the product?
What I like the most is the server availability, meaning we can trust launch darkly to stay up and evaluet our flags correctly anytime.
It's very easy to use, and I like that you can create different rules for staging/production.
It's very easy to use, and I like that you can create different rules for staging/production.
What do you dislike about the product?
I didnt like the latest UI changes... I found it much more comlex and difficulte to set my rules.
What problems is the product solving and how is that benefiting you?
We use it to disable/enable features for developers and customers in both staging and production environment.
Comprehensive tool for feature flagging and experimentation!
What do you like best about the product?
I've used LaunchDarkly at a few companies now and have had a seamless experience every time. I love how straightforward it is and also how detailed their documentation is for the more complex features. I highly recommend LaunchDarkly as a product for other companies who don't want to worry about implementing their own experimentation or feature flagging capabilities.
What do you dislike about the product?
If I had to say something I dislike about LaunchDarkly, it would be how they organize the rules of whether the flag is turned on or not. It's a little bit confusing but if you poke around for a little bit, it does make sense.
What problems is the product solving and how is that benefiting you?
I like that it's a low-cost way to enable feature flagging. My company was hitting Redis to query flags and now we don't have to worry about performance cost. The determination of whether a flag is on or not is done offline which is amazing.
Easy to use, functionality works as it should. UI could do some work.
What do you like best about the product?
It does what it is supposed to do very well. Easy to set up and easy to configure (once live).
What do you dislike about the product?
The UI isn't very intuitive. For instance, it's not immediately clear to me (I had to ask my colleague) that the flag evaluation rule works in an `if, else if...` manner. I didn't know this until I was told.
Secondly, when configuring flag rules, I wish there was a way for me to export my config (maybe into a csv or something). For example, I might have a rule that says: "if attribute=(a,b,c,d,e,f,g) then Y)". I wish there is a way to just get "a,b,c..." without having to inspect the page. Maybe there is though but I just did not know.
Secondly, when configuring flag rules, I wish there was a way for me to export my config (maybe into a csv or something). For example, I might have a rule that says: "if attribute=(a,b,c,d,e,f,g) then Y)". I wish there is a way to just get "a,b,c..." without having to inspect the page. Maybe there is though but I just did not know.
What problems is the product solving and how is that benefiting you?
Allows me to configure and change things in production.
Decent Infra as a service
What do you like best about the product?
Makes flag management easy.
Makes it easy to debug and resolve in case a feature cause outage.
Makes it easy to debug and resolve in case a feature cause outage.
What do you dislike about the product?
I would say UI can be better. Approval workflow can be confusing (not sure if that is exatly a LaunchDarkly issue or issue at my company).
What problems is the product solving and how is that benefiting you?
Feature launch and management
Experimentation and feature flags made simple
What do you like best about the product?
The user interface of LaunchDarkly is sleek. It is easy to switch between different environments and configure experiments or feature flags to only show the test variant to a select subset of users.
What do you dislike about the product?
Overall, no major negatives. Only thing would be that if you approve changes as a reviewer, the owner still has to apply those changes before they get published which has caused a bit of confusion in the past since there is an extra step involved.
What problems is the product solving and how is that benefiting you?
It allows my team to run experiments and gate features so that we can limit new features to select user cohorts
showing 231 - 240