Introducing targeting rules support for feature flags in version 1.1
Updated: Feb 7
FeatureHub extends its capabilities and in addition to percentage splits now supports a variety of targeting rules. Now you can release your features to a limited audience based on the following rules:
✅ User key (email, id)
✅ Percentage split
✅ Custom keys if none of the above satisfies your requirements
When would you most likely to use targeting rules?
Testing in production with Beta-testers groups
We know how important it is to test in production with real users. FeatureHub now allows you to setup a split strategy with the "User Key" rule in which you can provide the email addresses (or other type of IDs) of your Beta-testers. You can then enable this flag just for this strategy and have the default setting for this feature flag as "OFF" for the rest of your audience. Once you are happy with your beta testing, you can set default value as "ON" and remove the strategy with the User Key rule.
Enabling a feature in a specific country
You may be running a campaign for your e-commerce app whereby you are aiming to launch a new page only in certain countries. For such scenario you can add a "Country" rule to your feature flag strategy which allows you to add either single country or an array of countries.
Enabling a feature for specific versions of your app
Let's say you are developing a mobile app and releasing a new version for users to download. You have a requirement for your new feature to only work with this new version or future versions. For this scenario you can utilise "Version" rule and provide the version of your app with the matching condition "greater or equals"
Enabling a feature for a custom attribute
You may be a large enterprise with multiple clients. As an example, a large online store with multiple distribution centres (DCs) with the requirement to enable new functionality for all of the distribution centres, apart from #234 and #235. In this case you can create a new "Custom rule", name your attribute as "DC-number", set it as type "number" and use matcher "not equals" to provide your excluded DC numbers.
These are just some of the examples where you might use targeting rules, however there are many more use cases where you can also mix and match the rules and set them in accordance to your unique requirements.
To checkout the new version of the FeatureHub, go to https://demo.featurehub.io/ and experiment with Split Strategies rules.
Or install with Docker:
docker run -p 8085:80 -v $HOME/party:/db featurehub/party-server:latest