How It Feels To Chew Firebase Gum

You know you’re using Firebase Studio when:

  • You lose hours of time restarting your VM
  • You lose hours of time due to context loss
  • You lose hours of time due to token limits
  • You lose hours of time due to 10GB storage limits
  • You lose hours of time due to painfully slow VM CPUs.
  • You lose hours of time due to Gemini not responding
  • You spend more time troubleshooting basic functionality than coding.
  • You lose hours of time reading countless posts on these forums of other users experiencing the same exact issues you have, realizing that it is hopeless to continue troubleshooting this feeble product and that you must accept the sunken cost fallacy and cut your technical debt so that you can find another platform that can help you code and ship your app if you want to make any progress.

Does anyone else realize this app is just VS Code with some extension installed?

I’m starting to wonder how much of this project is actually meant to be a utility providing value for developers when it seems like the only thing it is doing is collecting more data for Google through Gemini.

No disrespect to the developers of Firebase Studio.

But what is your team actually doing to fix these issues?

This is my real experience using your product, and I am not the only one.

I do apologize for all of the issues you are running into.

I know it doesn’t seem like it (nor is comforting :sweat_smile:), but we are actively working on fixing these issues as quickly as we can. We are in some ways fixing a spaceship while it is flying in outerspace, so there are some pains here as fixes aren’t landing as quickly as we all like.

Thanks for taking the time to share your feedback and do stay tuned as we address a lot of these issues in the upcoming days, weeks, and beyond.

2 Likes

Thanks @kirupa, I understand what it’s like. I appreciate you taking the time to respond to this post and I wish you and the team best of luck on shipping updates.