Hey fellow developers,
We want to start by saying how incredible it is to see this community thrive. The willingness to share knowledge, help with complex problems, and showcase your work is what makes this forum a truly valuable resource. Thank you for being a part of it.
We want to share the best way we can work together to improve Firebase Studio, specifically when it comes to bugs and feature requests.
The power of this community forum
This forum is the go-to place for:
- Showcasing your projects and the amazing things you’ve built with Firebase Studio.
- Lending your expertise to help a fellow developer solve a tricky problem.
- Asking “How do I…?” questions and exploring different approaches.
- Sharing best practices and learning from your peers.
- Getting “unstuck” when you’re hitting a wall with your implementation.
- Finding out if other developers are experiencing a similar issue.
When you find a bug (and thank you for finding them!)
Your first instinct might be to post here, and that makes perfect sense! However, a busy forum can sometimes cause critical bug reports to get buried under other conversations. To ensure your voice is heard and we can act on your findings effectively, the single best thing you can do is file a report through the official support channel.
What happens when you use the official channel?
Filing a report there isn’t just sending a message into the void. It kicks off a formal process designed to get things fixed:
-
It guarantees we see it: Your report creates a trackable ticket that is immediately routed to the correct product and engineering teams.
-
It helps us fix it faster: The form asks for specific details (like product versions, replication steps, etc.). Having this structured data from the start prevents a lot of back-and-forth and helps our engineers diagnose the problem much more quickly.
-
Your report is a vote: We rely heavily on data to prioritize our work. The number of users impacted by an issue is one of several signals we use. If you want to see a bug fixed, filing a report is the most direct way to let us know you are impacted.
-
You get notified: we are committed to providing timely responses and updates as your issue is triaged, prioritized, and eventually resolved.
Our goal is to be as transparent as possible. Using the official channel helps us gather the information we need to build a better product, and it ensures you have a direct and trackable line to our team.
Please continue to use this forum to collaborate. A great practice is to file the bug first, then create a post here to say, “Hey, I’m seeing this issue and filed a report. Has anyone else found a good workaround in the meantime?”
Have an idea for a new feature?
In the same spirit, your ideas for new features and improvements are what shape the future of Firebase Studio. While it’s great to discuss ideas here, the most effective way to get them in front of our product team is through our dedicated feature request portal.
This channel allows you to see what other developers have suggested and, most importantly, vote on the ideas you like best. This voting system is a powerful signal that helps our product teams understand what our community wants most as they plan the roadmap for Firebase Studio.
Alternatively, you can submit your feature request privately through this report channel.
Thank you for your partnership and understanding. Happy building!
James obo/ Firebase Studio DevRel team