Skip to content

General

General

Categories

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

728 results found

  1. Ability to search collections and documents in the Firestore UI.

    84 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

    5 comments  ·  Firestore  ·  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. We would like to build and run our XCTest cases using the latest Xcode 16. According to 'gcloud firebase test ios versions list' the latest supported Xcode version is 15.3.

    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

    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)
  3. 15 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  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. I love that data connect supports {.._expr: "auth.uid"} to define server value based on Firebase auth token.

    What about other CEL operations?

    I want the ability to perform simple transformation using GraphQL variables, Firebase auth token and current timestamp. For example: _expr: "'hello from ' + auth.email"

    I want the ability to combine data from different sources. Like execute a query and then use its result to perform another query or mutation. CEL expression can help cross reference data in previous steps.

    6 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)
  5. Support web for Test Lab so I can test my PWA's on real devices

    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

    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)
  6. /__/auth/handler

    Identical to hosting but for app hosting.

    Would definitely make things simpler for Next.js apps.

    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

    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)
  7. What feature would you like to see?
    I would like to see Firebase add official support for the Linux platform. This enhancement would allow developers to build applications that leverage Firebase services natively on Linux, enabling broader platform compatibility and empowering Linux-based applications.

    Why would it be useful?
    Adding Linux support would:

    Enable developers to integrate Firebase services directly into Linux-based applications.
    Provide parity with other supported platforms (e.g., iOS, Android, Web).
    Open up Firebase's powerful features (e.g., authentication, cloud storage, Firestore) to a growing user base on Linux desktop and server environments.

    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

    0 comments  ·  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)
  8. What feature would you like to see?
    I would like to see Firebase add official support for the Linux platform. This enhancement would allow developers to build applications that leverage Firebase services natively on Linux, enabling broader platform compatibility and empowering Linux-based applications.

    Why would it be useful?
    Adding Linux support would:

    Enable developers to integrate Firebase services directly into Linux-based applications.
    Provide parity with other supported platforms (e.g., iOS, Android, Web).
    Open up Firebase's powerful features (e.g., authentication, cloud storage, Firestore) to a growing user base on Linux desktop and server environments.

    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

    0 comments  ·  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)
  9. 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.

    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

    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)
  10. A solid Firebase Functions experience requires a fully functional test suite.
    Firebase-functions-test is already there, and provides the experience, but is often forgotten for months.

    Firebase functions 6 was released a month ago, and it broke functions-test.

    There's currently a patch that fixes it, and it's been there for a week.

    This idea isn't about this issue. It's about giving resources to the firebase-functions-text project, so it can continue growing and thus giving cloud firebase functions users a solid testing experience before deploying.

    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)
  11. It would be nice if we can set our custom Postgres instance connection string so that we can use postgres instances outside the Google Cloud infrastructure.

    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)
  12. FCM must support targeting all users in HTTP v1 API by App Package Name via 'to' parameter in addition to 'topic', 'condition' and 'device token' as like available in FCM console. More suitable targeting parameter may also be added.

    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. It's not clear in the documentation nor by implementation that secrets work with scheduled cloud functions. This seems to me like a major missing feature in security and consistency with the v2 cloud functions. Is the only solution using the cloud config for api keys/secrets?

    We need to have something like:

    exports.someScheduledFunction = onSchedule(
    {
    schedule: "every 60 minutes",
    timeoutSeconds: 100,
    secrets: [someToken.name],
    },
    async () => {
    logInfo("Running every 60 min");

    ...
    }
    );

    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)
  14. It's not clear in the documentation nor by implementation that secrets work with scheduled cloud functions. This seems to me like a major missing feature in security and consistency with the v2 cloud functions. Is the only solution using the cloud config for api keys/secrets? Something like:

    exports.someScheduledFunction = onSchedule(
    {
    schedule: "every 60 minutes",
    timeoutSeconds: 100,
    secrets: [someToken.name],
    },
    async () => {
    logInfo("Running every 60 min");

    ...
    }
    );

    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)
  15. 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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. I have read this article https://firebase.google.com/docs/firestore/solutions/geoqueries in mentions cool examples on how to implement Geohashes, but I can't find python examples. Is there a recommended way of implementing geohashes on Firebase Admin SDK for python?

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Outside the office, I work on an 11" Chromebook and the console layout is not at all user-friendly for screens that are not large.
    The spaces in the appbarr, title, navigation and footer bars take up a lot of space and are fixed, the content of the page that is left for editing is very limited, having to scroll each line and some services do not even have space to open the item to be consulted, like in analytics, for example, some cards are truncated.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Add Remix (https://remix.run) as one of the supported frameworks to deploy apps. It is rather similar to Next.js in many ways so that should be possible.

    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

    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)
  19. I suggest that Firebase enhances the Firestore console by adding support for keyboard navigation, allowing users to move between documents using the up and down arrow keys. This feature would improve accessibility and efficiency, especially for users who prefer using the keyboard over the mouse or trackpad. Implementing this functionality would make data management in Firestore more user-friendly and accessible to a wider range of users.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Currently the events exported from Firebase to BigQuery don't have the issue state, which requires additional work to check the issue state without the information on when the state was updated.

    The proposal is that real-time exporting can consider the issue state at the time of receiving the event.

    E.g.
    - Issue ID 1 currently has an open state
    - Issue ID 1 receives event ID A at 10:30am
    - Issue ID 1 is set to a closed state at 10:31am
    - Issue ID 1 receives event ID B at 10:32am
    - BigQuery has event ID A set as open…

    7 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)
1 2 8 10 12 36 37
  • Don't see your idea?