Congratulations on choosing FeatureBoard! You are about to set the foundation for a more data driven approach to your product development.
We think feature management is an essential part of your product architecture and your modern CI/CD pipeline.
Additionally, FeatureBoard puts the power of feature management in the hands of your product managers and marketers, allowing them to make changes to your product without needing to involve your development team.
Designing your FeatureBoard implementation
The key to a successful FeatureBoard implementation is setting up your FeatureBoard account as an accurate representation of your business model.
It is important to understand the following terminology when designing your FeatureBoard implementation.
|Organization||Represents your company or organization account|
|Audiences||Meaningful groups of users e.g. admin users, premium plan, registered users, subscribers etc. Typically, Audiences are important to your business as a whole.|
|Audience Categories||A way to group your Audiences e.g. User Role, Subscription Level, Geolocation etc.|
|Features||Parts of your application/website which needs to dynamically change based on Audiences|
|Feature Categories||A way to group your Features e.g. Release Flag, Permissions, Subscription Limits etc.|
|Projects||Represents your product, website or application|
|Environments||A deployment of your website/application e.g. Development, Production, UAT etc.|
Features and Audiences categories are configured at the Organization level and are available to all Projects and Environments.
Environments are configured at the Project level.
Typically, you will set up one Project per product, website or application.
Frequently Asked Questions
Can I target a user in FeatureBoard?
Instead of targeting users, FeatureBoard enables you to specify Audiences that a user belongs to.
This approach has a number of advantages for simplicity and scalability.
For example, using feature flags on a high traffic website, like a news website, can heavily impact your ability to cache the page. News websites have a lot of users, but only a handful of variations based on the users subscription level, country of origin etc.
Another example is a typical user targeting scenario, where you grant a user access to an early access feature. In FeatureBoard you can create an Early Access attribute on your users then pass that as an Audience to FeatureBoard.
This concept is well established in other platforms like Azure where it’s best practice to grant groups permissions, not direct to users. We have taken those lessons and applied them to feature management.
Can I do A/B testing with FeatureBoard?
While A/B testing is not officially supported by FeatureBoard right now, this is coming soon.
If this interests you, please contact us as email@example.com to be added to the preview list.