Firebase Remote Config for help text
Firebase Remote Config can serve help text. It stores values under keys, your app fetches them at runtime, and a change goes live without a release. It is free up to 100,000 fetches per day per project. For a small set of short tooltips in an app that already uses Firebase, that is often enough. This page covers where it stops.
What Remote Config does well
- Keyed values at runtime. Each parameter has a key and a value, and the client SDKs fetch current values while the app runs.
- No release for a change. You edit a value in the Firebase console and publish. Real-time listeners can apply the update without waiting for the next scheduled fetch.
- Cost. Fetches are free up to 100,000 per day per project on both the Spark and the Blaze plan. From 1 September 2026, Blaze usage above that costs $0.06 per 10,000 requests, falling to $0.01 per 10,000 above ten million a day.
- Nothing new to install. If the app already uses Firebase, the SDK is there.
Where it stops for help text
One pool for everything. A project holds at most 3,000 parameters, and all parameter values together may not exceed 1,000,000 characters. Feature flags, configuration and help text share those limits. A million characters covers tooltips and error messages comfortably. It gets tight once help includes full task descriptions, and tighter when each language needs its own copy.
Values without an editor. A parameter value is a string, number, boolean or JSON. You can store markdown in a string, but the console edits it as a text field with no preview. Steps, warnings and links between topics are yours to encode and render.
Access covers every parameter. Firebase has IAM roles specific to Remote Config, so a writer can get access to Remote Config without the rest of the project. That role covers every parameter, though. The person who edits the onboarding tooltip can also change the flag that switches off a payment feature.
One publish for all pending changes. Edits wait in the console until you publish, and publishing releases every pending change as a new version of the template. There is no draft state per text: a finished tooltip and a half-written one go out together unless you discard the second first.
When Remote Config is the right choice
It fits well when:
- the app already uses Firebase;
- the help consists of short strings;
- the developer writes the help, or whoever does can safely be given access to all Remote Config parameters.
When it stops fitting
It stops fitting once the help outgrows short strings, or once it is written by someone who should not have access to your configuration. From there, the choice is between building the missing pieces yourself and moving help text into a system made for it. How to manage in-app help sets out the options.
Sources
- Remote Config parameters and conditions: value types, 3,000 parameters and 1,000,000 characters per project
- Firebase pricing: free quota and Blaze pricing from 1 September 2026
- Remote Config loading strategies: real-time updates
- Firebase Remote Config roles and permissions