LaunchDarkly vs. monday dev

If a new feature should be added but unsure of how it will actually work or how users will accept the new enhancement or change, this tool allows you test and measure initial results. This saves so much time and energy knowing the results before it is deployed and might have low user adoption or acceptance.

Incentivized

I find Monday helpful for lead management. It's great because details like phone, email, and addresses are specific columns from which we can grab data and pull it into other areas. It's great to see who is assigned what and to know what the next steps are for your leads. We use a different scheduling tool with our team, as that calendar view isn't as robust.

Incentivized

• A/B or Multi Variant Testing as a methodology to gather insight from customer usage. Experimentation as a feature within LaunchDarkly offers information around the success of one variant over another and whether the experiment has reached statistical significance.
• Being able to decouple deployment of code from the release of a feature is hugely valuable.
• Development teams are empowered to manage features within their production applications for reliability or testing purposes.

Incentivized

• Managing specific objectives
• Automation
• Integration and interaction with GitHub
• Scheduling and feedback effectively

Incentivized

• Limited number of users on cheaper plans that is limiting our ability to audit log who is making changes.
• Some of our engineers are confused between flags and segments and have set up items incorrectly.
• Better documented support for React with Typescript.

Incentivized

• Sometimes, it's a little technical to set up. Someone who isn't particularly savvy will have a hard time setting it up.
• Sometimes there are glitches in the automations.
• The comments areas can be confusing- how they nest. Things can get lost in there.

Incentivized

It fits out business case

Incentivized

We are very likely to renew, because it has been really useful

Incentivized

It's very easy to create new feature flags and set them properly. It is more difficult to get LaunchDarkly integrated within a distributed system so that flags can be used. Especially on stateless servers where gating features by user is not easy. Overall though, it is very easy to get started and I like how simple it is to use.

Incentivized

I give a ten for monday dev's usability because it was a really smooth transition coming from Jira to monday dev. All team members also felt that way. When managing projects, the quality and various options I am able to customize views and columns for each task is really a dealbreaker. Approved.

Incentivized

No issue with availability at all

Incentivized

From what I have seen, LaunchDarkly integrates well with your code and also services you might have in your tech ecosystem. We use Jenkins for automation and we were able to use it to build pipelines to automate the control of LaunchDarkly toggles in our code.

Incentivized

The overall support is very responsive

Incentivized

Good engagement from account manager

Incentivized

Yes I do.

Incentivized

No I wasn't involved

Incentivized

LaunchDarkly stood out to us because it put control of the application within the hands of our engineers. We didn't want to allow business users to manipulate the production site via a third-party tool. Instead, our focus was on delivering faster as an engineering team.

Incentivized

It is at least as good as these tools, in many ways, it is better because it is easier to use and setup. It doesn't require a full-time admin like these tools do. It does lack some of the detailed reporting and such that these offer, but the product is still young and growing. These are much more well-developed tools

The platform didn't go down since we implemented it

Incentivized

• Improved developer experience with some teams moving to Trunk-based Development.
• Increased deployment frequency due to smaller code releases.
• Validation of the technical and business value of work is achieved more quickly through smaller pieces of work and through experimenting with a small group of users before a feature gets to 100% of customers.

Incentivized

• Although the initial operational cost is usually somewhat high, it is really worth considering in an environment with more than 10 employees working together.
• In project costing (web development) it is quite acceptable and falls within the scope of the final product quote.
• I don't have exact numbers or percentages (because I'm not in charge of that section) but I can say that it falls within a good to acceptable ROI range.

Incentivized