1208 results found

1. Ability to see a text editor like view when editing Firestore field in the Firebase Console
   3 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  ·  Firestore  ·  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. List all Dynamic Links created by the REST API
   3 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
   AdminAnonymous (Product Manager, Google, LLC - Firebase) responded

3. Add "children count" to Firestore queries
   3 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  ·  Firestore  ·  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. Official Unreal support in SDKs
   3 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  ·  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

5. Throw an error message for missing App ID prefix and App Store ID
   3 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
   AdminAnonymous (Product Manager, Google, LLC - Firebase) responded

6. Add Support for Firestore Profiling to Firebase CLI
   3 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  ·  Firestore  ·  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. API to add authorized domains to the authentication module
   3 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

8. Allow the App Testing Agent to persist user state between test runs

   It would be great if the App Testing Agent could persist a user session or saved app state between test runs. This would allow tests to start from a predefined state instead of always going through the onboarding or login flow, making it much easier and faster to test authenticated features and later stages of the app.

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

9. Rap drill

   Des musiques social et spirituels pour motiver et faire réfléchir les gens
   Vidéo alléchantes

   2 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 AI Logic  ·  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. restore old firestore browser behavior where only part of long entries where visible.

    restore old firestore browser behavior where only part of long entries where visible. Now when browser show entire value of props usability dropds to ZERO for any recored with long texts of maps...

    2 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  ·  Firestore  ·  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 Native Document Counters and Metadata for Firestore Collections

    Problem:Currently, finding the total number of documents inside a Firestore collection requires building custom client-side listeners or cloud functions to maintain manual counter fields. This adds boilerplate code, introduces latency, and risks running into write rate limitations unless complex distributed counters are built.Proposed Solution:Firebase should provide an out-of-the-box, native SDK method (e.g., a simple client-side function) that securely requests the exact document count from the server's index layer without needing to download, fetch, or bill for individual document data payloads.Why this matters:This feature is critical for building cheap, efficient pagination UI, analytics dashboards, and status trackers without incurring massive read costs on large production databases.

    Problem:Currently, finding the total number of documents inside a Firestore collection requires building custom client-side listeners or cloud functions to maintain manual counter fields. This adds boilerplate code, introduces latency, and risks running into write rate limitations unless complex distributed counters are built.Proposed Solution:Firebase should provide an out-of-the-box, native SDK method (e.g., a simple client-side function) that securely requests the exact document count from the server's index layer without needing to download, fetch, or bill for individual document data payloads.Why this matters:This feature is critical for building cheap, efficient pagination UI, analytics dashboards, and status trackers without incurring massive read… more

    2 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  ·  Firestore  ·  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. Add support for pnpm workspaces

    While it does support for pnpm, it does not support pnpm workspaces. The reason for this is because it currently looks for the pnpm-lock.yaml file in the workspace app directory, but this file is actually in the root directory when using workspaces. This causes lots it to switch to using npm and the build to fail.

    2 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

13. Integrate Firebase product and developer notifications with Google Cloud Essential Contacts

    Larger customers often use Google Cloud Essential Contacts for ensuring critical notifications get to the right people. Currently Firebase product and developer communications seem to go out via email to named user accounts where the customer has no control who this goes to and it may miss its intended audience.

    It would be great if FIrebase notifications could be integrated with Google Cloud Essential Contacts to give customers more control over where critical notifications go to and to make this consistent with other Google Cloud services.

    https://docs.cloud.google.com/resource-manager/docs/managing-notification-contacts

    Thank you!

    2 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

14. More information in errors for native sql statements

    Errors in native sql statements like in _execute always result in the same "Invalid SQL statement" error without any further information, which makes it really difficult to debug. More data - for example the part of the SQL statement that is invalid - would be really helpful! Especially as this error also seems to be thrown when the SQL is perfectly fine but a wrong _execute syntax is used, which should not throw an "Invalid SQL statement" error, as it is not about SQL!

    2 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  ·  SQL Connect (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

15. Firebase Auth Expose Email Verification Status and Attempts

    Firebase Auth Expose Email Verification Status and Attempts

    We have a user that is having problems verifying. However there is no logging or debugging for this feature on firebase.

    1. Add an interface under auth to see which users have requested verification
    2. Add information about if the email was recieved, spammed, blocked, expired
    3. Visually show which accounts are not validated, pending validation, and validated.
    4. Be able to reset validation, or manually validate
    2 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

16. Gemini in firebase

    I think it would be a great idea to be able to create more one context chat with gemini , with ability to link them together , or merging them.

    Especially while gemini right now in Firebase , is very It is very distracted and does not adhere to instructions and commands and performs actions repeatedly and repeatedly outside the user's control, also it should be made more committed to the instructions and it has not been clearly indicated previously not to do so, for example if you ask to change the color of a button on the site, you will be surprised that it has made several other changes such as changing the size of the button or deleting the text above it.

    I think it would be a great idea to be able to create more one context chat with gemini , with ability to link them together , or merging them.

    Especially while gemini right now in Firebase , is very It is very distracted and does not adhere to instructions and commands and performs actions repeatedly and repeatedly outside the user's control, also it should be made more committed to the instructions and it has not been clearly indicated previously not to do so, for example if you ask to change the color of a button on the site, you… more

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

17. Request to make "flutter deploy" to allow Incremental Remote Config parameters update

    Take this case,

    An Enterprise Project with multiple Mobile Apps underneath. In our case, it is an ERP system with multiple subject-based mobile apps. Each mobile app needs to control its forced-update on the client side. Remote Config is thought to be the way forward.

    We need to have "flutter deploy" update a parameter for each app, to keep the latest version. The app will check this against its bulit-in version number. If a mismatch, then force an update. Very typical scenario.

    The issue with the current "flutter deploy" as a method to automatically update/maintain Remote Config parameter for the App, is that is erases all other parameters for all other apps in the same project !!

    A remote config file such as
    {
    "parameters": {
    "myapplatestversion": {
    "defaultValue": {
    "value": "A2001-AI0109"
    },
    "valueType": "STRING"
    }
    }
    }

    is missing a directive, to state if this is a New (Add) or Update, or Overwrite the entire project partameters.

    Currently, the firebase Console allows this sort of incremental maintenance of the project parameters. Therefore, it is only normal to expect the Deploy API to provide the same functionality of the portal.

    We are willing to help, if you need an extra hand to program the feature !

    Take this case,

    An Enterprise Project with multiple Mobile Apps underneath. In our case, it is an ERP system with multiple subject-based mobile apps. Each mobile app needs to control its forced-update on the client side. Remote Config is thought to be the way forward.

    We need to have "flutter deploy" update a parameter for each app, to keep the latest version. The app will check this against its bulit-in version number. If a mismatch, then force an update. Very typical scenario.

    The issue with the current "flutter deploy" as a method to automatically update/maintain Remote Config parameter for the… more

    2 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  ·  Remote Config  ·  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. Perform automatic rollouts only for changes to configured app directory

    I have a Next.js app within a monorepo for my Firebase project, which also includes an iOS and Android app, each in their own directories. My App Hosting backend is configured for the Next.js app directory, but it appears that the automatic rollouts feature does not take this setting into account when changes are pushed to the repo. I don't want to perform a rollout when making changes only the iOS app, for example.

    Automatic rollouts should only perform the rollout (or be able to be configured to) only when the specified app directory contains changes. Path matching is a common feature in CI/CD and I'm surprised to find that this isn't the default behavior. We should be able to specify which path(s) App Hosting monitors for changes, so that it doesn't needlessly roll out every time I make a change in the monorepo that doesn't affect the app.

    I have a Next.js app within a monorepo for my Firebase project, which also includes an iOS and Android app, each in their own directories. My App Hosting backend is configured for the Next.js app directory, but it appears that the automatic rollouts feature does not take this setting into account when changes are pushed to the repo. I don't want to perform a rollout when making changes only the iOS app, for example.

    Automatic rollouts should only perform the rollout (or be able to be configured to) only when the specified app directory contains changes. Path matching is a… more

    2 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

19. Persistent Memory & "Do Not Modify" Toggles to Protect Existing Code

    As a project becomes more developed, I've noticed that the Gemini assistant in Firebase Studio sometimes starts modifying templates, forms, and functions that were already working perfectly.

    To prevent this, I currently have to prepend a strict warning to every single prompt: "Proceed with extreme caution. Do not change the visual design, menus, structure, or any logic unrelated to this specific query: [my actual prompt]". While this workaround is effective and usually results in better code, it is tedious to write every time.

    My Suggestion: It would be incredibly helpful to implement a "Context Memory" feature with a checklist or on/off toggles. This would allow developers to explicitly mark certain functions, files, or UI layouts as "Locked/Remember" (Gemini must preserve them) and others as "Modifiable". This way, we wouldn't have to constantly use defensive prompting to protect the code that is already finished and working.

    As a project becomes more developed, I've noticed that the Gemini assistant in Firebase Studio sometimes starts modifying templates, forms, and functions that were already working perfectly.

    To prevent this, I currently have to prepend a strict warning to every single prompt: "Proceed with extreme caution. Do not change the visual design, menus, structure, or any logic unrelated to this specific query: [my actual prompt]". While this workaround is effective and usually results in better code, it is tedious to write every time.

    My Suggestion: It would be incredibly helpful to implement a "Context Memory" feature with a checklist or… more

    2 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  ·  Agent Skills  ·  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. Create a tool to import and export json data as collections in and out of firestore
    2 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  ·  Firestore  ·  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