2301 results found

1. I wonna create an app

   Hw will I create an app

   1 vote

   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  ·  App Distribution  ·  Edit…  ·  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. Nano Banana Pro

   I realised when adding my Gemini 3 Pro Preview API in the code the chat assistant doesnt recognize it.
   Also it cant use Nano Banana Pro still. Please add it ASAP. It´s a Google feature and Firebase is also Google.

   2 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. Allow underscores in task handler function names

   Underscores are not allowed in cloud tasks handler functions. In JS/TS hyphens are not an option (because they are not allowed in variable names) and so we are forced to use camel-cased names.

   We use underscores for all of our other function names, so we can't be consistent when naming task handlers.

   This seems like a silly constraint, even more so because it doesn't apply to other cloud function types. I've been waiting for years for this to be fixed, please make it happen.

   Request to https://cloudtasks.googleapis.com/v2/projects/myproject/locations/us-central1/queues/some_function_name had HTTP Error: 400, Queue ID "somefunctionname" can contain only letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). Queue ID must be between 1 and 100 characters.

   Underscores are not allowed in cloud tasks handler functions. In JS/TS hyphens are not an option (because they are not allowed in variable names) and so we are forced to use camel-cased names.

   We use underscores for all of our other function names, so we can't be consistent when naming task handlers.

   This seems like a silly constraint, even more so because it doesn't apply to other cloud function types. I've been waiting for years for this to be fixed, please make it happen.

   Request to https://cloudtasks.googleapis.com/v2/projects/myproject/locations/us-central1/queues/some_function_name had HTTP Error: 400, Queue ID "somefunctionname" can contain only letters… more

   1 vote

   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 Functions for Firebase  ·  Edit…  ·  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. Here is a **strong, complete, production-ready prompt** you can paste into any advanced LLM (GPT/Claude/LLaMA) to generate a **full tokenisa
   2 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  ·  App Distribution  ·  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. A Key Adjustment to Avoid Errors and Code Loss (Refactoring) in a Firebase Studio Project

   I've been developing a large-scale project using Firebase, still in the experimentation, testing, and evaluation phase of Firebase Studio's functionalities. However, I've observed that small changes made to specific parts of the project end up significantly impacting other areas that shouldn't be affected.

   This behavior creates insecurity in the development process, as minor adjustments end up compromising stable functionalities, even when there's no direct correlation between the modules.

   It's quite frustrating to see that, because of a minimal code flaw, the project can stop working completely—compromising months of work in a matter of seconds. As a safety measure, I've been making several duplications of the project to preserve functional versions. However, this quickly consumes all the contracted space and is not a sustainable solution.

   It would be extremely important to have a mechanism similar to a "restore point" or "rollback," allowing the project to revert to a previous stable state if a critical error occurs. This would guarantee greater security, control, and continuity in development, preventing isolated corrections from compromising the entire system.

   Therefore, I request an evaluation of the possibility of implementing a native internal restoration or versioning feature that protects projects against unexpected failures and minimizes impacts on the development environment.

   For example: when requesting AI to make a correction or adjustment to the code, a copy of the code would be created, the adjustment or implementation would be made, then the changes would be presented to the developer, and once the developer confirms, the functionality would be assigned to the original code, deleting the copy. If something goes wrong, the code would simply be deleted without altering the original structure, so as not to have to create copies of the project occupying server space.

   I've been developing a large-scale project using Firebase, still in the experimentation, testing, and evaluation phase of Firebase Studio's functionalities. However, I've observed that small changes made to specific parts of the project end up significantly impacting other areas that shouldn't be affected.

   This behavior creates insecurity in the development process, as minor adjustments end up compromising stable functionalities, even when there's no direct correlation between the modules.

   It's quite frustrating to see that, because of a minimal code flaw, the project can stop working completely—compromising months of work in a matter of seconds. As a safety measure, I've been… more

   3 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. Support Multiple Data Connect Services in Emulator Suite (or Allow Hybrid Cloud Fallback)

   Currently, the Firebase Emulator Suite allows running only a single Data Connect service instance locally. For projects utilizing a microservices architecture with multiple isolated Data Connect services, this creates a significant blocking issue during development.

   Primary Feature Request: Multi-Service Emulation - Please update the Emulator Suite to support running multiple Data Connect services simultaneously.

   Alternative / Interim Solution: Hybrid Cloud Fallback - If full multi-service emulation is technically complex to implement immediately, please introduce a "Hybrid" mode as an alternative.

   Current Behavior: When the emulator is running, all calls to Data Connect are forced to look locally. If a specific service isn't emulated, the call fails, even if a live version exists.

   Proposed Behavior: Allow an opt-in flag (e.g., --allow-cloud-fallback) that permits the SDK to connect to live/deployed Cloud instances for any Data Connect service not currently running in the emulator.

   Why this is critical: Support has confirmed the current "walled garden" approach is intended to prevent accidental costs. However, without multi-service support, this leaves developers in a deadlock: we cannot emulate our full stack locally, and we cannot mix local emulation with cloud resources. We are effectively forced to test entirely in production.

   Currently, the Firebase Emulator Suite allows running only a single Data Connect service instance locally. For projects utilizing a microservices architecture with multiple isolated Data Connect services, this creates a significant blocking issue during development.

   Primary Feature Request: Multi-Service Emulation - Please update the Emulator Suite to support running multiple Data Connect services simultaneously.

   Alternative / Interim Solution: Hybrid Cloud Fallback - If full multi-service emulation is technically complex to implement immediately, please introduce a "Hybrid" mode as an alternative.

   Current Behavior: When the emulator is running, all calls to Data Connect are forced to look locally. If a specific… more

   1 vote

   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  ·  Edit…  ·  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. Data Connect Event Triggers on Emulator

   Support Data Connect Event Triggers on emulator for local development. With the risk outlined in the event trigger documentation regarding infinite loops, we ought to be able to test our event triggers on emulator. Data Connect supports great local development except for the triggers, so this would be top notch!

   6 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

   2 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

8. I wish if i can integrate ai from aistudio.google.com to ai from firebase. and they can interconnect and share requirements.

   I wish if i can integrate ai from aistudio.google.com to ai from firebase. and they can interconnect and share requirements.

   2 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

9. Enable Identity Aware Proxy within Firebase Studio UI

   We’re exploring Firebase Studio as a replacement for platforms like Replit, Bolt, and Lovable for vibe-coding applications, especially because it offers seamless connectivity to private VPCs. However, one major concern is that apps become publicly accessible by default once published.

   Most vibe-coders learn cybersecurity the hard way and often end up blaming the platform, so having secure defaults is crucial. We fully support the direction Google is taking with Firebase Studio, but this issue needs to be addressed. Ideally, Firebase Studio apps should require Google authentication by default, with an explicit option for developers to make an app public only when they choose to.

   EDIT: Provide a simple option to enable Identity Aware Proxy (IAP) within the Firebase Studio UI!

   We’re exploring Firebase Studio as a replacement for platforms like Replit, Bolt, and Lovable for vibe-coding applications, especially because it offers seamless connectivity to private VPCs. However, one major concern is that apps become publicly accessible by default once published.

   Most vibe-coders learn cybersecurity the hard way and often end up blaming the platform, so having secure defaults is crucial. We fully support the direction Google is taking with Firebase Studio, but this issue needs to be addressed. Ideally, Firebase Studio apps should require Google authentication by default, with an explicit option for developers to make an app public only… more

   2 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

10. Support for Proper 404 Status Codes and Multiple 404 Pages Based on URL Patterns on Firebase Hosting

    Currently, when using a custom 404 page (e.g., 404.html), Firebase Hosting always responds with a 200 status code, even when the page is served via a rewrite rule.
    This differs from behavior on traditional servers (e.g., Nginx with the internal directive), where the server can correctly return a 404 while still serving a custom error page.

    Why this matters:
    - Proper HTTP status codes are essential for SEO.
    - Search engines may incorrectly index 404 pages if they return 200.
    - Client applications and monitoring tools rely on correct status codes.

    Additionally, In many multilingual or multi-section sites, different parts of a website require different 404 pages.
    At the moment, the only workaround is to use rewrite rules, such as:

    {
      "rewrites": [
        { "source": "/es/**", "destination": "/es/404.html" }
      ]
    }
    

    However, this still returns 200 instead of 404, which causes the same issue as above.

    Requested enhancement:
    - Allow developers to define multiple 404 handlers depending on URL patterns (e.g. /es/** → /es/404.html, /fr/** → /fr/404.html)
    - Ensure each of these handlers can return a real 404 status code

    These two capabilities would significantly improve:
    - SEO accuracy
    - Error analytics
    - User experience for multilingual or multi-section websites
    - Parity with traditional server behavior

    Thank you for considering these enhancements!

    Currently, when using a custom 404 page (e.g., 404.html), Firebase Hosting always responds with a 200 status code, even when the page is served via a rewrite rule.
    This differs from behavior on traditional servers (e.g., Nginx with the internal directive), where the server can correctly return a 404 while still serving a custom error page.

    Why this matters:
    - Proper HTTP status codes are essential for SEO.
    - Search engines may incorrectly index 404 pages if they return 200.
    - Client applications and monitoring tools rely on correct status codes.

    Additionally, In many multilingual or multi-section sites, different parts… more

    2 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  ·  Hosting  ·  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. Copy crashlytics stacktrace

    It would be nice to have a button to easily copy stacktrace from crashlytics.

    1 vote

    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  ·  Crashlytics  ·  Edit…  ·  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. database

    Provide better transaction open source database options like Postgres with Neon or MariaDB and optimized the Gemini model to interact with database to read and write schemas.

    1 vote

    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  ·  Edit…  ·  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. My history

    Name: SAKTINN
    Email: mommilk01@gmail.com
    Phone: +855 96 564 0090
    Bank Account: 100770859 (Wing Bank of Cambodia)
    Address: Pongro Village, Kampong Svay Commune, Serey Sophon District, Banteay Meanchey Province, Cambodia

    1 vote

    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  ·  Edit…  ·  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. Instruct the agent to be in the git head of the repository in the appropriate branch

    Instruct the agent to be in the git head of the repository in the appropriate branch, then to read the files it assumes it will edit, I ensure it's using the latest version of everything. This prevents many errors caused by hallucinations like outdated functions in a use case, which leads to wasted time fixing the same problem repeatedly.

    It's also important to tell it to validate that the files exist and are in the correct path. This way, the chain of thought process iterates automatically until it finds the correct files.

    I've been using this method since the update, and my experience has changed dramatically. I use Firebae Studio for about a month, roughly 14 hours a day, so I've really been able to experience the improvement. I hope this helps others.

    Instruct the agent to be in the git head of the repository in the appropriate branch, then to read the files it assumes it will edit, I ensure it's using the latest version of everything. This prevents many errors caused by hallucinations like outdated functions in a use case, which leads to wasted time fixing the same problem repeatedly.

    It's also important to tell it to validate that the files exist and are in the correct path. This way, the chain of thought process iterates automatically until it finds the correct files.

    I've been using this method since the update,… more

    3 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. apply gemini 3 pro in firebase strudio please

    i belive that we will have more control of our projects here in firebase studio than ai studio so please add gemini 3 pro in firebase studio

    7 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

16. أريد إنشاء تطبيق مدرسي يجمع بيانات التلاميذ في شكل نتائج
    1 vote

    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  ·  In-App Messaging  ·  Edit…  ·  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. Need document for MAUI

    We are using MAUI mobile application(Android & iOS). We don't have gradle. Share complete document to configure firebase crashlytics in MAUI application.

    1 vote

    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  ·  Crashlytics  ·  Edit…  ·  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. Table Event Triggers

    In additional to the onMutationExecuted, we would love to have events on table mutations.

    • onRowUpdated
    • onRowCreated
    • onRowDeleted

    onMutationExecuted is already launched in Nov 2026. https://firebase.blog/posts/2025/11/dataconnect-nov25

    3 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

19. Show parameter descriptions under their names in analytics events

    My analytics events often have several parameters with close, but slightly different meanings. I would like you to show parameter description (description of custom metric or custom dimension) I have provided in Custom Definitions right under parameter name (in however small font you like) in relevant places of Firebase Console. This is especially useful for Value parameters where I often assign one of the most important metrics of the many I track, but then forget which one I have been tracking via value. At the very least, you should always include that description as a tooltip whenever I hover over a specific parameter.

    My analytics events often have several parameters with close, but slightly different meanings. I would like you to show parameter description (description of custom metric or custom dimension) I have provided in Custom Definitions right under parameter name (in however small font you like) in relevant places of Firebase Console. This is especially useful for Value parameters where I often assign one of the most important metrics of the many I track, but then forget which one I have been tracking via value. At the very least, you should always include that description as a tooltip whenever I hover over… more

    1 vote

    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  ·  Analytics  ·  Edit…  ·  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. Gradle plugin for Data Connect Android development

    Firebase should publish a Gradle plugin for Data Connect Android development. The plugin could integrate the code generation into the build process, much like https://github.com/google/protobuf-gradle-plugin.

    1 vote

    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  ·  Edit…  ·  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