2365 results found

1. Restore Archived Dynamic Links

   Automatically Imported from Firebase

   5 votes

   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  ·  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
   AdminAnonymous (Product Manager, Google, LLC - Firebase) responded

2. 💬 Fan Engagement System • Live chat with fans • Fan polls (vote best song, etc.) • Notifications (new drops)

   🎤 Music & Content Section
   • Upload songs, freestyles, skits
   • Fans can stream/download
   • Comments + likes system

   👉 Powered by:
   • Firebase Storage (files)
   • Firestore (data)

   4 votes

   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  ·  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. Request for Premium Firebase Studio Tier with Scalable VM Specs

   Dear Firebase Team,

   I am currently using Firebase Studio for my development projects (including hsse.tech). However, I frequently encounter "disk space full" issues which disrupt my workflow.

   I would like to suggest a Premium/Paid Tier for Firebase Studio that offers Virtual Machines (VM) with higher specifications (CPU, RAM, and specifically larger Disk Space). Having a more robust, scalable environment would ensure a seamless experience for professional developers who need more than the standard resources.

   Looking forward to seeing improvements in this area.

   4 votes

   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  ·  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. make linking console to studio a button, right

   that should be a done deal

   4 votes

   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  ·  Firebase console  ·  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. Automatically resolve all issues related to running the program

   The whole point of using Gemini and Firebase studio is to be able to automate everything. So why have you guys allowed Firebase studio to still remain so dependent on human action? When trying to run a Flutter project, I get such errors: simple_notes-82575463:~/simple_notes{main}$ apt install cmake
apt is not installed, but available in package apt, press [Enter] to run it, Ctrl+C to cancel.
these 4 paths will be fetched (4.78 MiB download, 28.84 MiB unpacked):
/nix/store/763a60pi91p93np19vkhn026hig5d5w1-apt-2.7.6
/nix/store/99lfzqv23jnxp5lj11hvgaqc62qrmnwa-dpkg-1.22.1
/nix/store/y6x85gyyndgbvzvdlz1y69gs1zxsa29f-stdenv-linux
/nix/store/dn6qi0xbx9sidpis4isrncnpkhxsd2v5-xxHash-0.8.2
copying path '/nix/store/y6x85gyyndgbvzvdlz1y69gs1zxsa29f-stdenv-linux' from 'https://cache.nixos.org' to 'local-overlay://'...
copying path '/nix/store/99lfzqv23jnxp5lj11hvgaqc62qrmnwa-dpkg-1.22.1' from 'https://cache.nixos.org' to 'local-overlay://'...
copying path '/nix/store/dn6qi0xbx9sidpis4isrncnpkhxsd2v5-xxHash-0.8.2' from 'https://cache.nixos.org' to 'local-overlay://'...
copying path '/nix/store/763a60pi91p93np19vkhn026hig5d5w1-apt-2.7.6' from 'https://cache.nixos.org' to 'local-overlay://'...
E: Unable to determine a suitable packaging system type
To permanently add this package to your environment, please add pkgs.apt to the list of packages in your dev.nix file, then rebuild your environment.

   These are the kind of errors that should not even happen. Gemini should be able to automatically detect these and fix them without even asking me, and it should ensure that the program runs without any intervention from my side. As engineers, you guys need to think from the perspective of automation. Even when typing this form, I'm shown a message that I need to sign in to continue, even though I'm already signed in to my Google account. This page could have automatically signed me in but again you made me manually require to do some actions.
   Automate instead of increasing manual effort.

   The whole point of using Gemini and Firebase studio is to be able to automate everything. So why have you guys allowed Firebase studio to still remain so dependent on human action? When trying to run a Flutter project, I get such errors: simple_notes-82575463:~/simple_notes{main}$ apt install cmake
apt is not installed, but available in package apt, press [Enter] to run it, Ctrl+C to cancel.
these 4 paths will be fetched (4.78 MiB download, 28.84 MiB unpacked):
/nix/store/763a60pi91p93np19vkhn026hig5d5w1-apt-2.7.6
/nix/store/99lfzqv23jnxp5lj11hvgaqc62qrmnwa-dpkg-1.22.1
/nix/store/y6x85gyyndgbvzvdlz1y69gs1zxsa29f-stdenv-linux
/nix/store/dn6qi0xbx9sidpis4isrncnpkhxsd2v5-xxHash-0.8.2
copying path '/nix/store/y6x85gyyndgbvzvdlz1y69gs1zxsa29f-stdenv-linux' from 'https://cache.nixos.org' to 'local-overlay://'...
copying path '/nix/store/99lfzqv23jnxp5lj11hvgaqc62qrmnwa-dpkg-1.22.1' from 'https://cache.nixos.org' to 'local-overlay://'...
copying path '/nix/store/dn6qi0xbx9sidpis4isrncnpkhxsd2v5-xxHash-0.8.2' from 'https://cache.nixos.org' to… more

   4 votes

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

   4 votes

   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  ·  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. Add MQTT protocol for lightweight communication with IoT devices RealTime Database and Authentication

   Ciao,
   Attualmente sto inviando dati da dispositivi ESP8266 a Firebase Realtime Database utilizzando la libreria:
   https://github.com/mobizt/FirebaseClient

   Tuttavia, ho riscontrato un problema importante: ogni invio di dati consuma molto traffico Firebase a causa dell'handshake SSL (molto pesante per ESP8266) richiesto per ogni connessione. Questo rende l'integrazione con dispositivi IoT a basso consumo con connettività limitata molto inefficiente.

   Per questi motivi, sarebbe estremamente utile e vantaggioso avere il supporto nativo per un protocollo più leggero e ottimizzato per l'IoT, come MQTT, che ridurrebbe drasticamente l'overhead, il consumo di dati e la latenza, migliorando significativamente l'esperienza utente della piattaforma nell'ambiente IoT.

   Firebase è un'ottima soluzione, ma l'aggiunta di MQTT la renderebbe davvero completa, anche per i casi d'uso IoT più sensibili alla rete.

   Cordiali saluti,
   Sebastiano La Tona

   Ciao,
   Attualmente sto inviando dati da dispositivi ESP8266 a Firebase Realtime Database utilizzando la libreria:
   https://github.com/mobizt/FirebaseClient

   Tuttavia, ho riscontrato un problema importante: ogni invio di dati consuma molto traffico Firebase a causa dell'handshake SSL (molto pesante per ESP8266) richiesto per ogni connessione. Questo rende l'integrazione con dispositivi IoT a basso consumo con connettività limitata molto inefficiente.

   Per questi motivi, sarebbe estremamente utile e vantaggioso avere il supporto nativo per un protocollo più leggero e ottimizzato per l'IoT, come MQTT, che ridurrebbe drasticamente l'overhead, il consumo di dati e la latenza, migliorando significativamente l'esperienza utente della piattaforma nell'ambiente IoT.

   Firebase è… more

   4 votes

   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  ·  Other  ·  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. No more excuses!

   I think for the sake of the mental health of all Firebase Studio users, Gemini should be completely restricted in Firebase Studio when it comes to apologies.

   It's so hard not to end up frustrated after an hour of discussions and bug fixes of all kinds, where Gemini's only main occupation is to find the most sincere and profound apologies possible! I think even he is becoming depressed at this point.

   Joking aside, starting every text you read with a paragraph of apologies, when he doesn't even make a mistake, it's just a simple request, becomes really trying in the long run.

   Thanks Google Firebase Studio Team !

   I think for the sake of the mental health of all Firebase Studio users, Gemini should be completely restricted in Firebase Studio when it comes to apologies.

   It's so hard not to end up frustrated after an hour of discussions and bug fixes of all kinds, where Gemini's only main occupation is to find the most sincere and profound apologies possible! I think even he is becoming depressed at this point.

   Joking aside, starting every text you read with a paragraph of apologies, when he doesn't even make a mistake, it's just a simple request, becomes really trying in the… more

   4 votes

   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  ·  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. Any one hacke my phone automatically attacks how track that devices totally collapsed

   Hel that himself completely distracted.
   Only one system connected.

   4 votes

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

10. Allow setting cloud build machine type in app hosting config

    Default cloud build machine is e2-medium which only has 4GB ram
    My epic nodejs web app build will OOM on heap when i has <4 GB ram
    Please allow me to set build machine type to e2-standard-2 in apphosting.yaml

    4 votes

    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 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. Mobile app

    It's difficult to work from a mobile phone it's be great if we could format it for mobile use

    4 votes

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

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

13. Built-in App Versioning & Rollback Feature

    I’ve faced repeated issues in Firebase where making updates or major changes can lead to fatal errors. The biggest frustration is that even the rollback request often fails, leaving no reliable way to restore the project to a stable state.

    Because of this, the only solution I’m forced to use is creating a full duplicate of the entire project every time I want to make major changes. This is inefficient, time-consuming, and increases the risk of inconsistencies.

    • * * Suggestion:

    Introduce built-in versioning for apps (e.g., 1.0.0.01, following semantic versioning best practices).

    Each update/deployment should automatically create a new version checkpoint.

    Provide a version history dashboard to easily track changes, along with the commands/prompts that triggered them.

    Add a rollback mechanism to fully restore a previous version of the app (even if restoring the entire project takes time).

    • * * Benefits:

    Eliminates the need to manually duplicate projects for backup.

    Gives developers confidence to make major updates without fear of unrecoverable errors.

    Provides transparency and accountability in the development workflow.

    I’ve faced repeated issues in Firebase where making updates or major changes can lead to fatal errors. The biggest frustration is that even the rollback request often fails, leaving no reliable way to restore the project to a stable state.

    Because of this, the only solution I’m forced to use is creating a full duplicate of the entire project every time I want to make major changes. This is inefficient, time-consuming, and increases the risk of inconsistencies.

    • * * Suggestion:

    Introduce built-in versioning for apps (e.g., 1.0.0.01, following semantic versioning best practices).

    Each update/deployment should automatically create a new version… more

    4 votes

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

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

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

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

    4 votes

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

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

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

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