Chavez Harris

Feature flags help teams release software with more control. You can roll out features gradually, target specific users, run safer production releases, and turn risky functionality off without redeploying your application.

But once feature flags become part of your release workflow, another question comes up: should your application code depend directly on one feature flag vendor's SDK?

That is where OpenFeature can help.

In this guide, we'll look at what OpenFeature is, how it works with ConfigCat, and how to use the ConfigCat OpenFeature Provider for Node.js in a simple Express API.

Suppose you have two variations of a software product, but you're not sure which one to deploy. That's the problem A/B testing solves. And in mobile development, running a clean A/B test is harder than it sounds because you can't just toggle a server-side flag and move on. You're dealing with bundle updates, app store review times, and users who haven't updated in months.

This guide shows how to run a proper A/B test in a React Native app using ConfigCat feature flags for the rollout and Amplitude for analytics. By the end, you'll have a working implementation, a real results-reading framework, and a clear picture of what to do when the test is over.

Software development can be challenging, but deploying and managing new features shouldn't be. With feature flags, you can rest assured that your updates and new features are delivered safely with minimal risk. In this guide, I'll show you how to integrate a feature flag into a NestJS application.

Feature flags help teams release features safely and quickly, but if left unmanaged, they can become stale and accumulate technical debt. To keep your codebase clean, you can use the Zombie Flags page, the Zombie Flags Report, and the Zombie Flags API. Let’s take a closer look at each of them.

Something breaks in your Vue app, and you need to act fast.

Do you push a hotfix and redeploy? Roll back the entire release? Or what if you could simply turn the feature off without touching a line of code?

That is one of the reasons development teams use feature flags. Feature flags let you separate deploying code from releasing it to users. You can ship code to production with a feature turned off, enable it for selected users, roll it out gradually, or disable it if something goes wrong.

In this guide, you will build a small Vue 3 application and use ConfigCat to control a feature remotely without changing or redeploying the application.

Before the open source movement, software programs were 'closed source,' meaning only software developers employed by the company could access and modify them. Outsiders were kept out through non-disclosure agreements and licenses. This exclusivity motivated the creation of the open-source movement, aiming to preserve the freedom to modify and distribute software through publicly accessible code. Today, many commercial companies actively participate in the open-source ecosystem, maintaining software that is open to the public for access and contributions. One such company supporting this effort is ConfigCat.

Instead of relying on assumptions to decide which variation of a piece of software is better, you can let your users guide the decision through a controlled experiment. A/B testing involves splitting your user base into separate groups, where each group experiences a unique variation of a product or feature. By measuring the performance of each variation, you can determine which one works better.

To conduct such a test, you need a tool that helps you split your users into groups and display the appropriate variation for each group. Feature flags are an ideal tool for this. Let's walk through the process of conducting such an experiment in an Elixir app.

Feature flags have equipped software developers to seamlessly roll out and roll back new features with the click of a button.

Due to their design and architecture, feature flags can be adapted and integrated into many languages and frameworks. They can be used with other technologies to enhance or add decoupled functionalities. Using them when scripting and automating your Unreal Engine editor is no exception to this.

GitOps is a framework that combines the practices of DevOps and Git and applies them to infrastructure management. It is not a tool or platform but a set of standards for managing IT infrastructure using Git. Within this realm, feature flags, like those from ConfigCat, can play a crucial role in streamlining workflows, managing releases, and enabling dynamic configurations.

Let’s dive into how ConfigCat and GitOps work together and why this combination is worth considering for your infrastructure and development processes.

Conducting an A/B test experiment is a popular approach to determining which variation of a particular feature works best for your users. This experiment can shape the success of any product or business. Conducting these tests can be tricky and time-consuming, but with the ideal tools, it doesn't have to be.

If you're a Ruby developer, you're in luck. I'll show you how to perform an A/B test experiment in Ruby using ConfigCat feature flags and how to record the results with Amplitude's data analytics platform. Let's get started!