In this tutorial, you'll learn how to use feature flags in React with the ConfigCat React SDK. We'll build a small car-racing app where a feature flag controls whether the race starts, making it easy to see how a remote feature flag change can affect the UI without a new deployment.
ASP.NET Core APIs often need to change behavior without requiring a new deployment. You might want to release functionality to a small group of users, make a feature available only to certain subscription tiers, or quickly disable a problematic change.
Feature flags make this possible by letting you change behavior remotely without modifying and redeploying your code.
In this tutorial, we'll build a simple ASP.NET Core Web API and use a ConfigCat feature flag to control if it returns a two-day or five-day weather forecast. Then, we'll add a targeting rule so only users on a premium subscription receive the full forecast.
Game developers often need to release new functionality without making every change available to every player at once. Feature flags make this possible by letting teams remotely enable or disable features, test changes with selected audiences, and respond quickly if something goes wrong.
In this tutorial, you'll connect a C# Godot project to ConfigCat and use a feature flag to control whether a sprite rotates.
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.
Running feature flags in AWS Lambda requires a slightly different approach from using them in a traditional long-running application. Lambda execution environments can be created and discarded as demand changes, so caching and feature configuration need to account for cold starts and short-lived instances.
In this tutorial, we'll build a .NET AWS Lambda function that uses ConfigCat to control application behavior at runtime. We'll also add Redis as a shared cache, configure the ConfigCat SDK for Lazy Loading, and change the Lambda's behavior without redeploying it.
This pattern is particularly useful in microservices and other distributed systems, where deployment and release often need to happen independently. A service can be deployed with new code already in place while a feature flag keeps the new behavior disabled until you're ready to release it.
A/B testing lets you compare two versions of a feature with real users and measure which one performs better. In an ASP.NET Core application, feature flags can handle which variation a user sees, while an analytics platform measures what happens afterward.
In this guide, we'll show you how to run an A/B test in ASP.NET Core using .NET 10, ConfigCat for experiment assignment, and Amplitude for analytics. We'll split users between two versions of an Add to Cart button and measure whether the change affects user behavior.
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.
