DEV Community

Cover image for One Firebase project, three named databases — stop losing your place
AppoBase
AppoBase

Posted on

One Firebase project, three named databases — stop losing your place

The switcher tax

A lot of Firebase projects now use more than one named Firestore database.

In the console you flip a switcher, wait for the tree to reload, and hope you remember which filters belonged to which database. Open Auth or Storage and you lose the document context you just had. By afternoon you are not “managing data.” You are recovering context.

What isolated tabs fix

AppoBase is a local Mac/Windows client. Each named database can sit in its own tab with isolated state — queries, history, and tree position stay with that database instead of collapsing into one switcher.

You still keep billing and project admin in Google’s console. The daily path is the desktop window: documents, query builder (filters or JavaScript), history with replay, and Auth + Storage when you need them beside the tree.

Honest scope

This is not multiplayer Google Cloud IAM. It is not Linux/mobile. Other desktop GUIs exist; only claim what appobase.com lists. Spelling: AppoBase.

Pricing (truth only)

Free to start (1 project). Pro $6.49 / month. 3-day trial. 14-day refund from first payment.

Download: appobase.com

Top comments (0)