2216 results found

1. Flag specific files or even code sections as DO NOT TOUCH for the agent

   I've had plenty of projects where unexpected (an often unnecesary) changes to config files break the app and it usually takes multiple rollbacks to go back to the stable version .
   I've seen this specially happen in config files (.env,firestore.rules,etc) where configs are set to invalid values and unless they get caught in the file diffs they make us think the problem is with the new generated code when acutally is a base setup that has been changed.

   would it be possible to flag certain files (eg .ai-ignore file) or annotate code in some way to let the coding agent know that section is "only humans allowed" and should not be changed using generated code.

   I've had plenty of projects where unexpected (an often unnecesary) changes to config files break the app and it usually takes multiple rollbacks to go back to the stable version .
   I've seen this specially happen in config files (.env,firestore.rules,etc) where configs are set to invalid values and unless they get caught in the file diffs they make us think the problem is with the new generated code when acutally is a base setup that has been changed.

   would it be possible to flag certain files (eg .ai-ignore file) or annotate code in some way to let the coding agent… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Discussion option in Chat

   In other Ai coding studios, there is a discussion button in the chat. This means you can ask a question of the Ai without it making changes to your app. This reduces errors and enables the user to clarify with the AI particular functions or ideas before implementing them.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Merging projects

   It would be nice to be able to merge projects. If you have multiple apps that may need to communicated to one another and read from the same data base, but you dont want to build a monolith, you should be able to merge the projects in a way that you can build the functionality between the apps so they can all talk to one another

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Partial No-Code options

   Has option to switch to partial no-code like Adalo, where developers can select the type of layouts, colors, move or drag the options, as it would be more easy to do for some cases than chatting/vibe coding

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. 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.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Data Connect  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. المشغل ضغط الملفات بيئة التطوير في كل مرة عند إرسال المطالبة عبر

   ضغط الملفات في بيئة التطوير للتقيل من حجم البيانات المرسلة عبر المشغل عندما يقوم بقراءة ملفات المشروع في كل مرة لتنفيذ المطالبة الأخيرة والرجوع بالنتائج في عملية المعالجة المطالبة

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. 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 language): (topics: Array<string>) => Promise<void> and would subscribe to/unsubscribe from the passed topics in one call.

   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… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Cloud Messaging  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. 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. And if there was an active goal or task at hand, we can have that marked as the "current topic" or maybe track a few topics at the same time. The goal is to have a low footprint, writte, non-ephemeral diary, connected to your workspace and project, that will keep a log/diary of your events in a simple way that mimics long term understanding of the goal of the user without parsing through logs and logs of data, files and files of the project, or volumes of markdown documentation, just to work on your project.

    The expected results will be that everytime Firebase studio crashes, or we reconnect, gemini prototyper, or gemini CLI, or even Gemini Code Assist, can read this diary and quickly be up to speed on the project definition, project goals, status and most recent conversation/tasks --- AND --- uses the most minimal amount of tokens needed to process the next set of queries and conversations.

    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.… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Provide a Migration Path for Existing Links in Printed Media (QR Codes) after FDL EOL (Similar to goo.gl Approach)

    ・The Problem:

    The Firebase Dynamic Links EOL on Aug 25, 2025, will cause millions of FDL links embedded as QR codes in printed textbooks to return 404 errors. These physical materials cannot be updated, creating a critical issue for the education sector and our publishing clients. The official migration guide does not offer a solution for these existing, unchangeable links.

    ・Precedent:

    Google has already solved this exact problem for another service. The Google Developers Blog recently announced that goo.gl links will be preserved because they are "embedded in countless documents, videos, posts and more."

    This situation with goo.gl is precisely identical to the critical issue we face with Firebase Dynamic Links. As we have explained, our publishing clients have embedded FDL-generated QR codes into printed textbooks, which cannot be altered. The very rationale that led to the preservation of goo.gl links perfectly describes the predicament of our clients.
    Our situation with FDL is identical.

    (Link: https://blog.google/technology/developers/googl-link-shortening-update/)

    ・Proposed Solutions

    Redirection-Only Grace Period
    Following the goo.gl precedent, continue to resolve and redirect existing FDLs for an extended period (e.g., 2-3 years) after the EOL date. New link creation could be disabled, but existing links should not break.

    This is a critical business continuity issue for many developers and their clients. We strongly request that the Firebase team provide a viable solution.

    ・The Problem:

    The Firebase Dynamic Links EOL on Aug 25, 2025, will cause millions of FDL links embedded as QR codes in printed textbooks to return 404 errors. These physical materials cannot be updated, creating a critical issue for the education sector and our publishing clients. The official migration guide does not offer a solution for these existing, unchangeable links.

    ・Precedent:

    Google has already solved this exact problem for another service. The Google Developers Blog recently announced that goo.gl links will be preserved because they are "embedded in countless documents, videos, posts and more."

    This situation with goo.gl is precisely… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Dynamic Links  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Better way to backup Gemini Conversations

    I use a second-brain tool that leverages markdown files (Obsidian). So I would like to be able to download each of my Gemini sessions in Markdown files to easily add to my vault. Having to export the json from the files or drag to copy and paste is not efficient or a great user experience.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Gemini in Firebase  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Subject: Proposal for Improving Firebase

    Subject: Proposal for Improving Firebase Studio for Developers with Basic Knowledge

    To the Firebase Studio Team at Google,

    I would like to offer several ideas for improving the platform, with an emphasis on making it more accessible to developers who are at the beginning of their professional journey or who have a basic level of development knowledge. Firebase Studio is a powerful tool with immense potential, and it can be made even more user-friendly and intuitive for this audience.

    The main challenge for a developer with basic knowledge is that the intelligent agent and the work environment assume a high level of prior expertise. The following suggestions focus on bridging this gap.

    Analysis and Suggestions for Improvement

    1. Adaptive Guidance:

       • The Problem: Currently, the agent suggests advanced solutions that may be too complex for a novice developer.
       • The Proposal: Develop an ability for the agent to identify the developer's expertise level. This could be based on an analysis of existing code, the types of questions asked, or even a short questionnaire at the beginning of a session. Based on the developer's level, the agent could adapt its answers and suggestions:
         • For Beginners: The agent would provide more "Boilerplate Code," break down complex tasks into small, clear steps, and offer detailed explanations of the concepts behind the code.
         • For Experts: The agent would continue to offer complex and efficient solutions as it does today.

    2. Simplifying Complex Processes with "Wizards":

       • The Problem: Configuring processes like Authentication, Security Rules, or connecting to Cloud Functions requires a deep understanding.
       • The Proposal: Instead of requiring manual code writing or configuration, integrate "Wizards" that guide the developer step-by-step. For example, a wizard for setting up Security Rules would ask the developer simple questions in plain language (e.g., "Who is allowed to read this data?", "Can only registered users write data?") and automatically generate the complex rules file.

    3. Enhanced Error Handling and Explanations:

       • The Problem: Error messages are often technical and difficult for an inexperienced developer to decipher.
       • The Proposal: When an error occurs, the agent should not only display it but also analyze it within the project's context, explain the likely cause in simple terms, and suggest concrete solutions for fixing it. For example, if a package was forgotten in the package.json file, the agent would identify this and suggest the appropriate installation command.

    4. Highlighting Basic Concepts (Conceptual Explanations):

       • The Problem: Many developers learn "how" to do something but not "why." This understanding is crucial for long-term skill development.
       • The Proposal: When the agent suggests a piece of code, it should also offer a brief and concise explanation of the concept behind it. For instance, if it suggests using Firestore, it would briefly explain what a NoSQL database is and why it is suitable for the current use case.

    5. Guided Project Templates:

       • The Problem: Starting a new project can be intimidating.
       • The Proposal: Expand the template gallery to include "guided templates." Such a template would include not only the initial code but also a series of small tasks and explanations that lead the developer through building their first feature from end to end, using the agent as a personal assistant throughout the process.

    In summary, making Firebase Studio a tool that better understands the needs of developers at the beginning of their journey will significantly broaden its user base and establish the platform as the preferred entry point for modern application development.

    Thank you for your consideration.

    Subject: Proposal for Improving Firebase Studio for Developers with Basic Knowledge

    To the Firebase Studio Team at Google,

    I would like to offer several ideas for improving the platform, with an emphasis on making it more accessible to developers who are at the beginning of their professional journey or who have a basic level of development knowledge. Firebase Studio is a powerful tool with immense potential, and it can be made even more user-friendly and intuitive for this audience.

    The main challenge for a developer with basic knowledge is that the intelligent agent and the work environment assume a high… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. ChatGPT
    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Pre-built User Authentication & Common App Features

    We propose adding a suite of pre-built, configurable modules for user authentication and other common application features directly into Firebase Studio. This would allow developers to quickly set up essential functionality without writing repetitive boilerplate code.

    Why this is important: Many developers spend significant time implementing standard features like user registration, login, and profile management. By providing these components out-of-the-box, Firebase Studio would enable developers to skip these steps and focus immediately on building their app's unique and core functionality. This would dramatically accelerate development speed and improve time-to-market.

    Core Features to Include: User Authentication Module: A ready-to-use system for user registration, sign-in, password reset, and social login (e.g., Google, Apple).

    User Profile Management: A common UI for users to view and edit their profile details.

    Role-Based Access Control (RBAC): A simple way to define and manage user roles and permissions.

    This feature would significantly enhance the value of Firebase Studio by transforming it from a data management tool into a comprehensive, rapid application development platform.

    We propose adding a suite of pre-built, configurable modules for user authentication and other common application features directly into Firebase Studio. This would allow developers to quickly set up essential functionality without writing repetitive boilerplate code.

    Why this is important: Many developers spend significant time implementing standard features like user registration, login, and profile management. By providing these components out-of-the-box, Firebase Studio would enable developers to skip these steps and focus immediately on building their app's unique and core functionality. This would dramatically accelerate development speed and improve time-to-market.

    Core Features to Include: User Authentication Module: A ready-to-use system for… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. : “Make Firebase the best home for AI + Media: Vector Search, AI Studio (Genkit), India‑first Auth, and Media Extensions”

    We’re building LegacyVerse Studio—a global, culture‑rooted AI platform (clones, memories, voice, and music). To keep Firebase at the heart of our stack, we need:

    1. Managed Vector Search for Firestore (embeddings + whereNear()),

    2. Firebase + Genkit “AI Studio” in Console (flows, tools, evals, deploy, cost dashboard),

    3. Official AI Media Extensions: Gemini TTS/STT, audio transcode to HLS/MP3, normalization, subtitles,

    4. India‑first Phone Auth improvements (DLT, fallback providers, better deliverability & pricing clarity),

    5. Edge Functions on Hosting with streaming (SSE) for low‑latency AI,

    6. Firestore TTL + simple archival tier for cost control,

    7. Built‑in multi‑tenant RBAC patterns for orgs/workspaces,

    8. Native full‑text search (Indic aware) with realtime updates,

    9. Project‑level budget & quota controls (caps, per‑user limits, AI usage analytics),

    10. Regions & data sovereignty parity in India (Auth/Functions/Extensions).

    These make Firebase the definitive platform for AI + media + multilingual apps, especially in India.
    We’re happy to share real workloads and test these features in beta. 🙏

    We’re building LegacyVerse Studio—a global, culture‑rooted AI platform (clones, memories, voice, and music). To keep Firebase at the heart of our stack, we need:

    1. Managed Vector Search for Firestore (embeddings + whereNear()),

    2. Firebase + Genkit “AI Studio” in Console (flows, tools, evals, deploy, cost dashboard),

    3. Official AI Media Extensions: Gemini TTS/STT, audio transcode to HLS/MP3, normalization, subtitles,

    4. India‑first Phone Auth improvements (DLT, fallback providers, better deliverability & pricing clarity),

    5. Edge Functions on Hosting with streaming (SSE) for low‑latency AI,

    6. Firestore TTL + simple archival tier for cost control,

    7. Built‑in multi‑tenant RBAC patterns for orgs/workspaces,

    8. Native full‑text search (Indic aware) with… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. mcp server integration

    mcp-playwright integration

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  MCP Server  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. AdMob

    (Google Ads Display & Video 360)

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Performance Monitoring  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Firebase Should Work With Kotlin Multiplatform

    KMP is now getting stable and the Firebase should be able to be used in these projects

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  SDKs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Snake app

    To exit this game

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating