1247 results found

1. Please remove all the AI stuff about having Gemini write us a barista app

   The Firebase console used to be intuitive to navigate. Now if I am trying to find my Crashlytics settings there are all these buttons in my face inviting me to let Gemini create a barista app. No one wants to create a barista app, can you please move all this stuff over to some other system hyping agents somewhere else?

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Our Project has been suspended last two days

   Our Project is suspended from last two days and has been restored yet..

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Alert on live activity updates

   Live Activity pushes are meant to be completely silent background updates, so Firebase’s requirement for an alert field is technically incorrect and creates unnecessary sound/vibration issues.

   When sending APNs messages with "apns-push-type": "liveactivity" via Firebase Cloud Messaging (FCM), the service currently requires an "aps.alert" field to be present in the payload.

   However, Live Activity updates are designed by Apple to be silent background updates, they should not display alerts, play sounds, or trigger any user-visible notification behavior.

   Because FCM enforces the presence of "aps.alert", developers are forced to include dummy or empty alert values (e.g. "alert": {}), which can still cause unwanted side effects or violate Apple’s Live Activity design guidelines.

   Live Activity pushes are meant to be completely silent background updates, so Firebase’s requirement for an alert field is technically incorrect and creates unnecessary sound/vibration issues.

   When sending APNs messages with "apns-push-type": "liveactivity" via Firebase Cloud Messaging (FCM), the service currently requires an "aps.alert" field to be present in the payload.

   However, Live Activity updates are designed by Apple to be silent background updates, they should not display alerts, play sounds, or trigger any user-visible notification behavior.

   Because FCM enforces the presence of "aps.alert", developers are forced to include dummy or empty alert values (e.g. "alert": {}), which can still… more

   17 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  In-App Messaging  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. restore old firestore browser behavior where only part of long entries where visible.

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

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. I dislike your new UI for A/B testing; it's extremely difficult to use. Configurations aren't readily apparent; the page shrinks to the righ

   I dislike your new UI for A/B testing; it's extremely difficult to use. Configurations aren't readily apparent; the page shrinks to the right sidebar, which is visually unpleasant. New configurations can't be created immediately, unlike in the previous mode. Starting a test requires creating a new condition; otherwise, the test won't be at the highest priority under the same configuration, and users will end up using other conditions within the same configuration. It's difficult to use, very difficult to use.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. First-class Firebase SDK support for Kotlin/Wasm and Compose Multiplatform Web

   Please add first-class Firebase SDK support for Kotlin/Wasm, especially for Compose Multiplatform Web apps.

   Kotlin/Wasm is becoming an important target for sharing Kotlin and Compose UI across Android and Web. Today, Firebase works well on Android and through the JavaScript SDK on Web, but Kotlin/Wasm integration is still awkward and requires wrappers, JS interop, REST calls, or platform-specific abstractions.

   It would be very useful to have official support for Auth, Remote Config, Realtime Database, Firestore, Analytics, and Storage from Kotlin/Wasm.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  SDKs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Allow Firebase project root to be configured independently of firebase.json location

   The Firebase CLI currently appears to treat the directory containing "firebase.json" as the effective root directory for the Firebase project.

   While "--config" allows "firebase.json" itself to be moved, moving the config file also changes how relative paths inside that configuration are resolved.

   This creates an awkward limitation for monorepos, where configuration files may naturally live in an infrastructure/configuration directory while build artifacts remain at the workspace root.

   It would be useful if the Firebase CLI allowed the configuration file location and the project root to be specified independently.

   Example

   Consider an Nx monorepo structured like this:

   repo/
   ├── apps/
   ├── libs/
   ├── dist/
   │ └── apps/
   │ └── web/
   ├── infrastructure/
   │ └── firebase/
   │ ├── firebase.json
   │ ├── firestore.rules
   │ ├── firestore.indexes.json
   │ └── storage.rules
   ├── nx.json
   └── package.json

   From an organizational standpoint, keeping Firebase-specific infrastructure under:

   infrastructure/firebase/

   is desirable.

   The CLI supports selecting that file:

   firebase deploy --config infrastructure/firebase/firebase.json

   However, if the Hosting configuration contains:

   {
   "hosting": {
   "public": "dist/apps/web"
   }
   }

   the path is effectively resolved relative to:

   infrastructure/firebase/

   rather than the actual workspace root.

   The build output produced by Nx is located at:

   repo/dist/apps/web

   so moving "firebase.json" also unintentionally changes the filesystem context of the Firebase project.

   Current workaround

   The practical workaround is to leave "firebase.json" at the workspace root:

   repo/
   ├── firebase.json
   ├── apps/
   ├── libs/
   ├── dist/
   └── infrastructure/
   └── firebase/
   ├── firestore.rules
   ├── firestore.indexes.json
   └── storage.rules

   and then reference Firebase-specific files from the root configuration.

   This works, but it means "firebase.json" becomes a special root-level file purely because its location controls the CLI's filesystem context.

   In larger monorepos, that makes Firebase configuration harder to organize consistently with other infrastructure.

   Proposed behavior

   It would be useful to provide a way to explicitly specify the Firebase project root separately from the config file.

   For example, a CLI option:

   firebase deploy \
   --config infrastructure/firebase/firebase.json \
   --project-root .

   or perhaps a configuration property:

   {
   "root": "../../",
   "hosting": {
   "public": "dist/apps/web"
   }
   }

   The exact API is less important than allowing these two concepts to be independent:

   1. Location of "firebase.json"
   2. Root directory used for resolving project-relative paths

   Why this matters

   This becomes particularly useful in monorepos using tools such as Nx, where:

   • application source lives under "apps/"
   • shared code lives under "libs/" or "packages/"
   • build artifacts are emitted to a workspace-level "dist/"
   • deployment/infrastructure configuration may live under "infrastructure/"

   In that structure, the location of a Firebase configuration file is an organizational concern and doesn't necessarily represent the root of the application workspace.

   Separating the config location from the project root would make Firebase CLI behavior more flexible without changing the existing default behavior.

   Backwards compatibility

   Existing behavior could remain unchanged when no explicit project root is supplied.

   For example:

   firebase deploy

   would continue using the directory containing "firebase.json" as it does today.

   Only users who explicitly provide a root would get the new behavior.

   Additional context

   I initially expected "--config" to control only which Firebase configuration file was loaded.

   The surprising part was discovering that relocating the configuration also effectively relocates the filesystem context used by Firebase.

   A separate root option would make "--config" much more useful for monorepo and infrastructure-oriented repository layouts.

   The Firebase CLI currently appears to treat the directory containing "firebase.json" as the effective root directory for the Firebase project.

   While "--config" allows "firebase.json" itself to be moved, moving the config file also changes how relative paths inside that configuration are resolved.

   This creates an awkward limitation for monorepos, where configuration files may naturally live in an infrastructure/configuration directory while build artifacts remain at the workspace root.

   It would be useful if the Firebase CLI allowed the configuration file location and the project root to be specified independently.

   Example

   Consider an Nx monorepo structured like this:

   repo/
   ├── apps/
   ├──… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase CLI  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Samuel

   Markus

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Agent Skills & MCP Server  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release

   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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Authentication  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Good App put on teachers and the liners

    This app is very very intelligent is good from teachers underlying all the student the healthy us from exam or question you can solve it

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Documentation  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Table Event Triggers

    In additional to the onMutationExecuted, we would love to have events on table mutations.

    • onRowUpdated
    • onRowCreated
    • onRowDeleted

    onMutationExecuted is already launched in Nov 2026. https://firebase.blog/posts/2025/11/dataconnect-nov25

    12 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  SQL Connect (Data Connect)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Add support for pnpm workspaces

    While it does support for pnpm, it does not support pnpm workspaces. The reason for this is because it currently looks for the pnpm-lock.yaml file in the workspace app directory, but this file is actually in the root directory when using workspaces. This causes lots it to switch to using npm and the build to fail.

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Provide Native Document Counters and Metadata for Firestore Collections

    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 costs on large production databases.

    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… more

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. car racing game

    Online Gaming Platform – Project Requirements Document

    1. Platform Name

    ---

    2. Project Objective

    The platform will provide a secure online gaming experience where users can create accounts, verify their identity, manage a digital wallet, and participate in games. The system will include secure payment processing, user verification, and fair gameplay mechanisms.

    3. User Registration

    • Full Name
    • Mobile Number
    • Email Address
    • Password
    • OTP Verification
    • Age Verification (where legally required)

    4. Identity Verification (KYC)

    • Government ID Upload
    • Selfie Verification
    • Mobile Number Verification
    • Email Verification
    • KYC Approval Status

    5. Digital Wallet System

    The platform will include a secure wallet that allows users to:

    • View Balance
    • View Transaction History
    • Deposit Funds
    • Withdraw Funds
    • Monitor Account Activity

    6. Payment System

    Supported payment methods may include:

    • Digital Banks
    • Mobile Wallets
    • Bank Transfers
    • Debit/Credit Cards

    All payment transactions will be processed through secure, encrypted channels.

    7. Gaming Features

    • Multiplayer Game Modes
    • Leaderboards
    • Ranking System
    • Match History
    • Fair Play System
    • Anti-Cheat Protection

    8. User Dashboard

    • User Profile
    • Wallet Balance
    • Game History
    • Achievements
    • Notifications
    • Account Settings

    9. Admin Panel

    • User Management
    • KYC Approval Management
    • Transaction Monitoring
    • Reports and Analytics
    • Security Monitoring
    • Customer Support Tools

    10. Security Features

    • Two-Factor Authentication (2FA)
    • Data Encryption
    • Secure Login System
    • Fraud Detection
    • Suspicious Activity Monitoring

    11. Legal & Compliance Requirements

    • Compliance with Local Laws
    • Privacy Policy
    • Terms and Conditions
    • Age Verification Requirements
    • Financial Compliance Standards

    12. Future Enhancements

    • Android Application
    • iOS Application
    • Live Chat Support
    • Referral Program
    • Tournament System
    • Multi-Language Support
    • AI-Based Security Monitoring

    Project Summary

    This project aims to build a modern, secure, and scalable online gaming platform with user registration, identity verification, digital wallet management, secure payment integration, fair gameplay systems, and a professional administration panel.

    Online Gaming Platform – Project Requirements Document

    1. Platform Name

    ---

    2. Project Objective

    The platform will provide a secure online gaming experience where users can create accounts, verify their identity, manage a digital wallet, and participate in games. The system will include secure payment processing, user verification, and fair gameplay mechanisms.

    3. User Registration

    • Full Name
    • Mobile Number
    • Email Address
    • Password
    • OTP Verification
    • Age Verification (where legally required)

    4. Identity Verification (KYC)

    • Government ID Upload
    • Selfie Verification
    • Mobile Number Verification
    • Email Verification
    • KYC Approval Status

    5. Digital Wallet System

    The platform will include a secure wallet that allows users to:

    • … more
    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. App Distribution should have at least basic management of email notifications

    There is no option to set email preferences for tester groups in Firebase App Distribution. It is unnecessary to pester everyone with emails when they can find the last app version in App Tester.

    60 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    10 comments  ·  App Distribution  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Look into Gemini Ai as well as Google Ai concentrate on permissions and time ie. Min, hour etc etc

    Look into Gemini Ai as well as Google Ai

    7 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Cancel Extensions Deprecation

    Continue offering the Extensions service, do not shut it down.

    Extensions are a core feature of Firebase, and the work required for customers to replace them is unacceptable.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Improve SEO Support for Content-Driven Websites

    I suggest that Firebase improve its support for content-driven websites by adding better SEO tools, enhanced static site optimization, and easier integration with search engines.

    I manage a gaming website called TomodachiLifeROM, where I publish game guides, tutorials, and gaming resources. Features such as built-in sitemap generation, improved metadata management, better structured data support, and more detailed performance recommendations would make Firebase Hosting even more useful for publishers.

    https://support.google.com/sites/thread/451587408?hl=en&sjid=16379941293809233418-EU

    It would also be helpful to have clearer documentation and examples for deploying SEO-friendly websites while maintaining excellent performance.

    Thank you for considering this suggestion.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Firestore Enterprise, array indexes failure

    In Firestore Enterprise, array indexes can be created in the index management view without throwing any errors or warnings. However, when executing queries that rely on array operations (such as array-contains or array-contains-any), the query engine completely ignores the created array index and falls back to a full table scan.
    ​This creates significant issues for setups migrating from Firestore Standard, where array indexes are commonly used to handle multi-document references and array-based lookups.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. firebase init hosting:github environment secret

    The firebase init hosting:github command should support creating secrets for a GitHub environment for better security posture.

    https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets#creating-secrets-for-an-environment

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase CLI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating