It really is pretty simple to start using featureflow if an application. If you’re deciding how hard it is and whether you can make that switch, read on.

1. Try the 5 minute quick starts

If your a developer, see how easy it is for yourself – sign up for a free trial and try a 5 minute quick start – this will give you a quick overview and something to demonstrate to your fellow developers, devops and product owners. It really can be done in just a few lines of code. Ensure you read our documentation to learn the basics.

  • Set up a basic feature
  • Toggle the feature on and off
  • Add some extra context
  • Try targeting the feature to turn on or off based on the context
  • Add some new variants and try targeting those
  • Try gradually rolling out by using the gradual rollout sliders

Try the javascript SDK and one of our server SDKs depending on your requirements. You’ll find the implementation and concepts are simple but the implications for management are very powerful.

2. Check your legacy code and current processes

  • Head though your application and note any frequently used pieces of configuration – these may be great candidates for becoming manageable features.
  • Identify common deployment pinch points and problems – these might be
    • Coordination issues between multiple team deployments
    • Unstable legacy systems
    • Maintenance modes
    • Production of PVT test scenarios
  • Identify longer running use cases
    • Targeting beta users
    • Coordinating releases across multiple platforms
    • Timing feature releases with marketing requirements

3. Incorporate feature flags into your design planning

  • When defining new features, decide if you may wish to manage the rollout, target the feature or possibly manage an upgrade in the future then define this requirement up front.
    • New experiments that may need targeted testing
    • High performance issues that may need gradually rolling out to avoid overload
    • Features targeted to user segments such as gold, silver, bronze
    • Maintenance mode states
    • Subscription features
    • Turning on only for Beta users


4. Slot it into your SDLC

  • If your following agile you may wish to discus the requirement in the sprint planning meeting and when you kick off a story with a developer.
  • Treating the management of a new feature as a first class-citizen along with the feature itself will ensure you have a well designed and easy to manage and maintain application.

5. Test in your personal sandbox then migrate to test and production

  • Create a personal sandbox environment just for you.
  • Create and test feature toggle locally – this will mitigate any risk and ensure you can get something up and running in the safety of your own dev environment.
  • Featureflow has the concept of environments so when you’re ready you can migrate to test, then deploy to production only when you’re ready.


6. Toggle and mange away!

  • Feel in control and manage your features!
  • Ensure you designate a feature management champion who can help coordinate the effort.
  • Ensure you remove old features that have not been changed in a while. Featureflow will prompt you to do so.