84 posts tagged with "feature management"

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.

When it comes to shipping features fast and confidently, feature flags are your secret weapon. They let you roll out updates safely, test in production, and avoid deployment risks. But here's the big question: should you build your own feature flag system, or choose a ready-made solution like ConfigCat?

As the gaming industry continues to evolve, driven by technological advancement and an ever-growing demand for more immersive, engaging experiences, players no longer settle for static and predictable game worlds—they crave dynamic environments that respond and adapt to their actions in real-time.

This shift toward adaptive gaming revolutionizes development techniques, enabling developers to craft personalized gameplay as unique as the player behind the controller. At the heart of this transformation lies a powerful tool: feature flags.

Hey, Rustaceans! We developed the Rust SDK in response to a feature request from one of our customers, OneSignal. When we heard about their needs, we rolled up our sleeves and released the Rust SDK two months later. With it, you can manage feature flags like a pro—whether starting a new project or optimizing an existing app. It allows you to toggle features on and off without redeploying your code. That's right—no more redeploys every time your boss changes their mind about a button color!

With ConfigCat's feature flags, you can gradually roll out new features, rigorously test them (in a controlled environment, of course), and make changes on the fly—all directly from your dashboard! Let's dive into why this is a game-changer for your development workflow.

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.

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.

Feature flags are powerful tools for managing new releases. They let developers toggle features on and off without modifying the underlying code. This method, known as feature flagging, provides flexibility for rolling out updates gradually to specific user groups.

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!

From social media to banking, health monitoring to entertainment, mobile apps have intricately woven themselves into the fabric of our day-to-day activities. This widespread adoption has led to a surge in demand for more sophisticated, user-friendly, and dynamic applications.

In response to this demand, developers and companies are constantly seeking innovative methodologies and tools to streamline the app development process, enhance user experience, and ensure the delivery of high-quality products. This is where feature flags come into play.