13 posts tagged with "integration"

Creating an exceptional software product is a challenging task that doesn't end on release day. As developers aim to provide an exceptional user experience, they often revisit features and wonder how they can be improved. Luckily, there are many tools available that can help developers understand pain points and improve their products accordingly.

This article explores how ConfigCat feature flags can be integrated with Amplitude Analytics to uncover unique ways to improve products, complete with a demo.

Suppose you come up with an idea to improve the conversion rates on your website. You could implement the idea and roll out the changes to all users. But what happens if the idea is only good on paper and fails in reality? In cases like this, conducting an A/B test is an excellent way to validate your idea.

In the upcoming sections, we'll learn how to set up an A/B test using ConfigCat feature flags and visualize the test's data in Google Analytics.

If there's one thing we don't tolerate here at ConfigCat, that's terrible customer support. Our customers are important to us, and we try our best to provide all the help we can so that they get the best out of our services. In this article, we'll look at how we ensure that our customers have a hassle-free experience when using our service.

While there may not be a one-size-fits-all solution for optimizing workflow and maximizing productivity, you can often put things in place to really up your productivity game. At ConfigCat, we understand this and strive to provide our customers with the essential integration tools to help automate their feature flagging workflow.

For this reason, we are thrilled to announce that ConfigCat now has an official integration with Zapier, a powerful automation tool. With this Zapier integration, you can now connect ConfigCat with over 5,000+ apps, unlocking a new level of automation for your feature flagging workflow. This allows you to make things happen on autopilot without ever having to touch them after the initial integration. And you know what's most interesting about this integration? No code is required! It's like having superpowers.

Continuous Integration (CI) is a process by which new features and updates are continuously added to an application to keep it updated and secure. At the end of each cycle, the changes are deployed to end users. To prevent human errors, various automated tools are chained together to carry out this process. CircleCI is a broader tool that facilitates this, and it also provides an automated solution for managing your feature flags.

Using specialized tools is beneficial. However, we often keep flicking between screens, making it easy to lose focus on what matters. But, if your tools integrate, that problem becomes obsolete.

I'm taking you around to learn how ConfigCat and Jira can work together to streamline your development process.

Developers are one of the most prone groups of people to sprout white hair before their time. This happens for a multitude of stress-related reasons, and not choosing a proper CI/CD DevOps platform surely plays a substantial role in this!

Manage your feature flags from Visual Studio Code using ConfigCat's new Visual Studio Code Extension.

Ever since we heard about Zapier we have been ecstatic by the possibilities this could bring to our platform. Zapier is an integration platform that allows you to easily connect multiple platforms by taking inputs from one service and outputting them to another service. While software integration is common, some integration may not be appropriate for your technology stack, or native integration may not yet be supported. This is where Zapier can step in and save the day.

Nowadays, thanks to modern continuous delivery tools, many software development processes make it easy to deliver multiple releases per week. It is often common for several scheduled releases per week to be released. The usual practice is that during the release process, DevOps guys keep their eyes on the monitoring dashboard, and if they find any anomalies, they roll back the version.

But what happens if someone changes a feature flag's value (release toggles) in the production environment?

Release Toggles allow incomplete and un-tested code paths to be shipped to production as latent code which may never be turned on. https://martinfowler.com/articles/feature-toggles.html

DevOps are notified that a certain threshold has been reached for the production environment and that when they open a related metric they see something similar: