I built LazyFire, a terminal UI for Firebase Firestore inspired by lazygit.
I use Firestore a lot, but constantly switching to the Firebase Console to inspect data, run queries, or debug documents was slowing down my workflow. I wanted something that works entirely inside the terminal with keyboard navigation.
LazyFire lets you:
• browse Firestore collections and documents • inspect nested JSON easily • run queries • filter results with jq • navigate everything with vim-style keys • view Cloud Function logs
The goal is to make working with Firestore feel similar to tools like lazygit or k9s.
It's written as a CLI tool and works well if you're already developing from the terminal.
I'd love feedback from other Firebase users: - missing features - workflow improvements - bugs or UX issues
Thanks!
egosurffing•6h ago
One feature people might find interesting is the “Collection Health Scan”.
Firestore has a number of limits that are easy to hit accidentally as a project grows (document size, number of fields, nesting depth, index entry limits, etc.). LazyFire can scan collections and highlight documents that approach or exceed those limits.
I originally built this because debugging Firestore issues in the Firebase Console was slow when working with large collections.
LazyFire also supports: • browsing collections and documents • running queries • jq filtering of results • vim-style keyboard navigation • viewing Cloud Function logs
If anyone here is using Firestore at scale, I’d be curious: - what’s the most annoying thing about the Firebase Console? - are there features missing that would make a terminal tool useful?