2140 results found
-
Avoiding mock functions, placeholders, and demo functions.
A recurring problem with Gemini is that when asked to implement functions, it often generates mock functions, placeholders, or demo code instead of real, production-ready logic. This makes the output more suitable for prototypes and proofs of concept, but useless in actual development or production environments. To solve this, Gemini should follow a strict mode-based rule. In prototype mode, it may generate mock data or placeholder functions for quick demonstrations. However, in development or production mode, it must always deliver fully functional, non-mock implementations. This ensures projects remain practical, reliable, and ready for real-world deployment.
2 votes -
Avoiding mock functions, placeholders, and demo functions.
Gemini should be told a rule that never provide mock functions, placeholders and demo
most of the time i see this issue, when i asked it to add a function it add mock functions, just a demo project.
this is making useless projects it mean only that firebase studio can be only used for prototype.
In rules, which it should always follow this rule can be set as mode
if mode is prototype then it can go for placeholders and mock data but if its development or production then this is useless with mock or placeholder building the apps.I…
2 votes -
Auto build Dev.nix preview for any project that is started with git hub Repo
When a user create a new project and link it with a github repo , it should create dev.nix file and preview automatically by reading the project instead user needed this to build manually.
Same should be done if user uploaded a project to firebase studio.3 votes -
Saving chat convo per task like in cursor ide
Current chat feature in prototyper gets too long and going back to previous request is difficult. It would be nice to create a separate chat convo per task. The prototyper will auto save the task and giving it a title or description about the task. This way it is easier to go back to the task if we want to update or revise related to the task. At the same time easily restore the code to that particular task
2 votes -
History Restore option
Implement a version control or history tracking system for your workspace that allows you to view and restore previous states of your features. Specifically, add a "history restore" option accessible through the user interface, enabling you to revert to a prior version of the feature if the latest changes cause issues and history navigation is currently unavailable. Ensure that this system maintains a reliable history log, provides an intuitive restore function, and integrates seamlessly with existing workspace functionalities.
5 votes -
only 5 projects should be able to have 30 projects?
needing to add more projects
2 votes -
Edit Project UI in Preview Window
Add the option to edit the UI of the current project in the preview window (Like Lovable) For example, once the code is generated for a landing page, allow me to edit the text directly in the preview window as opposed to doing this in the code directly.
4 votes -
Add an option to open a project directly in code view
There is no option in Firebase studio, to open a project directly in code view. If you wish to do so, first you have to click on a project, opens in prototyper mode, but then you have to quickly switch to code view.
3 votes -
Map Firebase Data Connect (FDC) schema to custom postgres schema (not PUBLIC)
Currently, any gql files placed in schema folder generate one FDC schema in FDC console, which generates associated tables in postgres PUBLIC schema. Putting tables there is not ideal.
It would be nice if creating additional subfolders within schema source folder (or some other mechanism) could allow mapping to developer defined postgres schemas other than PUBLIC. For example, the following folder structure:
schema/appname/*.gql
would map to APPNAME schema in Postgres and tables would be created there.
3 votes -
المشغل ضغط الملفات بيئة التطوير في كل مرة عند إرسال المطالبة عبر
ضغط الملفات في بيئة التطوير للتقيل من حجم البيانات المرسلة عبر المشغل عندما يقوم بقراءة ملفات المشروع في كل مرة لتنفيذ المطالبة الأخيرة والرجوع بالنتائج في عملية المعالجة المطالبة
4 votes -
Permettre à Firebase Studio de développer des applications mobiles (et de les publier automatiquement sur le Play Store / App Store).
Firebase Studio permet de générer une application web en quelques minutes à partir d'un simple prompt.
Mon idée est d'élargir le champ des possibles (vous n'avez pas idée à quel point cela sera révolutionnaire) en permettant de développer des applications mobiles avec Firebase Studio.
4 votes -
اريد نموذج قوي وحديث
اريد كود قوي وفعال من اجل ابلاغ ريبورت على انتهاك شخصيه
2 votes -
Bulk Topic Subscription Operations
In some apps, it is desirable for a user to subscribe to multiple topics by default, and it also is desireable to allow users to subscribe to/unsubscribe from many topics at once. For example, "I want all/no weather notifications" may entail subscribing/unsubscribing to "thunderstorm-warnings", "thunderstorm-watches", "tornados-warnings", "tornado-watches", etc, for all the topics of that type in your app.
Currently, you have to make one API call for each of these. This is very slow, has unnecessary network overhead, and complicates calling code.
My proposed feature: add "subscribeToTopics" and "unsubscribeFromTopics" methods to the SDKs. The signature would be (depedning on the…
3 votes -
Proposal for long term, low footprint (minimize tokens) written memory of conversations, tasks and goals.
I propose a long term feature that allows users to enable an auto-management of a "diary" that logs session activities and summarizes as you use studio.
There is the short term and long term aspect of this feature. During the current session, since its ephemeral, when major conversation topic shifts or efforts shift, we notate that in the short term memory; every time we reload a new session, we review the past short term, summarize/compress , and add it to our long term "memory" or diary. Then we start fresh for the day, with some context of the past efforts.…
4 votes -
2 votes
-
1 vote
-
unknown
Do not do any unintended/unknown changes to existing UI or backend or functionality that is already developed and approved by the user to prototyper
1 vote -
firebase_messaging windows support
Add windows support for firebase_messaging
1 vote -
Firebase studio to support source code in google drive.
That's when it would start feeling like VSCode. I would even go further and suggest, all the gcp artifacts could reside on my google drive folder hierarchy.
- source code files
- artifact registry
- infra automation code
- static hosting files.
- Resource usage and billing on google sheets.
If that's a big ask, provide a way to map the above GCP resources as a google drive.
It gives so much comfort that all is in my drive and I can search/copy/paste with file explorer !!
3 votes -
Superior Version
I propose creating a "Superior Paid Option" that would provide subscribers with technical developer assistance in situations where the built-in LLM is not capable of overcoming complex tasks. It could be a simple Chat Option, but at the very least, an email option to allow creative people with great ideas (but lack the technical ability) to flourish. The "Paid Option" could also provide for better LLM options and can go towards more dedicated software improvements to make this application "Ultra" amazing!
3 votes
- Don't see your idea?