Skip to main content

4 posts tagged with "release"

View All Tags

· 4 min read
Zoltan David

You created a new software feature, put it behind a feature flag, and deployed it to production. Now, you want to enable this new feature to some of your users, so you get early feedback, before releasing the new feature to your whole userbase.

But whom to release the new feature first? How to choose the first user segment? And how to target them with feature flag rules?

Lets see some typical real world examples how big companies do it.

Release based on Company, or Email address

A great first step is to enable the new feature to your colleagues, while keeping it hidden from the rest of the world. This enables you to get early feedback from users inside of your company. You'd be surprised how much bug they'll catch on the first day!

Here is how you can segment and target your colleagues with one simple rule in ConfigCat:

Dogfooding: releasing your software's new feature to the users from your own company

The example above assumes that everyone in your organization has an email address in the form of [email protected], or [email protected].

Note how we used the Email property, and the CONTAINS operator to target only those users who work for your company.

This is what needs to be done in your application at the code level:

var user = new User("<userid>") { Email = "[email protected]" };
var god_mode_enabled = client.GetValue("god_mode_enabled", false, user);

Please note, how we used the god_mode_enabled key and the user object here to check whether God Mode is enabled for [email protected].

The example above is in C#, but you can do the same in Java, JS, Python, Go, Ruby, Swift, Kotlin, PHP etc. See examples in other languages.

Release on a Country basis

Another typical strategy is to release new features to users from a specific country only. This strategy enables you to