Somewhat off topic question though: if you guys are such skilled developers to be building something as involved as this, why not just use something other than Firebase? I used Firebase mainly as a crutch when I was first getting into web dev, but feel that I’ve sorta outgrown it. Do you feel Firebase still serves developers like you well or are you developing this moreso for people like my old self?
Thanks Josh! Of course I'm using many other services other than Firebase. But Firebase even on 2026, I feel it still does what is suppose to do well. It does have many gaps tho, but tons of small projects or for beginners where it's really easy to get started with Firebase.
And surprisingly, there are still many large scale mobile app and webapps that's running on Firebase. For most of them, the local development without costing them, depends on this local emulators suite.
Compare to the alternatives like Supabase, where the team are really focused on giving best dev exps, for some reason Firebase local development has been the same for a long time.
I personally thought, giving that best dev exps locally for Firebase, could give devs a fresh of breath air for maintaining or developing new projects faster.
Why didnt you simply provision more powerful developer boxes to handle the needs of the Firebase emulator?
If runtime performance is the moat then won’t Google simply improve on these regressions using their decades of cloud database expertise with projects like Google Spanner?
—-
These are hardball questions and I feel a bit bad asking them, but I believe asking hard questions is kinder than blind adulation and support.
Hi there, don't feel bad asking these questions. In fact, i had this questions in mind too while this project was started.
Firstly, we already running of powerful dev boxes but still hitting out of memory issues in the official local emulators. These stronger machines doesn't remove Java or replaces the old console UI or able to loads tons of data.
Google should fix it and it's expected, but for some reason, they haven't really prioritized local tools for local devs. In other ways of saying, some one had to take this in hand and try it out, and well we did :)
This is really neat! I've been working on an open-source version of the Firebase Realtime Database as well that might be of interest[1]. Also written in Rust! Might be a good basis for building out the Realtime Database part of Firenook if you have any interest in supporting that as well.
Thanks and Lark looks really good and interesting!! Will definitely look into it as I do have plans to integrate Realtime Database into Firenook too :)
Awesome, not surprised to hear that Google still neglects to improve this experience, but you called out exactly why:
> [...] the only way Firebase developers can build apps without directly costing them is using the official Firebase Emulator Suite
We had started on the management UI portion of this at my old job out of similar frustrations. Felt awful seeing what should be a small/medium sized development-only application spew forth Java flotsam.
Well, right now plans are there to make Firenook to run locally perfect first. I was thinking, once it's well stable, to make it self-hosted first before thinking of any cloud versions. But I'm curious to ask, may I ask which service you're going to use it for in cloud?
Somewhat off topic question though: if you guys are such skilled developers to be building something as involved as this, why not just use something other than Firebase? I used Firebase mainly as a crutch when I was first getting into web dev, but feel that I’ve sorta outgrown it. Do you feel Firebase still serves developers like you well or are you developing this moreso for people like my old self?
Again, nice work!
And surprisingly, there are still many large scale mobile app and webapps that's running on Firebase. For most of them, the local development without costing them, depends on this local emulators suite.
Compare to the alternatives like Supabase, where the team are really focused on giving best dev exps, for some reason Firebase local development has been the same for a long time.
I personally thought, giving that best dev exps locally for Firebase, could give devs a fresh of breath air for maintaining or developing new projects faster.
Why didnt you simply provision more powerful developer boxes to handle the needs of the Firebase emulator?
If runtime performance is the moat then won’t Google simply improve on these regressions using their decades of cloud database expertise with projects like Google Spanner?
—-
These are hardball questions and I feel a bit bad asking them, but I believe asking hard questions is kinder than blind adulation and support.
Firstly, we already running of powerful dev boxes but still hitting out of memory issues in the official local emulators. These stronger machines doesn't remove Java or replaces the old console UI or able to loads tons of data.
Google should fix it and it's expected, but for some reason, they haven't really prioritized local tools for local devs. In other ways of saying, some one had to take this in hand and try it out, and well we did :)
[1] https://github.com/lark-sh/lark
> [...] the only way Firebase developers can build apps without directly costing them is using the official Firebase Emulator Suite
We had started on the management UI portion of this at my old job out of similar frustrations. Felt awful seeing what should be a small/medium sized development-only application spew forth Java flotsam.