LaunchDarkly makes releasing functionality using flags a breeze.
April 13, 2021

LaunchDarkly makes releasing functionality using flags a breeze.

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with LaunchDarkly

We use LaunchDarkly to separate the Deploy and Release aspects of changes. The R&D team implements LaunchDarkly flags in code, and then by using the user targeting functionality the QA team can validate the changes with the flag on and off. The main point is testing with the flag off, as this means that the master can be deployed to production at any point with the flag remaining off, so we don't have to worry about breaking existing functionality by using these flags.
  • Easy to use UI
  • Great resiliency
  • Good documentation
  • Forward thinking improvements
  • Good performance
  • Large language support in SDKs
  • Add an option to mandate change requests.
  • Allow segments to be used in the professional plan.
  • Increased number of deployments.
  • Enabling the flag at any time of the day or night means fewer employees on hand during functionality releases.
  • Reduced risk of deployments.
  • Less live issues caused by new functionality.
Simple flags and user targeting are very simple, as well as calling a flag value in the code. The hardest is deciding on custom attributes to uniquely identify the user or device as it will be on a case-by-case basis.
LaunchDarkly responds very quickly and we have not noticed any performance impacts from using it.

Do you think LaunchDarkly delivers good value for the price?

Yes

Are you happy with LaunchDarkly's feature set?

Yes

Did LaunchDarkly live up to sales and marketing promises?

Yes

Did implementation of LaunchDarkly go as expected?

Yes

Would you buy LaunchDarkly again?

Yes

It is well suited when you are making changes in areas that are already being used and do not want to impact existing customers in any way. Being able to hide all new code behind a flag means your master branch can be deployed even when your new code is not fully finished. It also means you can focus on testing when the flag is off and almost ignore when the flag is on to ensure the master is production-ready.