Roxana Halați

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.

Knowing what your customers expect is one of the most difficult challenges when developing a product. Your team may prefer a particular color scheme, whereas your customers may prefer a different one. Fortunately, even if you're updating as you go, you don't have to read customers’ minds.

Including A/B testing in your development process can help you ensure that you're always in sync with your customers and never have to second-guess your decisions. Furthermore, it is simple and inexpensive, and it has the potential to significantly improve the success of your work.

In the ever-changing world of programming, it can be difficult to keep up to date with all the latest technologies and frameworks. There's always something newer and cooler that you simply must try.

In this article, I'll guide you through the process of dipping your toes into the .NET MAUI framework and incorporating feature flags along the way. If you're already a seasoned .NET developer, this tutorial might reveal a couple of things you didn't know about feature flags, so don't hesitate to read on.

Sending your code out into the world can be a nerve-wracking experience. Regardless of how much testing you do beforehand, you’re never quite sure if everything will work according to plan. Even if it’s the case, during an applications life-time, you’ll need to redeploy your code many times. Code redeployment means time, money and a lot of hassle.

Fortunately, feature flags are useful tools that can help reduce the need for code redeployment as well as enable you to test your changes in production without affecting the end-user. In this article, I’ll show you how to make use of feature toggles in a React-like framework. So…