When would Firebase fit your app?
Imagine a small team sharing a task board. Firebase can save a task, recognize the teammate who signs in and show an update on someone else’s screen. You still decide who belongs to each board and which tasks they may open or change.
This profile uses Cloud Firestore Standard for records, Firebase Authentication for accounts and Cloud Storage for attachments. Firestore calls each record a document. A task document might contain a title, a due date and the board it belongs to. A collection groups documents your app works with together.
Which Firebase service does your board need first?
Start with saving a task. Add sign-in when tasks need to belong to a person or team. If the first version has no attachments, you can leave Cloud Storage out of that version.
| Job | Service | What you configure |
|---|---|---|
| Save a task | Cloud Firestore | Where records live, what fields they hold and who can read or write them. |
| Recognize a teammate | Firebase Authentication | How people sign in and what account screens they use. |
| Attach a file | Cloud Storage | How uploads are added, who may open them and the required billing setup. |
On a small screen, scroll the table sideways to read every column.
Can you save one task and open it again?
Make a Firebase test project, register the web app and connect it using Firebase’s JavaScript library. In the Firestore setup, choose Standard and decide where its records will be stored.
For a browser app, the initial production rules deny reads and writes until you grant the access you want. Firestore test mode can let anyone read and overwrite records. Keep real information out of test mode.
Put one invented task on the board. Set the rules needed for that test, then save a change, refresh the page and confirm it reopens with the new value. Add an ordinary test account when you’re ready to check private board access.
Can a signed-in teammate open a board they don’t belong to?
If the browser connects directly to Firestore, use Firestore Security Rules to check board membership and control what each person can do. If only members may change a task, also check the information they submit. Otherwise a person could try to give themselves access by changing a task’s owner.
Use two ordinary accounts. Let one save a private task, then try to read it, change its owner and delete it as the other account. Test signed out too. If the task has a private attachment, try to open it under the same conditions. Cloud Storage has its own rules, so a private task can still have an exposed file.
Run the test through the app your customer will open. Firestore’s server libraries bypass those rules. If your app uses them, make sure your server code checks what each person is allowed to do before reading or changing records.
What might change the bill for a small task board?
Spark is the no-cost plan with limits. Blaze connects a billing account and charges for applicable usage. Before you invite people, estimate how often the board opens, how many tasks it loads and how many files people might attach.
One visit can read several documents. A board that keeps updating while someone watches it can add more reads. Budget alerts can warn you about spending without stopping service. Firebase’s current spend caps do not cover the Firestore database or Cloud Storage files in this example.
| Part | What the plan includes or requires | What to track |
|---|---|---|
| Firestore Standard | One eligible database per project has 1 GiB of storage, 50,000 document reads and 20,000 writes per day at no charge. | Paid charges can include reads, writes, deletes, stored data, data sent out and some of the index entries used to find matching records. Check the rate for your location and billing currency. |
| Uploaded files | Cloud Storage requires Blaze. Since February 3, 2026, that also applies to keeping access to older default storage buckets. | Track stored files, requests and data sent out. Some usage can still be included. |
| Database backups | Scheduled backups require Blaze. | Backup storage and restore work are separate charges outside Firestore’s free usage. |
On a small screen, scroll the table sideways to read every column.
What would you restore after someone deletes a task?
A scheduled Firestore backup can restore records into a new database. Before relying on it, decide what happens to the task’s original attachment and the accounts that need to open it.
Firestore can take those backups daily or weekly. They contain the data and the database’s index settings for finding records. Automatic expiry settings are excluded. Check who can access the new database before you connect an app to it.
Try the recovery with invented tasks first. Sign in as the original team member, find a recovered task and open its file. Check the task’s access with an account outside the team. A recovered task record only proves that one part of the app is back.
What can you take with you if you switch services?
Firestore and Firebase Authentication have separate exports. You will also need the original uploads, the rules that protected them and a plan for replacing the parts of your app that call Firebase.
| Part | Export or transfer | Check before switching |
|---|---|---|
| Task records | Use Firestore’s managed export to Cloud Storage. It requires Blaze and the appropriate permissions. | Check that the destination can import or convert the format. |
| Accounts | Export Firebase Authentication users as JSON or CSV. | Check which password formats the destination accepts and whether people can still sign in. |
| Files and access rules | Inventory the original files and how the app uses them. | Open a copied test attachment and confirm the new permissions still match the board’s sharing rules. |
On a small screen, scroll the table sideways to read every column.
When would you keep a board up to date without a refresh?
Firestore can listen for changes. That helps if two teammates need to see the same board while they work. Choose which records the open screen listens to so it requests what the user can see.
Check what the board shows after the connection drops and when a member loses access. Those are more useful tests than seeing one task update in a demo. Measure reads with a small test board before deciding how much live behavior to add.
Where can you learn the next steps?
- Test sign-in and access as separate jobsUse ordinary accounts to check confirmation, expired sessions and attempts to open another person’s private information.