Skip to main content

· 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

· One min read
Zoltan David

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.

Step-by-step guide

  1. register at https//app.configcat.com
  2. go to https://app.configcat.com/plans
  3. click the "change plan" button under the desired plan and follow the instructions
  4. go to https://app.configcat.com/invite
  5. invite your client to the "Administrator" group

If you run into any problem, just drop us an email at [email protected].

· One min read
Gergely Sinka

What is 2FA?

2FA is a way of granting access to users only after presenting two separate pieces of evidence (factors). One of these factors is usually a password which the user should know and the other factor something they have or even something they are. This way you can be sure that only knowing your password won't be enough for an attacker to gain access to your account.

How does 2FA work in ConfigCat?

In our case the first factor is password you use to login to ConfigCat Dashboard. The second factor is a 6-digit number generated via an Authenticator App.

· 2 min read
Zoltan David

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

· 2 min read
Zoltan David

"Thank you guys, your rock."

We love to get emails like the one above. And sometimes we get 😃 Actually, more often than I've ever dared to imagine.

Part of the reasons our user love us (well, when they do) are those million little tweaks we do to our feature flag service on a daily basis.

Normally we don't share those little tweaks and updates

· 3 min read
Endre Toth

What kind of cat loves raspberry?

raspberry

…actually I know one, who is a huge fan of Raspberry Pi…it’s CHOCOLATE from the ConfigCat team 🙂

Ingredients:

  • Raspberry Pi 2/3 with:
  • python3
  • ConfigCat python SDK
  • (‘GPIO Zero’ integration to any hardware) - optional
  • ConfigCat subscription (free plan is enough :))