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 hit the ground running feature flag and configuration SaaS tool
What do you like best about the product?
In both a personal and professional capacity LD has been easy to integrate with. Their SDKs are plug'n'play.
What do you dislike about the product?
Using launch darkly for configuration can be a bit tedious especially when dealing with JSON variations. Navigating around the JSON input does not feel natural, and the review box (diff tool) does not hightlight field changes very well, if at all.
What problems is the product solving and how is that benefiting you?
Feature flagging and configuration management. Config management means less engineer input into certain features when other stakeholders in the business can own the config.
- Leave a Comment |
- Mark review as helpful
Comprehensive solution for feature flag management
What do you like best about the product?
LaunchDarkly offers a complete full-featured platform for managing our feature flags. The interface is straightforward, the documentation is complete, and the customer success support has been very helpful. Most importantly we haven't encountered any operational issues in production related to our use of LaunchDarkly.
What do you dislike about the product?
The broad scope of LaunchDarkly functionality also means it can be difficult to be sure we are using it to its full potential.
What problems is the product solving and how is that benefiting you?
LaunchDarkly allows us to activate technical preview features for specific customers only, and also allows us to hide features deployed through continuous delivery so that we can reveal them as part of a coordinated marketing release.
Easy release and manage features effectively
What do you like best about the product?
I like the fact that my team is able to control the rollout of features and changes across our applications, enabling us to deliver better software faster and with less risk. Overall, the tool is easy to use and integrate with several different tools.
What do you dislike about the product?
Integrating LaunchDarkly into applications can introduce some performance overhead, particularly if the feature flag evaluations are done synchronously and impact application response times.
What problems is the product solving and how is that benefiting you?
LaunchDarkly helps businesses overcome the challenges associated with modern software development and release management by providing a powerful feature management platform that enables continuous delivery, risk mitigation, user experience optimization, and cross-functional collaboration.
Feature flags made easy
What do you like best about the product?
I think one of the biggest advantages of using LaunchDarkly is the easy integration of libraries with application code. Simply register the LaunchDarkly client when bootstrapping the application, and make it available. All engineering levels can start working with feature flags in no time. Another great feature is the ability to target specific users and control how a flag's value behaves, which is excellent for piloting new applications in production. Even though we didn't use several integrations, seeing so many ways to connect LaunchDarkly to other apps is awesome. For us, the Slack integration was more than enough. Newer apps with no built-in feature flags would default to LaunchDarkly, increasing the frequency of use in the organization.
As far as I'm aware, we never reached out to Customer Support, so I don't have any useful comments to provide on that topic.
As far as I'm aware, we never reached out to Customer Support, so I don't have any useful comments to provide on that topic.
What do you dislike about the product?
Probably the website at the begining, but never was a dealbreaker. It does what it needs to do and after sometime I kind of like it.
What problems is the product solving and how is that benefiting you?
Streamlining the process for launching new features into production, controlling when to turn them on and off, increases engineers' confidence when deploying without affecting the running systems.
LaunchDarkly is the tool for anyone serious about feature management
What do you like best about the product?
It's a one-stop shop for all things related to feature management: feature toggling, experiments, rollout strategies, ... It's all there and all very simple to use.
What do you dislike about the product?
Searching for contexts, I find the filter option and its specific language a bit tricky and I always need a few tries to find what I want.
What problems is the product solving and how is that benefiting you?
It allows us to have:
- release trains on mobile, so that we can ship every week
- progressive rollouts of features
- graceful degradation
- kill-switches
- experiments, A/B testing
Overall, LaunchDarkly has changed the way we approach software. We're more relaxed about shipping because we know everything can be behind a toggle, released progressively. It allows us to try things, show versions to a small cohort of users and get feedback early, ...
- release trains on mobile, so that we can ship every week
- progressive rollouts of features
- graceful degradation
- kill-switches
- experiments, A/B testing
Overall, LaunchDarkly has changed the way we approach software. We're more relaxed about shipping because we know everything can be behind a toggle, released progressively. It allows us to try things, show versions to a small cohort of users and get feedback early, ...
LaunchDarkly was and actually is a big game changer in our company.
What do you like best about the product?
A lot of possibilities to manage your product. Now we are using it on a daily basis. It is really easy to use, and if you explore it more you will find more and more useful things. "Easy to learn, hard to master". It was really easy to implement it in our environment. Contact with support was always a pleasure (Aaron is the nicest person I ve ever met).
What do you dislike about the product?
Implementation process was a little tricky. Not from the technical side but organisational. We didn't know that we can create one project for all platforms etc.
What problems is the product solving and how is that benefiting you?
It allows us to proceed to CI/CD. Now every team can work on its part of the product. Timelines and limits of regular upgrades do not stop them, they can do it alone. Fuckups on the production can be "fixed" quickly by switching off the flag, then the team has more time to investigate and fix the problem with no time pressure.
Powerful feature flag tool that we rely on
What do you like best about the product?
Very configurable - for instance, you can target any flag by any of multiple facts you send to the LaunchDarkly tool, and can use custom names for the contexts you use (such as "User" or "Enterprise").
Great modern JS SDK means you can do all your feature flagging on the frontend if you want, allowing neat tricks like React updating in real time when you toggle a flag on.
Thoughtfully designed and well-documented API means you can also fetch flags completely manually on the backend and handle them yourself.
The API also allows you to do admin things such as creating flags and setting targeting. In our case we had a senior engineer make tooling and scripts to use their API to synchronize it with our old in-house feature flag system, allowing us to shift to using LD seamlessly with no manual labor or risk of outdated targeting.
Product feels very well designed and is reliable and performant.
We have never had even a hint of a reliability problem, as far as I know they have had zero downtime problems.
They have a lot of features, many we don't even use such as scheduling flags, approvals, and especially, A/B testing.
Great modern JS SDK means you can do all your feature flagging on the frontend if you want, allowing neat tricks like React updating in real time when you toggle a flag on.
Thoughtfully designed and well-documented API means you can also fetch flags completely manually on the backend and handle them yourself.
The API also allows you to do admin things such as creating flags and setting targeting. In our case we had a senior engineer make tooling and scripts to use their API to synchronize it with our old in-house feature flag system, allowing us to shift to using LD seamlessly with no manual labor or risk of outdated targeting.
Product feels very well designed and is reliable and performant.
We have never had even a hint of a reliability problem, as far as I know they have had zero downtime problems.
They have a lot of features, many we don't even use such as scheduling flags, approvals, and especially, A/B testing.
What do you dislike about the product?
They find ways to inconvenience you by withholding features on the non-enterprise plans. There are parts of the UI where they tease you such as the flag compare tool, where it will show you what flags don't match across environments, but you can't have it copy the settings if you aren't on Enterprise. Overall there are too many of these, but I admit that most of them aren't vital to my usage.
The (MAU-based) pricing can get expensive if you have a lot of users/entities that you are targeting separately. Likewise, the seat-based pricing can get expensive if you need a lot of licenses.
Overall it is expensive. If software is your core competency, your needs are actually very simple (meaning you don't use a lot of their many advanced features and tools), and your usage level is high enough to hurt, you may be better off considering either a much simpler tool, or something simple that you support in-house.
The (MAU-based) pricing can get expensive if you have a lot of users/entities that you are targeting separately. Likewise, the seat-based pricing can get expensive if you need a lot of licenses.
Overall it is expensive. If software is your core competency, your needs are actually very simple (meaning you don't use a lot of their many advanced features and tools), and your usage level is high enough to hurt, you may be better off considering either a much simpler tool, or something simple that you support in-house.
What problems is the product solving and how is that benefiting you?
We use LaunchDarkly to allow us to protect all the code we push until it's passed QA and we're ready to launch a feature. We also use it to hold back a feature sometimes for a customer who isn't ready to migrate.
The best feature flagging tool available
What do you like best about the product?
LaunchDarkly is simply the best feature flagging tool.
The integration from a service and application perspective, is super lightweight and very DevOps focused.
Configuring new flags, tracking the life-cycle of a flag, auditing, etc and just a breath of fresh air
The integration from a service and application perspective, is super lightweight and very DevOps focused.
Configuring new flags, tracking the life-cycle of a flag, auditing, etc and just a breath of fresh air
What do you dislike about the product?
LaunchDarkly for larger development teams can be expensive.
What problems is the product solving and how is that benefiting you?
We used LaunchDarkly to help us move from multiple internal tools, with limited feature sets, and limited visability. We now have a single place to understand how all our services and frontend systems are configured to run.
Further it has helped us to move to move complete trunk based development
Further it has helped us to move to move complete trunk based development
Enables continuous deployment
What do you like best about the product?
We can place new features behind feature flags and continually push to production without fear of new features causing errors.
What do you dislike about the product?
The maintenance of cleaning up old feature flags.
What problems is the product solving and how is that benefiting you?
We can allow internal users test the new features before releasing it to the general public.
Not sure how we could ever go without it now.
What do you like best about the product?
It is no understatement that Launch Darkly has changed how we build, test, and deploy functionality.
When we first demo'd it to our team, it "just worked". It was like magic.
Our team can try new things, turn them on, and then rollback if necessary. Or we can build new bits of functionality and test them for individuals easily. You can use it as a killswitch, as a development tool, or even, in a pinch to do content modifications or a one-off permission test. We don't have to wait for something to be 100% finished. We can hide it behind a flag and then come back later.
It was super easy to add to all of our front-end and back-end systems (PHP, JavaScript). While the conversion from Users to Contexts was a little confusing at first, once we made the migration, it actually made a lot of sense. The rules systems and custom attributes make it easy to target individuals or groups. We can turn something on for a group or a subset of users really easily.
The administrative UI is great. We can get questions really easily about who sees what and why, looking at evaluations happening in real time, etc.
When there are problems or questions about what fields are in what values, the historical log of changes in the UI have been a god-send. "When did this change?" is always something we can answer. Who changed it, when, and (usually) why is recorded in the historical log.
When we first demo'd it to our team, it "just worked". It was like magic.
Our team can try new things, turn them on, and then rollback if necessary. Or we can build new bits of functionality and test them for individuals easily. You can use it as a killswitch, as a development tool, or even, in a pinch to do content modifications or a one-off permission test. We don't have to wait for something to be 100% finished. We can hide it behind a flag and then come back later.
It was super easy to add to all of our front-end and back-end systems (PHP, JavaScript). While the conversion from Users to Contexts was a little confusing at first, once we made the migration, it actually made a lot of sense. The rules systems and custom attributes make it easy to target individuals or groups. We can turn something on for a group or a subset of users really easily.
The administrative UI is great. We can get questions really easily about who sees what and why, looking at evaluations happening in real time, etc.
When there are problems or questions about what fields are in what values, the historical log of changes in the UI have been a god-send. "When did this change?" is always something we can answer. Who changed it, when, and (usually) why is recorded in the historical log.
What do you dislike about the product?
The only real downside we've encountered is the lack of a true Angular integration. There are options out there, but we had to tweak and modify to make it work well.
What problems is the product solving and how is that benefiting you?
Allows us to launch smaller features more quickly and with more confidence. We can use it to deploy stuff that isn't quite ready but we still want to be able to get feedback in production. Or we can just enable it for a group of testing users.
showing 331 - 340