Skip to content

General

General

Categories

(thinking…)

I suggest that Firebase...

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

765 results found

  1. Hosting CDN cache stale-while-revalidate

    Time-to-first-byte from Firebase Functions is usually slow (more than 500ms) even without cold start, sometimes (with cold starts) TTFB becomes absolutely unacceptable for projects where performance is important. SSRed HTML is also not Brotli compressed as static files.
    This is a really big problem to deploy SSR web apps to Firebase IMO, and cache SWR at the CDN layer (edge) would solve it perfectly.

    5 votes
    0 comments  ·  Hosting  ·  Admin →
    How important is this to you?

  2. Crashlytics will report different stacks as different crash

    Currently exception events are gathered as one issue depending solely on the actual exception location and its type.
    Moreover, every such event pops all previous ones as regressed.
    This makes it hard to follow the different issues. It is specifically a big problem where a fallback is used, with non-fatal crash reports in it. All crashes that ended up with the fallback are reported as one.
    My suggestion is that different call stack and/or message will be shown as different issues. (Possibly with an option to set the differing place in the stack)

    2 votes
    1 comment  ·  Crashlytics  ·  Admin →
    How important is this to you?

  3. Allow URLs to be accessible fully, or by invitation, or by password protection, like Notion and Figma

    Allow natively what we can do in Notion / Figma (sharing a prototype), by sharing a page with the followings options:
    1/ allow a page to be fully accessible (that's already possible, so the default)
    2/ allow a page to be viewed only if we provide another User a link.
    3/ allow a page to be viewed if 2/ + password protected

    11 votes
    1 comment  ·  Hosting  ·  Admin →
    How important is this to you?

  4. Does Native Support for Authentication for EHR Providers like Epic and Cerner

    Authentication is a difficult part of getting healthcare apps out there, and rightfully so, patient data security is hugely important. If Firebase offered this natively, not only would development be faster, but fewer mistakes/vulnerabilities would be present in healthcare apps that integrate with EHR.

    1 vote
    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

  5. disable deleting an entire collection if it's in production

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

  6. Firebase AppCheck (something like ReCaptcha Enterprise) for Expo React Native Android web app projects

    How can I install Firebase AppCheck in my Expo React Native Android web app project? This app is deployed on Google play console registered as webapp on firebase.

    ReCaptcha Enterprise

    1 vote
    1 comment  ·  App Check  ·  Admin →
    How important is this to you?

  7. Streaming

    To implement userfriendly generative AI applications it is import to stream data produced by LLMs back to the users browser. Firebase currently buffers all content and only returns when data is complete. Is the firebase team planning to implement this?

    4 votes
    1 comment  ·  Cloud Functions for Firebase  ·  Admin →
    How important is this to you?

  8. Restrict Unauthenticated PURGE requests

    At the moment Hosting is using Varnish cache which developers do not have access so they can't configure it, this leaves a small window for people to continuously Purge the page and increase the developer's usage

    10 votes
    1 comment  ·  Hosting  ·  Admin →
    How important is this to you?

  9. Firestore Index Name

    As a Firestore project grows, so do the number of Composite Indexes.

    While the fields are visible, being able to name a composite index would allow us to define which specific feature(s) a composite index is tied to, allowing us to remove unused indexes if they're no longer relevant.

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

  10. should be able to sort data and select data with criteria on different fields

    should be able to sort data and select data with criteria on different fields (the limitation section on https://firebase.google.com/docs/firestore/query-data/order-limit-data?hl=en&authuser=0)

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

  11. getDownloadURL method in the Admin SDK

    11 votes
    1 comment  ·  Cloud Storage for Firebase  ·  Admin →
    How important is this to you?

  12. Add Bulk User Update to SDK

    Add a bulk update user method to avoid handling the user configuration update limit of 10/s in code. Specifically, my use case is to bulk disable/enable users in a single call.

    1 vote
    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

  13. support Google OneLogin

    1 vote
    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

  14. HTTPS Proxy with Authentication

    Firebase currently does not have a clear way of supporting HTTPS proxy. If the network is limited by OEM's restrictions, or firewalls then Firebase Crashlytics won't operate. Probably no Firebase service will be able to work.

    We can set the domain and the port for HTTP proxy, but then it is not authenticated.

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

  15. Support hierarchical google-services.json

    When you define multiple build types for your application you need to create a google-services.json file for each build type, eg : app/src/flavor1, app/src/flavor2, app/src/flavor_3

    This becomes cumbersome when using multiple build flavors. It would be great if
    1. the flavor directories acted as optional overrides of a default
    2. the hierarchy for google-services.json respected initWith, e.. if I create a buildType1 with "initWith debug" I should be able to use the debug/google-services.json unless I try to overwrite it.

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

  16. Expose subcollections as json fields

    Currently, subcollections are treated separately from fields in the UI. This seems like an arbitrary distinction - a subcollection is simply a json object under a document. You could do the same thing with a string field.

    The API could support retrieving subcollections as string fields in json format for a document. This would prevent the need to iterate over every document in a collection, then get a list of the subcollections, then retrieve the documents from those subcollections, etc. If worried about time required, since Firestore supports 100 nesting levels, perhaps the API call could include the nesting level…

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

  17. Put the button to run a query on bottom not top in the console's query builder

    In the console, after building a query in the query builder, one has to scroll up again and again to run it, it's an inconvenience when the query is long and has to be changed multiple times.
    Putting the button at the bottom can make it easier to change and test out queries

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

  18. TTL for Realtime DB

    Realtime DB is very similar to Redis functionality. It would be very valuable to enable real caching behaviour by adding time to live to an entry.

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

  19. Allow security rules to validate custom bearer tokens

    Currently, Firestore and Cloud Storage security rules req.auth property will only validate and accept Google-signed ID tokens from Firebase Auth/Identity Platform.

    This means that "user authentication rules" CANNOT be used if we rely on our own (or 3rd-party) authentication/token server.

    Proposal:
    Allow security rules to configure the token verification rules so that they can verify the token claims of a configured token authority. For example, tokens signed by a service account private key, or 3rd party auth server (aside from Firebase Auth/Identity Platform).

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

  20. firebase framework sveltekit environment (vite mode mode)

    in a svelte-kit app if you have multiple environments (staging, production) you can specify multiple .env files.

    Unfortunately, there is no way to tell Firebase which one to use so it always deploys using production. and always uses development in the emulator

    3 votes
    0 comments  ·  Firebase CLI  ·  Admin →
    How important is this to you?
1 2 … 27 29 31 … 38 39
  • Don't see your idea?