1. Home
  2. Feature Management Software
  3. LaunchDarkly Reviews
  4. User Review of LaunchDarkly
Use LaunchDarkly to level up your Release On Demand capabilities!
April 13, 2021

Use LaunchDarkly to level up your Release On Demand capabilities!

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

Overall Satisfaction with LaunchDarkly

We use LaunchDarkly to improve our Release-on-Demand capabilities and cycle time of features for our business. It allows our product delivery teams to decouple from one another and launch features independent of a release window. It is currently being used by a few teams, but we are looking to expand the capability across as many business applications/components as possible in the near future.
  • Top Notch Documentation.
  • RESt API / SDK's that are easy to code against.
  • High performing CDN's to avoid performance bottlenecks.
  • More advanced communication around price increases.
  • Usage based pricing option as opposed to trying to guess what you will need.
  • Less risky deployments.
  • More flexibility for feature releases.
  • Less overtime.
We primarily use the Rest API since all features can be controlled with it which is great, but the UI is very user friendly too.
I haven't noticed any performance issues yet with it. Time will tell as more applications adopt the platform in our organization.
  • Split
We decided to use LaunchDarkly because they are the market leader. Split was fairly new and immatured platform at the time.

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

JFrog Artifactory, Jira Service Management (Jira Service Desk), Atlassian Confluence
Great use cases include wrapping code logic with a flag that enables you to release the feature at will without requiring any deployment or downtime for end users. This also allows different microservice teams to implement dependent functionality at their own pace, turning everything on with the toggle of a flag. Less appropriate uses would be to wrap every feature with a flag as this can bloat out code and cause feature flag sprawl.