When deploying code, one of the best ways to ensure it's high quality, meets user or business requirements, and works as it should is by feature flagging it. Feature flags are a great way to control the release of new code or features in your software, as feature flags make it possible to test new code on specific users or a group of users before releasing them to everyone.

Feature flagging allows you and your team to easily experiment with new features or make changes to existing ones without deploying a new software version. Furthermore, feature flags make it possible for you and your team to seamlessly execute trunk-based development by facilitating continuous deployments and ensuring code integration reliability.

This guide will cover how we can use feature flags to introduce new features in a Svelte application.

Let's say you've just built a new feature, but it's not ready for a full release just yet. So, you decide to test it with a small group of people.

You can go about it in two ways - deterministic or random. The first way lets you specify people by name, email, company or any other attribute you know about them. The latter uses fancy math and probability to randomly assign users into groups. Let's see how you'd accomplish both using ConfigCat's feature flag services. For context, ConfigCat is a developer-centric feature flag service with unlimited team size, awesome support, and a reasonable price tag.

When it comes to releasing new features or changes in software, we can rely on A/B testing for making informed decisions. In this type of testing, we can measure the impact of the new change or feature on users before deciding to deploy it. By doing so, we can carefully roll out updates without negatively impacting user experience.

Feature flags are a great way to control the release of new features in your software. They allow you to easily turn new features on or off without redeploying your code.

However, when implementing a feature flag in an application, we may want to customize its management after the initial release, i.e., schedule an incremental release/delivery strategy that is carried out automatically or schedule future changes to a flag's targeting rule that can take effect at specific time intervals.

For example:

• Activate a flag’s config by date and time. For instance, release a feature at noon on a Sunday afternoon.
• Gradually increase the discount value of an ongoing promotion at specific times of weekdays.
• Enable a feature only on weekends or on weekdays.
• Three days from today, turn on a feature for internal testing and enable it for public use a week later.

The world population continues to grow, and so does the number of house pets. While we all hope most of them have a good quality of life, some don't have a home. To combat this, we can make an animal care app. In this blog post, the app's objective is to increase the pet adoption rate. We will change the color of our call-to-action button and measure the click-through rate of each button version using A/B testing.

Got some free time on your hands? Got you covered!

I'm going to show you a more peculiar way of using feature flags. Feature flags enable non-developers to switch on and off application features or change software configuration.

Following this step-by-step tutorial, you'll build a remote light switch using a Raspberry Pi and ConfigCat’s feature flag tools in no time. Let’s get started!

The goal of software development workflows is geared toward releasing new features and updates, which can sometimes cause issues if not handled correctly. In my opinion, using feature flags has proven to be essential in situations like these. You can use them to easily deploy new features, and if there are bugs you can quickly turn a feature off, then turned it on again when they have been fixed without having to redeploy the app.

By now, you’re probably well-acquainted with the suite of useful feature flag tools offered by ConfigCat. In case you aren't, ConfigCat is a developer-centric feature flag service with unlimited team size, awesome support, and a reasonable price tag. Let's play it safe and discuss 3 cool things that ConfigCat allows you to do – which we bet you didn’t know about! I’ll cover:

• Purchasing a ConfigCat subscription for someone else
• Enabling Two-Factor Authentication (2FA) in ConfigCat
• Getting a free feature flag pack for students

Let’s get started!

Autumn of 2021 saw the release of the newest .NET version, .NET6. This new release brought some updates that could potentially make a developer’s life easier, such as improved performance and a simpler development process. With less code to write and productivity tools like hot reloading, the new .NET was quickly adopted by developers all over the world.

Even before the new release, .NET had a wide range of utilities and has risen to become of the most popular frameworks available. Whether you’re migrating from an older version or just getting started on a new project, you may be wondering what feature management solutions are available to you. I wondered as well, so in this tutorial, I’ll go over one of the best - using feature flags.

If you’ve been reading about feature flags then I’m sure you’re convinced of the power and value they provide. Since development is mostly a team effort, you may be wondering how to manage a feature flag within a team, regardless of size, so one developer’s work doesn’t affect another’s. Well, in this article, we discuss exactly this issue and offer two solutions, depending on the size of your team.