Skip to content

General

General

Categories

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

1232 results found

  1. Firebase should add .bd domain extenstion. already info.bd is added. why not .bd?

    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

    1 comment  ·  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)
  2. Dear Google,

    I contact from Movitel in Mozambique,
    Currently we deploy new Prefix +25888xxxxx for MSISDN , but it not yet update by google, to ensure services for customer when receive otp from google applicaition.
    I want to contact to need your help

    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  ·  Authentication  ·  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. Emulator ports can currently only be configured statically in the "emulators" block of firebase.json (or interactively via "firebase init emulators"). There is no way to set or override a port at invocation time.

    This is especially painful in CI and parallel test runs: running multiple emulator suites concurrently (e.g. sharded test jobs on one runner) requires generating a distinct firebase.json per shard just to change port numbers.

    A good solution are optional, per-emulator port flags on emulators:start and emulators:exec that override the corresponding firebase.json values, for example:

    firebase emulators:start --firestore-port 8081 --auth-port 9098 --functions-port 5002 --ui-port 4001

    Precedence: CLI flag…

    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)
  4. Description:

    Add an in-place upgrade from Firestore Standard to Enterprise edition — a single button in the console (or a gcloud flag) that converts our existing database, with no downtime and no application code changes.

    Today there's no in-place path. The edition is fixed at creation, so the only route is to provision a new Enterprise database and copy data over via export/import or the Dataflow firestore-to-firestore template. The problems:

    • It's a point-in-time copy, not a live cutover — so there's effective downtime unless we build our own dual-write/backfill.
    • Only documents move; indexes, TTL policies, and other settings must be…
    9 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)
  5. The document view for firebase is really a pain when you need to navgate or access specific documents you have to scroll and it becomes a pain when you are quickly looking for something in the 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

    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)
  6. 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)
  7. It would be great if the App Testing Agent could persist a user session or saved app state between test runs. This would allow tests to start from a predefined state instead of always going through the onboarding or login flow, making it much easier and faster to test authenticated features and later stages of the app.

    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. Des musiques social et spirituels pour motiver et faire réfléchir les gens
    Vidéo alléchantes

    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)
  9. restore old firestore browser behavior where only part of long entries where visible. Now when browser show entire value of props usability dropds to ZERO for any recored with long texts of maps...

    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  ·  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. Firestore should support a simple language like the rule language that allows modifying the data before sending it to clients.

    The primary use case is changing or hiding some fields depending on the auth uid

    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)
  11. Currently, when configuring a refresh condition on a query, the condition can only evaluate the triggering mutation's variables and auth (uid/token). We cannot check the actual result (response) of the mutation.

    This creates a significant friction point when mutations are executed from non-client environments, such as a Cloud Function triggered by another backend service (e.g., Firebase Storage). Because the Cloud Function executes without the end-user's auth context, the only way to accurately filter the query refresh is to pass the userId into the mutation's variables. This feels like an unnecessary workaround just to satisfy the refresh condition.

    To make real-time…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release a service that after staring into your devices camera for 20 seconds will log you into any account email platform or social media that's ever log your face and stored it in the cloud

    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)
  13. قيام التطبيق بالحجز عند الأطباء ورفع روشته المريض لطلب الادويه من الصيدليات

    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)
  14. This SDK will help developer, who wants to develop web/portal/application with PHP.
    PHP is secure language if used properly, PHP Is not dead

    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  ·  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)
  15. We are encountering a block when placing our project under VPC Service Controls enforcement. When a user attempts to access the Storage tab in the Firebase Console, it fails with an "Unknown Error" (Audit logs show NOMATCHINGACCESS_LEVEL with an empty clientIp). The Firebase Console currently acts as an internal proxy, routing traffic through Google's internal infrastructure. Because it traverses these internal paths, the end-user's local corporate egress IP is entirely stripped before the API payload reaches the protected Storage endpoint (storage.googleapis.com). We have strict compliance requirements to restrict access solely to trusted corporate network IPs, meaning the standard…

    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)
  16. Problem:Currently, finding the total number of documents inside a Firestore collection requires building custom client-side listeners or cloud functions to maintain manual counter fields. This adds boilerplate code, introduces latency, and risks running into write rate limitations unless complex distributed counters are built.Proposed Solution:Firebase should provide an out-of-the-box, native SDK method (e.g., a simple client-side function) that securely requests the exact document count from the server's index layer without needing to download, fetch, or bill for individual document data payloads.Why this matters:This feature is critical for building cheap, efficient pagination UI, analytics dashboards, and status trackers without incurring massive read…

    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  ·  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. Making business account anything help him

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. I'd like to submit a feature request for a first-party payment service within the Firebase ecosystem — tentatively called Firebase Payments.

    The Problem

    Firebase does an excellent job abstracting away common backend concerns — authentication, real-time databases, cloud functions, push notifications, and hosting. However, one critical backend responsibility remains entirely unaddressed: payment processing and subscription management.

    Today, developers who build on Firebase must wire together third-party providers (Stripe, Razorpay, Paddle, etc.) manually, manage webhooks, store transaction state in Firestore themselves, and handle currency normalization independently across regions. This introduces significant complexity, maintenance overhead, and security surface area — all of…

    8 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)
  19. 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 Distribution  ·  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. We are currently using the Firebase Testing Agent for automated testing of our React Native mobile application.

    One major limitation for us is the current 5-minute maximum test duration. Our real user flows include authentication, navigation, API loading, and media/content interactions, so even the login process alone can sometimes take around 3.5 minutes before the actual test scenario begins.

    Because of this, many realistic end-to-end test cases cannot be completed within the current limit.

    It would be extremely helpful if Firebase could:

    Increase the maximum test duration beyond 5 minutes, or
    Provide configurable/custom timeout options, or
    Offer optimization recommendations/features for…

    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 Distribution  ·  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?