Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I want my team to release safely without showing unfinished features to customers

Short answer

A feature flag is an on-off switch in the code that lets you ship a feature hidden and show it later, or only to some people. It decouples releasing from showing. A small team can start with a plain setting, switch features on for staff first, and remove each flag once the feature is fully live.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I hold back releases because one feature is not finished.
  • A half-built feature once showed up for customers.
  • A bad feature means a full rollback of everything.
  • I want to try a new feature with a few customers first.
  • Release days are stressful because everything goes out at once.

Why does this happen?

  1. Everything ships together

    When one release contains several features and one is not ready, the options are to delay all of it or ship it all. A switch per feature gives a third option.

  2. A rollback undoes good work too

    If a new release has a problem, rolling back removes the working changes with the broken one. Turning off one feature is a smaller and faster step.

  3. Testing on real data needs real users

    Some things only show up with real use. Showing a feature first to staff or to a few accounts limits who is affected if something is wrong.

  4. Flags that are never removed pile up

    A flag is meant to be temporary. When old flags stay in the code, they make it harder to read and to test. They need an owner and a removal date.

What can I do about it today?

  1. Ask how features are hidden todayAsk your developer what stops an unfinished feature from reaching customers right now. The answer shows whether a flag would help.
  2. Pick one upcoming feature as the firstChoose a feature that is not critical to try the method. Do not turn it on for everyone at first.
  3. Decide who sees it firstName the group, for example your own staff or two friendly customers, and who decides when it goes to everyone.
  4. Write down how to turn it offEveryone involved should know who can switch it off and how. Ask that this be tested before the real release.
  5. Do not buy a tool yetA paid flag service is not needed to begin. A simple setting stored in the database or in the server configuration is often enough for a small team.

When should I bring someone in?

  • A feature leaked to customers before it was ready.
  • Switching a feature off would need a new release.
  • Flags already exist and nobody knows which are still used.

How do I handle it?

  1. Start with the simplest switchA setting that the application reads, which can be changed without a new release, covering the one feature in question.
  2. Keep the check in one placeThe decision whether a feature is on is made at one spot, so removing it later is easy.
  3. Test both statesThe feature is tested with the switch on and off, so turning it off never breaks anything.
  4. Remove the flag when doneEach flag gets a written owner and a cleanup date, and it is deleted once the feature is fully live.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Do I need a paid feature flag service?

Not to begin. A setting the application reads can do the job. A service becomes useful with many flags, many people changing them or complex targeting.

Do mobile apps support feature flags?

Yes, if the app reads the switch from your server. A flag baked into the app itself needs a new app release, so it does not help there.

Can a flag make the app slower or riskier?

A badly managed flag can add complexity. Keep few flags, test both states and remove each one when the feature is complete.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.