2219 results found

1. linux

   What feature would you like to see?
   I would like to see FlutterFire plugins add support for the Linux platform. This enhancement would allow developers to build applications that leverage Firebase services on Linux, enabling cross-platform compatibility and expanding Flutter's reach.

   Why would it be useful?
   Adding Linux support would:

   Enable developers to target a wider range of platforms with their Flutter apps.
   Provide parity with other supported platforms (e.g., iOS, Android, Web).
   Leverage Firebase's capabilities (e.g., authentication, cloud storage, and Firestore) in desktop environments where Linux is widely used.

   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  ·  Crashlytics  ·  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. API for NotebookLM

   Developer api to interact with notebooklm

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

3. Do not require third-party cookies

   A service released in 2023 should not require third-party cookies to be allowed.
   If not for the privacy and usability for its users, then for the project itself, since many browsers are phasing out support for third-party cookies. Firefox already blocks them and chrome will soon do the same:
   https://developer.chrome.com/en/docs/privacy-sandbox/third-party-cookie-phase-out/

   81 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

   under review  ·  3 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. Allow configuring standard Firebase Authentication via Terraform

   The google Terraform providers allow creating and configuring Firebase projects via Terraform.

   This includes Firebase Authentication via the googleidentityplatform_config Terraform resource, but also forces an upgrade to Firebase Authentication with Identity Platform.

   Identity Platform has a much higher cost.

   We'd like to be able to configure standard Firebase Authentication via Terraform

   5 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

5. Give access to dir outside home like /opt, /mnt. etc.

   It is getting hard to setup the existing open source project on google idx as we only has access to /home dir and all other are only in read only mode which is making hard for use to develop new project on the idx

   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  ·  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. Documenting Schema and Connections

   One of the things that was important to me when developing clients in Apollo graphql is the playground.
   You should be able to create a document with a proper description.
   And currently, description using “”” is only possible for schema type. It is also needed for query, mutation.
   And we need to be able to generate them with the SDK and then see them in the client code.

   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

7. CLI deploy and link blocking functions

   Function Deployment & Validation Flow:

   When deploying cloud functions with recognized lifecycle hook names (e.g., beforeCreate, beforeSignin), the system should:

   .
   Detect Blocking Function Patterns
   Check if the deployed function's name matches known blocking trigger conventions.

   .
   Assignment Validation
   Verify whether the detected function is registered as a blocking trigger in the system configuration.

   .
   Interactive Guidance
   If unassigned, display CLI prompt:
   "Seems like you want to deploy a 'Blocking' function named <FUNCTION_NAME> but no blocking trigger is assigned. To configure this function visit: <CONSOLE URL>"

   .
   Key Function Patterns:

   beforeCreate | beforeSignin | afterSignout | customBeforeHook
   

   Why This Matters:

   Proactively addresses common configuration gaps through contextual prompts, reducing deployment errors and cognitive load for developers while maintaining automation compatibility.

   Function Deployment & Validation Flow:

   When deploying cloud functions with recognized lifecycle hook names (e.g., beforeCreate, beforeSignin), the system should:

   .
   Detect Blocking Function Patterns
   Check if the deployed function's name matches known blocking trigger conventions.

   .
   Assignment Validation
   Verify whether the detected function is registered as a blocking trigger in the system configuration.

   .
   Interactive Guidance
   If unassigned, display CLI prompt:
   "Seems like you want to deploy a 'Blocking' function named <FUNCTION_NAME> but no blocking trigger is assigned. To configure this function visit: <CONSOLE URL>"

   .
   Key Function Patterns:

   beforeCreate | beforeSignin | afterSignout | customBeforeHook
   

   Why This Matters:

   … 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  ·  Firebase CLI  ·  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

8. CLI deploy and link blocking functions

   Function Deployment & Validation Flow:
   When deploying cloud functions with recognized lifecycle hook names (e.g., beforeCreate, beforeSignin), the system should:

   Detect Blocking Function Patterns
   Check if the deployed function's name matches known blocking trigger conventions.

   Assignment Validation
   Verify whether the detected function is registered as a blocking trigger in the system configuration.

   Interactive Guidance
   If unassigned, display CLI prompt:
   "Seems like you want to deploy a 'Blocking' function named <FUNCTION_NAME> but no blocking trigger is assigned. Would you like to configure this function now? (y/N)"

   Key Function Patterns:
   ```
   beforeCreate | beforeSignin | afterSignout | customBeforeHook

   (Additional supported hooks)

   
   Why This Matters:
   Proactively addresses common configuration gaps through contextual prompts, reducing deployment errors and cognitive load for developers while maintaining automation compatibility.
   

   Function Deployment & Validation Flow:
   When deploying cloud functions with recognized lifecycle hook names (e.g., beforeCreate, beforeSignin), the system should:

   Detect Blocking Function Patterns
   Check if the deployed function's name matches known blocking trigger conventions.

   Assignment Validation
   Verify whether the detected function is registered as a blocking trigger in the system configuration.

   Interactive Guidance
   If unassigned, display CLI prompt:
   "Seems like you want to deploy a 'Blocking' function named <FUNCTION_NAME> but no blocking trigger is assigned. Would you like to configure this function now? (y/N)"

   Key Function Patterns:
   ```
   beforeCreate | beforeSignin | afterSignout | customBeforeHook

   (Additional supported hooks)

   
   Why

   … 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  ·  Firebase CLI  ·  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. CollIDE

   Collaboration and Communication

   It would be nice to have the ability to join an IRC chat or some sort of chat within the project so you could collaborate with other individuals, including the ability to paste spots in the code another can click and look at, pastebins, quick access to bug trackers with the ability to paste the links as well, and all the tools you need to organize your project.

   Gemini Suggestions

   Ok, love the suggestions in grey though they are a bit slow.

   So, if there were a chat interface, it would be nice to have a chat bot with commands where i could say take the last 50 lines and boil it down to suggestions, not of code, but of architectural decisions or different ways to implement the solution to a problem.

   Also such a bot would be able to record decisions onto a jira board, for example, or jot down notes of the discussions using natural commands.

   Package Metasearch

   I would love to see metasearch for maven, npm, etc.

   Supply Chain Analysis

   This is where you could really shine. People are aware of and scared of supply chain attacks. Though they may be rare, that's not what risk managers care about.

   It would be nice to have a graphical tool to administer all of the package managers. The tool could show the status of a package's signature or whether it was published by npm, how dormant a project is, etc. Maybe a mouseover that shows their github activity graph for the proceeding 12 month period.

   *Conclusion

   If you take ideas seriously, I'm a vision guy. Not a great coder, but I always think from the user perspective. So, great job on this project, it's excellent.

   Disclosure
   This post has been edited by the author for clarity. It was a very rough first draft.

   Collaboration and Communication

   It would be nice to have the ability to join an IRC chat or some sort of chat within the project so you could collaborate with other individuals, including the ability to paste spots in the code another can click and look at, pastebins, quick access to bug trackers with the ability to paste the links as well, and all the tools you need to organize your project.

   Gemini Suggestions

   Ok, love the suggestions in grey though they are a bit slow.

   So, if there were a chat interface, it would be nice to have a chat… more

   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

   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. Analytics Admin Sdk

    Create Api for Firebase Admin SDK to get analytics data.

    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

    1 comment  ·  Analytics  ·  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. Firebase Admin Lite

    Right now you can't host Firebase on Cloudflare, Vercel Edge Functions, Bun, or Deno without using the "Firestore Lite" package. However, there are no "auth" functions, and no access to admin functions. We will need to create server sessions etc on the server. This cannot be done in NON NodeJS environments without the REST API. There needs to be a Firebase Admin Lite package, or the very least add an "auth" lite package.

    12 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

    3 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

12. Suggestion for Enhanced Authentication Flow in Firebase Authentication

    Dear Firebase Support Team,

    I hope this message finds you well. I am reaching out to share a suggestion that I believe could greatly benefit Firebase Authentication and developers working on more complex applications.

    Currently, Firebase Authentication provides excellent flexibility with signInWithPhoneNumber and createUserWithEmailAndPassword, allowing projects to authenticate users using either a phone number or an email/password combination. However, in certain projects, both the phone number and email/password are essential to meet higher security standards and user profile requirements.

    In these cases, having an integrated authentication flow that combines signInWithPhoneNumber and createUserWithEmailAndPassword within a single, cohesive process would be highly valuable. This would allow developers to:

    Verify both Phone Number and Email in one seamless flow, ensuring that both contact methods are valid.
    Enhance Security and User Experience by allowing users to use either their phone number or email for future logins, while maintaining a smooth registration process.
    Create a More Complete User Profile right from the start, which is especially useful for applications that require strong user verification for sensitive data or financial transactions.
    Currently, implementing both methods within the same authentication process involves a multi-step workaround that can complicate the onboarding experience. A built-in support mechanism from Firebase could simplify this flow for developers and improve the overall user experience.

    I hope this suggestion resonates with your team and aligns with Firebase’s mission to provide developers with powerful, user-friendly tools. I would be thrilled to see this feature implemented in a future release.

    Thank you for considering this idea, and please let me know if I can provide any additional details.

    Best regards,

    Nicolas N'DAH

    Dear Firebase Support Team,

    I hope this message finds you well. I am reaching out to share a suggestion that I believe could greatly benefit Firebase Authentication and developers working on more complex applications.

    Currently, Firebase Authentication provides excellent flexibility with signInWithPhoneNumber and createUserWithEmailAndPassword, allowing projects to authenticate users using either a phone number or an email/password combination. However, in certain projects, both the phone number and email/password are essential to meet higher security standards and user profile requirements.

    In these cases, having an integrated authentication flow that combines signInWithPhoneNumber and createUserWithEmailAndPassword within a single, cohesive process would be highly… 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

13. Delivery logging in iOS

    Does anyone know why Firebase doesn't support notification delivery on iOS? This is supported by other messaging frameworks such as OneSignal by hooking into Notification Service Extensions.

    Firebase does have a FIRMessagingExtensionHelper class which has an exportDeliveryMetricsToBigQuery method — however I didn't see references to this in the docs, how it should be used, or whether it suits my needs.

    The ideal scenario is that Firebase can just report iOS delivery rates in the console. It's confusing to me why this is not made simple, and if anyone has some insight here it would be much appreciated.

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

14. API Revoke Token

    Simple API to revoke the token/refresh token from a backend without using the SDK.

    20 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

    4 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

15. Request Query Parameters for Security Rules

    Introduce a request.query.parameters object to store key-value pairs from the query payload, enabling conditional access control based on user authentication state.

    Current workarounds, like nesting documents in sub-collections, restrict uniqueness to a single field. This proposal allows queries to be filtered dynamically based on multiple conditions.

    For example, access can be restricted based on user authentication state or location.

    if request.query.parameters.user == request.auth.uid
    if request.query.parameters.location == request.auth.token.region
    if request.query.parameters.email != null
    if request.query.parameters.email == request.auth.email
    

    Privileged searches can be enabled with conditions such as:

    if request.query.parameters.key == request.auth.token.vipkey
    

    Range queries can be implemented using a function object to validate if a value is in range or test its min/max bounds.

    if request.query.parameters.age == 37
    if request.query.parameters.age.valid(37)
    if request.query.parameters.age.min(17)
    

    This approach prevents excessive database reads by filtering queries early, keeps operations lightweight and efficient, separates query logic from request.query for better maintainability, and provides more flexibility in data access without rigid document structures. It ensures data segregation while maintaining query performance.

    the key take away is fine control over queries that could otherwise be hijacked or manipulated from the client, leading to excessive reads, exposing unwanted documents, or even conflict with regulatory requirements.

    Introduce a request.query.parameters object to store key-value pairs from the query payload, enabling conditional access control based on user authentication state.

    Current workarounds, like nesting documents in sub-collections, restrict uniqueness to a single field. This proposal allows queries to be filtered dynamically based on multiple conditions.

    For example, access can be restricted based on user authentication state or location.

    if request.query.parameters.user == request.auth.uid
    if request.query.parameters.location == request.auth.token.region
    if request.query.parameters.email != null
    if request.query.parameters.email == request.auth.email
    

    Privileged searches can be enabled with conditions such as:

    if request.query.parameters.key == request.auth.token.vipkey
    

    Range queries can be implemented using a function object to validate if… 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  ·  Firestore  ·  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

16. Support a repl/shell in firebase CLI

    Some operations can only be preformed through the firebase-admin SDK, or sometimes you just want to run/test some Firestore query.

    The Firebase CLI can provide a "shell" command that opens a Node.js REPL with the firebase-admin SDK preconfigured and global variables such as "db", "auth" that you can then use to interact with Firebase.

    This was so much needed that I implemented this by myself in our project as a custom package.json scripts.

    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 CLI  ·  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. Support skipping deploy targets that are configured empty

    Sometimes you have deploy target that you want to not deploy in some projects.

    Currently if a deploy target is not configured or empty, the CLI will error.

    It would be nice if it just skipped deploying that configuration if the deploy target is explicitly configured empty.

    This is also useful to allow varying configuration in different projects, as you can deploy different target configurations depending on the selected project this way.

    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 CLI  ·  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. have a unity sdk for dataconnect

    I'd like a Unity SDK for DataConnect

    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

    1 comment  ·  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. We've detected suspicious activity on one of your workspaces. Please contact support for further assistance
    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

20. Improve new project form by enabling common services

    When creating a new project, I wish you guys add multiple checkboxes for common features just like you did for Flutter checkbox, common feat

    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