Skip to content

General

General

Categories

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

776 results found

  1. Transactions allow passing an options object with maxRetries, but all retries are immediate. If there are many other functions writing the same document, transactions will fail after all retries (lock will time out). Maybe a better strategy would be to delay with exponential backoff like pub sub does.

    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

    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. Same dashboard in GCP as Firestore in datastore mode. Collection storage space usage, index size, data size, etc.

    Also, for multi tenancy apps in both modes (using subcollections or multiple databases or also schemas in native mode would be nice to have) an API that can tell how much resources - space, reads, writes, etc. did each customer use, to be able to offer some kind of pay-as-you-go type of subscription.

    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

    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)
  3. 37 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

    2 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. Hosting preview channels are great, and work well for client-side code, however for full-stack apps that require a server (either for SSR or API routes), the preview channel uses to the 'main' server as a backend. It would be great if the server side code also got deployed to a new firebase function and was managed alongside the hosting preview.

    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

    0 comments  ·  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. Current data fetch is not filtered at query level and all of your config fetches to your frontend. This means for example, IOS app fetches IOS, Android and Web config if all apps fall under the same project.

    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)
  6. Crashlytics velocity alerting mechanism is very basic and it unfortunately generates a lot of false positive alerts. Support more advanced alarm settings

    30 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  ·  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)
  7. Right now, a Firebase function can only accept a request payload size up to 32Mb.
    Using it as webhook for some external APIs, we would need to have no limits or at least 100Mb limit

    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)
  8. Note: If your top priority is to use Flutter with Firebase on Windows/Linux, this may not be the best option.

    Currently, the Flutter SDKs (also known as FlutterFire) are wrappers around other existing SDKs, such as the iOS, Android, and web SDKs. This allows Flutter apps to target these platforms when using Firebase. However, if a Flutter app needs to target other platforms, it is not possible. A pure Dart SDK would allow developers to target all the devices that Flutter supports, but they would need to manually customize the integration with Google Analytics in Firebase. This manual integration could…

    34 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

    3 comments  ·  SDKs  ·  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. 36 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  ·  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)
  10. 34 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

    3 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)
  11. Currently, the Firebase CLI command can add testers to a Firebase App distribution project. But adding testers to a tester group can be done only manually on the Firebase portal. This becomes tedious for teams who maintain multiple tester groups and a large number of testers. Adding feasibility to mention to which tester group, the tester should be added in the Firebase add tester CLI command will make this process easier.

    16 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. The automatic custom schema migrations are great, but when managing an API expressed almost explicitly by the schema, there needs to be a clear dev story of how to migrate the database schema yourself, and move data in custom ways, while still allowing the exposed api to be backwards compatible. This can be very challenging with automatic migrations.

    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)
  13. Support SSR from frameworks like Nextjs in the SDK. Currently, the web sdk can only be used in client side components, severely complicating the codebase vs something like supabase which has support already baked in

    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  ·  SDKs  ·  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. 36 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)
  15. The FirebaseMessagingException class is sealed with an internal constructor and no interface. This means we cannot test our code that handles this exception because we can't create this type of exception nor can we mock it due to the lack of an interface.

    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

    0 comments  ·  SDKs  ·  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. Iterating over list of files and deleting each is wasteful as a call has to be made using the API for each file, and this can get expensive if a lot of delete operations are involved.

    I suggest a single API call that deletes all data given the required parameters. Further, the response from Firebase API will be that it has received the instruction to delete, and not when it has completed deleting as the operation might take quite a while.

    A function could look like this.

    deleteFolder({
    url: 'path',
    responsetype: 'requestreceived', // Another could be 'deletecomplete'

    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. Right now, there are two levels of pre-defined roles: "Viewer" and "Admin".

    However, sometimes you don't need all of the Admin permissions, but you still need to make some changes in the system as normal operations.
    This has been already done for App Check but not other products.


    Cloud Firestore:

    Let's take the Firestore roles as an example:

    • Cloud Datastore Viewer (A generic Firestore viewer permission)
    • Cloud Datastore User (A service account for manipulating data in the Firestore databases)
    • Cloud Datastore Owner (A generic Firestore owner permission).

    And then, there are specialized roles with viewer/admin level access for certain types…

    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

    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)
  18. Bring Gemini in Firebase into the Firebase CLI to help suggest the right CLI command for me to use based on my needs (that I describe in natural language).

    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)
  19. Currently, the screen rendering trace tool displays a list of issues, but with many items, it becomes overwhelming to sift through and identify the most significant problems.

    Specific Challenges

    • Volume of Data: With many items in the trace list, manually identifying high-impact issues is impractical.
    • Lack of Prioritization: The current list does not prioritize issues based on their impact, making it difficult to focus on what matters most.
    • Efficiency: Developers need a way to quickly pinpoint and address the most significant rendering issues to improve application performance.

    Proposed Solution

    Introduce an "Impact Sort" option in the screen rendering trace tool.…

    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)
  20. Need a .net MAUI support on Apple sign-in for authentication

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