Roxana Halați

Want to enable or disable features in your ASP.NET Core MVC application without deploying new code? With feature flags, you can control which features users see and change their availability remotely.

In this tutorial, you'll learn how to implement feature flags in ASP.NET Core MVC using the ConfigCat .NET SDK. We'll build a simple application where a feature flag controls the visibility of a mailing list subscription button. You'll see how to integrate ConfigCat, evaluate a feature flag in an MVC controller, and conditionally render elements in a Razor view.

By the end, you'll be able to turn the button on or off directly from the ConfigCat Dashboard, without rebuilding or redeploying your application.

React Native is a popular framework created by Meta (formerly Facebook) that simplifies the development of cross-platform mobile applications. In short, React Native lets you build mobile apps using JavaScript, which gets automatically transpiled into native code for Android and iOS.

If you've ever wanted to release a React Native feature to users without waiting for app store approval, you're not alone.

In this guide, you'll learn how to use feature flags in React Native to control features without redeploying your app, using ConfigCat.

Releasing new features in a mobile app can feel like walking a tightrope, especially when updates require going through lengthy App Store and Google Play review processes, and users still need to download the new build. That's where feature flags come in. They are software development tools that give developers the power to toggle features remotely, test new functionality safely, and control rollouts without shipping a new app version.

This guide shows you how to use feature flags in Flutter (Dart) with ConfigCat, focusing on best practices, manual polling, offline support, and real-world examples.

In software development, engineers and operations teams have a variety of deployment techniques, each with pros and cons. With so many options available, choosing the right release strategy can be challenging, especially when addressing specific problems.

In this blog, we will focus on two deployment strategies, blue/green and ring deployments, which aim to deploy software with minimal risk and disruptions, each using a different approach. These strategies can be applied to a variety of scenarios.

Coming up, we will explore how they work, their ideal use cases, their advantages and disadvantages, and, most importantly, how using a feature flag service like ConfigCat can enhance the flexibility and suitability of both blue/green and ring deployments to meet your specific needs.

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.

In today's fast-paced digital landscape, users expect seamless, high-quality software experiences without interruptions. As developers, our challenge is introducing new features and updates without causing downtime. The solution? Feature flags. With feature flags, you can safely roll out new features gradually, ensuring your application remains fully operational while the development process continues.

Improving your digital product over time is a sure way to keep your target audience engaged and your business running smoothly. Rewarding specific users, such as loyal customers, can be an effective way of increasing customer loyalty and brand recognition.

In this article, I’m exploring how feature flags can be used in a C#10 console application for simple user targeting and feature management, while walking you through an easy-to-reproduce example.

In software development, being quick is always an asset. In a world where everything moves at a nauseating speed, you can’t afford to waste time. This means every second counts, especially when it comes to loading a website! Fortunately, frameworks are constantly evolving and becoming faster and lighter every day. In this written piece, we'll look at development in Qwik with the help of feature flags.

There’s nothing quite as exciting as seeing your app live on Google Play or the App Store. The culmination of months, if not years, of hard work can bring a sense of accomplishment, but with it comes the pressure of ensuring that your digital product functions as intended and meets the needs of your users.

Whether you’re planning to launch your first app or are a veteran in releases, you’re probably aware of the review process your app must go through before it can go live on the store. These reviews can take anywhere from a few hours to a few days, depending on the complexity of your app and the number of apps waiting to be reviewed.

Releasing your digital product on the market is both an exciting and terrifying process. Whether you’ve created a mobile app or another type of software product, seeing it in the hands of real users is the ultimate achievement. But, simply building a wonderful product is not enough to ensure its long-term success. Over time, you’ll inevitably want to make changes and updates to your app.

But how can you be sure you’re making the right changes? It’s impossible to read your clients’ minds, but A/B testing might just be the next best thing. In this article, I’ll guide you through conducting an A/B test on an Android (Kotlin) application using ConfigCat’s feature flag management system and Amplitude.