Skip to content

General

General

Categories

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

690 results found

  1. A document always maintain createdAt / updatedAt timestamp value internally. But these fields can't be used for ordering documents.

    For example :-

    (This is possible)

    await citiesRef.orderBy('name').limit(3).get();

    (This is NOT possible)

    await citiesRef.orderBy('created_at').limit(3).get();

    Currently if we need order by timestamp, we need to maintain a separate timestamp field alongside internal createdAt / updatedAt fields. Then create index over that additional field to perform order by timestamp.

    Similar to name sentinel, firestore should provide created_at and updated_at sentinel for ordering document. These sentinel should work without any new index, ascending or descending order.

    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)
  2. Right now the SDK generated only has init with decoder.

    public init(from decoder: any Decoder)

    This limits us in generating the Previews for the views. Please consider adding additional inits with all variables in the struct

    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  ·  Data Connect  ·  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. 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)
  4. /__/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)
  5. 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)
  6. 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)
  7. 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)
  8. KYAw Min paing

    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)
  9. 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)
  10. 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)
  11. Create Api for Firebase Admin SDK to get analytics data.

    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)
  12. 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)
  13. 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)
  14. 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)
  15. 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)
  16. Consider the scenario where you create a new Remote Config parameter in your template.json file and deploy it via the Firebase CLI to TEST and PROD environments with a default value. You then modify the value in PROD via the Firebase console. The next time you deploy Remote Config to PROD the value is overwritten. It would be useful for CI/CD deployments to have an option that would only deploy new parameters and would NOT overwrite the values for existing parameters. This would allow you to structure your template.json file to have default values for new non-PROD environments without having…

    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  ·  Remote Config  ·  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. The current procedure for setting CORS rules for a bucket is horrendous from a developer standpoint. One has to download and install a CLI called gsutil, which requires Python. The CLI must be configured and authenticated. Then one has to create a JSON-file with the desired CORS-rules and run a single command with the CLI. How is this not possible to accomplish in the web GUI?

    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)
  18. Firebase should offer a built-in feature to automatically detect changes to Cloud Functions and deploy only those functions, grouped into manageable batches to avoid rate limits. This feature would streamline deployments by:

    • Scanning the project directory to identify functions with modified code since the last deployment.
    • Automatically batching the deployment of changed functions based on rate limit thresholds (e.g., 8-10 functions per batch).
    • Handling the deployment process transparently within the Firebase CLI or CI/CD integrations, reducing manual intervention.

    This functionality would save time, minimize deployment errors, and improve developer workflows, particularly in large projects with numerous functions.

    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)
  19. PLEASE update punycode version, I get this:
    (node:26660) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
    (Use node --trace-deprecation ... to show where the warning was created)

    └─┬ firebase-tools@13.25.0
    ├─┬ ajv@6.12.6
    │ └─┬ uri-js@4.4.1
    │ └── punycode@2.3.1
    └─┬ superstatic@9.1.0
    └─┬ fast-url-parser@1.1.3
    └── punycode@1.4.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

    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)
  20. 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)
  • Don't see your idea?