Feature Control

Determine if a feature flag is appropriate

Determine the type of feature control to use

Write feature flagging components at the beginning

Do not use GIT as a feature control

Integrate code with your normal release process, even if the feature isn't complete

Test to ensure the "disabled" state of the feature works as expected

Enable the feature for an internal group and iterate on it

Enable the feature for a trusted external group and get feed back

Enable the feature for all users

(should not require a deploy)

If it's not going away, remove the feature flag code

Features that may never be turned on for all users

Use Database Feature

Create a boolean column in the emma_account_settings table 

(for now)

The feature tag is the same as the column name

Features that will eventually be enabled for all users

Use RedisFeature

Self deprecating

Individual control until enable for all

NO GOING BACK

If you enable for all then disable for one, it will disable for all!

Factory

Switch on the feature flag in the controller and use a different template

Pass a boolean to a template and switch internally

(use sparingly, gets messy)

Add a layer between the data and presentation that translates the data into the required format by the presentation