Feature Flags in a Small Business App: Changes Without a Release
Short answer: A feature flag is a switch your app checks before showing a feature, and remote config is the service that lets you flip that switch from a dashboard instead of shipping a new version. For a small business app, that means you can hide a broken checkout option in minutes, release a feature to a tenth of users first, or turn on a seasonal menu on the right morning. The cost is a little extra code and the discipline to delete flags once they've done their job.
What a flag actually is
Every app update goes through a build, a store review and then a slow trickle of people installing it. If a feature misbehaves, the usual fix takes the same route, which can mean days of a broken button in people's hands.
A flag sidesteps that. The new code ships inside an ordinary update, but it sits behind a condition like "show the gift-card screen only if gift_cards_enabled is true". The value of gift_cards_enabled lives on a server. Change it there, and installed apps pick up the new value next time they check.
Firebase describes Remote Config in exactly these terms: you set in-app default values, then override them from the console for everyone or for segments of users, without publishing an app update. Dedicated flag services such as LaunchDarkly and ConfigCat do the same job with more targeting, approval and audit features. Which one fits depends on what you already use; if your app already runs on Firebase, Remote Config is often the shortest path.
How it works in practice
There are four moving parts:
- A default value inside the app. If the phone is offline or the server can't be reached, the app uses this. Pick defaults that are safe: usually "new feature off".
- A parameter on the server with the live value, plus optional conditions such as app version, language or a percentage of users.
- Fetch and activate logic. The app downloads values and decides when to apply them. Firebase's documentation recommends real-time Remote Config so apps receive new values as soon as you publish, rather than waiting for the next scheduled fetch.
- A dashboard where someone with permission changes values and can see a history of changes.
One firm rule from Firebase's own policy notes: don't put confidential data in remote config. The values reach every app instance that fetches them, so a user who goes looking can read them. Flags decide what the app shows; they are not a place for API keys, discount codes you want kept private, or pricing logic that must be enforced on your server.
Five jobs flags do well for small businesses
Kill switches
A payment method starts failing, a third-party booking widget goes down, or a promo screen has a typo in the price. With a kill switch, you hide it while you fix it. LaunchDarkly's flag templates list a "kill switch" as a permanent flag type for turning non-core functionality on or off, which is a useful way to think about it: some flags are meant to stay.
Staged rollouts
Rather than releasing a new ordering flow to everyone, you turn it on for, say, 10% of users, watch crash reports and conversions, then widen it. Firebase's rollouts feature is built for this: it compares a rollout group with a control group using Crashlytics and Google Analytics, and lets you roll back for everyone or a segment.
Seasonal and scheduled features
A café app shows a Christmas pre-order screen from 1 December; a garden centre switches its home screen banner in spring. Flags let you ship the screen weeks early and turn it on when the season starts, rather than racing a store review.
Testing two versions
If you're unsure whether a one-page or two-step booking form works better, a flag can split users and your analytics can compare the outcome. Firebase pairs Remote Config with A/B Testing and random percentage targeting for this. Small apps need patience here: with modest traffic, a test may need weeks before the difference means anything.
Per-customer or per-location switches
For a business app used by staff at several sites, a flag can turn on a new stock-count screen at one branch first. That is often more valuable than percentage rollouts for a small team.
When flags matter, and when they don't
Flags earn their place if:
- Your app takes payments, bookings or orders, where a broken feature costs money by the hour.
- You release regularly and want to separate "code shipped" from "feature switched on".
- You run seasonal promotions or menus that change on fixed dates.
They're overkill if your app is a simple brochure that changes twice a year. Every flag adds a branch to test: with three flags, there are already eight combinations of on and off.
Flags also don't replace proper version management. If an old version of your app breaks against a new backend, you need a minimum-version check; we cover that separately in forcing users onto a new app version.
Setting up your first flags
A sensible first project for a small team:
- Name flags by purpose and type.
release_new_checkout,killswitch_apple_pay,season_xmas_preorders. LaunchDarkly notes that a flag key can't be changed after it's saved, so get naming right at the start. - Write the safe default first. Ask: if the app can't reach the server, what should happen?
- Limit who can flip switches. One owner and one developer is plenty. Record why each change was made.
- Add an expiry note. For release and seasonal flags, write a "remove by" date in the description.
- Test both states before every release, not just the "on" state.
Cleaning up flag debt
Flags that outlive their purpose become clutter. ConfigCat calls these "zombie flags": a temporary feature became permanent but the flag stayed, an experiment finished, or a flag hasn't been touched for months. They make code harder to read and can quietly switch on old logic.
A simple routine: once a quarter, list every flag, mark which are permanent (kill switches, per-location settings), and schedule code removal for the rest. Removing a flag means deleting the condition in the code and the parameter on the server, in that order, in a normal release.
FAQ
Do feature flags work on both iOS and Android?
Yes. Remote config services provide SDKs for both, and Firebase also covers web, Flutter and Unity. The flag values live on the server, so one change reaches both platforms.
Can a flag change what the App Store approved?
Flags should switch features that were in the reviewed build, not deliver new functionality the store never saw. Check Apple's and Google's current review guidelines if you plan anything beyond on/off switches.
How quickly does a flag change reach users?
It depends on your fetch logic. With real-time updates, open apps can pick up a change within moments; otherwise it happens at the next fetch or app launch.
Are free tiers enough?
Often, for a small app. Check each provider's current pricing page, since limits on users, seats and requests differ.
Running an app where a single bad release would hurt bookings or sales? Tell us how you ship updates today and we'll suggest where a switch belongs.