FirestoreWhat it is, and why it's in our toolbox
Document database with offline sync, security rules as code and realtime listeners — mobile's default database until measured otherwise.
Why Chimbuk uses it
Rules are unit-tested in CI; every collection gets documented read models and server-authored updates. Boring, auditable, works offline.
How we work with it
The working rule on every engagement: a technology stays only while it pays rent — in developer speed, runtime performance, hosting cost or hiring availability for your future team. Firestore passed that test; the written case for it (and its honest trade-offs) goes into your project's decision log, so nobody has to reverse-engineer the reasoning after handover.
In this studio today
You can see firestore doing real work on this very site and across the Concept Lab demos — including the CSS-rendered device screens on /concepts — and, where it concerns shipped product, in the verified work ledger under our own Google Play label.
Used in these practices
Begin the ascent
Want Firestore doing this kind of work for you?
Tell us what you're building — we'll say honestly whether this tool (or a duller one) wins.