Skip to content

General

General

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

724 results found

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  In-App Messaging  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Cloud Messaging  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Analytics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Allow configuration of velocity alerts for overall crash rate rather than individually spiking crashes.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Crashlytics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. According to
    https://firebase.google.com/docs/auth/web/email-link-auth#default-email
    and
    https://github.com/firebase/firebase-js-sdk/issues/2574
    The email sign in template contains a timestamp in the email title and body, so email are not collapsed into a sigle thread.

    I believe the current date time format, such as 2024 November 11 13:33 UTC is not user friendly, and should be replaced with a more readable format, such as Nov. 11, 2024, 11:33.

    The mail language is already based on the language set in the Firebase Authentication -> Template language section, so the formatting can be done based on the same setting, or a new option can be added in the Firebase…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Data Connect automatically queues and applies database schema migrations as you make changes to your application's schema including destructive migration detection and diff approval.

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. firebase currently has two firebase auth triggers:
    functions.auth.user().onCreate()
    functions.auth.user().onDelete()

    I would like a trigger to respond to onLinkWithCredential so that I can update the user document in the user collection with the additional/changes from the new auth method

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Enable VertexAI web access for googleSearchRetrieval() and Grounding to work on the FirebaseVertexAI.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. If bad JSON is sent to a cloud function, for example if the function is an API endpoint, the body-parse in Firebase Functions will throw an HTML response error before and user function code is run.

    This is a really bad experience for endpoint users where instead of a formatted JSON error message, they get a strange HTML response.

    The body-parser used in by Firebase Functions should pass along the error instead of returning the response.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. create a UI for managing environment variables and surfacing build error messages in the Firebase console (so you don't have to go into CloudBuild)

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  0 comments  ·  App Hosting  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Currently the dataconnect:sdk:generate command in firebase-tools will generate functions for queries and mutations. There are cases where having TypeScript interface reflections of the schema types would also be beneficial.

    AFAIK there's no existing tooling that will conveniently do this mapping (due missing types that one can find in .dataconnect/schema/prelude.gql when the emulator is running).

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Simple API to revoke the token/refresh token from a backend without using the SDK.

    19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. A Hard Spending Limit option in Firebase Billing settings would allow developers to set an absolute cap on resource spending for their Firebase projects. Once this limit is reached, Firebase would automatically pause or throttle resources to prevent any charges beyond the specified amount. This feature would enhance budget control and predictability for developers and organizations of all sizes.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. There is no possibility to accept Firebase Terms of Service automatically (or at least manually in advance, without the need to go through manual Firebase project creation process) when using Firebase via Terraform.
    When trying to create a Firebase project using Terraform (add googlefirebaseproject resource), apparently unaccepted ToS cause 403 "Error creating Project".
    After at least one Firebase project is created manually via Firebase Console, creation project via Terraform works.
    It would be great to separate accepting ToS from project creation or at least improve error message in this case.
    Here are some examples:
    https://stackoverflow.com/a/79345435/14866192

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Some applications are very dependent (in performance perspective) on resources from CDNs & backend location - it would be great if we can choose location of the Test Lab's device location (preferably Android real devices) to set it closer to CDN & backend.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Test Lab  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?