61 posts tagged with "how to"

Feature Flagging is a powerful technique that gives businesses and organizations granular control over features by providing the ability to scope these features to a specific segment of users.

Feature flags are helpful for many reasons - one of which is they allow organizations and engineering teams in a multi-tenant software application to limit access to certain features by mapping them to the various tenants in the application or organization.

Using specialized tools is beneficial. However, we often keep flicking between screens, making it easy to lose focus on what matters. But, if your tools integrate, that problem becomes obsolete.

I'm taking you around to learn how ConfigCat and Jira can work together to streamline your development process.

Do you want to learn how to work with ConfigCat's feature toggles better and more efficiently? You've come to the right place! Let's take a look at the benefits of using some good practices when managing feature flags with ConfigCat.

In this post, we’ll look at how we can easily implement a canary release of a feature in 7 steps using ConfigCat’s feature flagging service through its provided dashboard.

This step-by-step guide will showcase how we can release a new feature incrementally, by first exposing it to low-risk user groups (e.g. team members and possibly friends), and then gradually releasing it to a larger audience - using ConfigCat, a feature flag service to implement everything.

Let's take a look at how practical a feature flag can be in a Phaser.io application. Phaser is one of the most popular browser game libraries and with its help, I'll build a simple game that replicates the experience of being in a music studio. Let's get started!

Feature flags have greatly simplified the process of continuously testing and integrating new features into our applications. They ensure confidence even in production environments, eliminating deployment risks such as downtimes or bugs that could adversely affect the entire user base.

Let's play with a hypothetical scenario where you've built a Kotlin-based mobile application, and you'd like to customize the overall user experience based on specified criteria. You've got a perfect idea, but then this question pops up everywhere: Now what? Folks, allow me to introduce you to the concept of feature flags in Kotlin.

Thanks to the latest CI/CD tools and services, software companies can now deliver multiple releases in a week. Over the release process, it's expected that DevOps professionals keep their eyes on the monitoring dashboard and roll-back the deployment on the first suspicion. Since the use of feature flags gets more and more traction, it seems like a good idea to connect those releases and the monitoring tools.

TL;DR​

If you're a software reseller you are allowed to buy a ConfigCat subscription for your client. You are allowed to resell one subscription to one client only. Of course, you are allowed to resell more subscriptions to the same client.

Here is how to do it.

Feature flag services are getting popular, but...​

As feature flags are getting popular, an ever-growing number of developers are facing the challenges associated with them.

No matter if you implement your own feature flag library, or choose a hosted feature flag service like ConfigCat, chances are high you want to use your feature flags in your frontend and in your backend services as well.

If your feature flags can be toggled on a central feature flag dashboard, such as