Amplitude Analytics vs. LaunchDarkly

Amplitude Analytics is well suited for scenarios where you have multiple data points to understand customer behavior and journeys and utilize simple to medium complexity graphs/charts. It may not be suitable for scenarios where you need to slice and dice data into highly customizable dashboards as that requires significant effort from technical teams.

Incentivized

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

• Feature analytics - measuring frequency of usage
• Time taken by users to convert in funnels
• Actions that drive certain user behaviors in funnels via correlation
• Actions that lead to user drop off in funnels via correlation
• Comparing behavior of two custom user cohorts

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

• Some more clarity and examples of implementation with GDPR in mind
• Some segregation inside user properties can be difficult to implement
• Splicing information inside funnels could be more intuitive
• User support for the cheaper tiers is hard to access
• Pricing transparency really needs to be improved

• 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

It fits out business case

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

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

I haven't used the Amplitude support other than their training docs so I can't speak too much to the in-person support but the docs are serviceable. Nothing too crazy but between the user tips, email notifications, and the decent number of docs I was able to get the support I needed to ramp up on the tool.

Incentivized

The overall support is very responsive

Incentivized

Yes I do.

Incentivized

It's the best in class with all the bells and whistles. Other options could suit you just fine at a lower price point, but you need to be sure of what you are not getting and the switching cost associated with when you do need it.

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

The platform didn't go down since we implemented it

Incentivized

• It collects data of great importance which allows to make product improvements.
• It easily identifies problems a user may have with the product.
• The flow of users who have used the product has improved, thus being able to generate more income thanks to the improvements and new functions.

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