1218 results found

1. Support background triggers (like Firestore) in Cloud Functions with Dart

   Since Support Dart in Cloud Functions was marked as completed, we can now write callable and HTTP triggered Cloud Functions in Dart. 🎯💙

   It would be good if background triggers (like when a document is created/updated in Firestore, a user is created in Authentication, etc) would also be supported.

   37 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

   3 comments  ·  Cloud Functions for Firebase  ·  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. Add "Delete Chat History" or "Reset Assistant" Button in Firebase Studio / Gemini AI

   Many developers are experiencing lag, broken context, or freezing when Firebase Studio (especially with Gemini AI integration) accumulates too much chat history. This often forces us to reset or recreate the entire project — and even then, Gemini may not respond at all.

   😫 Common issues:
   Chat lag and UI freezing as history grows.

   Inaccurate or irrelevant responses from Gemini due to old context.

   No way to manually clear or reset the AI assistant.

   Developers are forced to reset projects, which is disruptive and time-wasting.

   ✅ Suggested Solution:
   Add a simple button such as:

   “Clear Chat History” or

   “Reset Gemini Session”

   Some ideas:

   Place it at the top or settings icon in the chat window.

   Optionally prompt the user for confirmation before clearing.

   Consider auto-clearing old history after a certain time or session timeout.

   🙌 Why It Matters:
   Boosts developer productivity by keeping AI responses accurate and fast.

   Reduces frustration caused by needing to reset entire Firebase projects.

   Enhances privacy and control over shared chat context (e.g., code, data).

   It's a small UX change that solves a major usability issue.

   🧩 Bonus Suggestion:
   Also allow developers to opt-out of chat memory for sensitive projects or to start each session fresh by default.

   Thanks for your consideration — this change would dramatically improve the Firebase Studio + Gemini experience for many developers.

   Many developers are experiencing lag, broken context, or freezing when Firebase Studio (especially with Gemini AI integration) accumulates too much chat history. This often forces us to reset or recreate the entire project — and even then, Gemini may not respond at all.

   😫 Common issues:
   Chat lag and UI freezing as history grows.

   Inaccurate or irrelevant responses from Gemini due to old context.

   No way to manually clear or reset the AI assistant.

   Developers are forced to reset projects, which is disruptive and time-wasting.

   ✅ Suggested Solution:
   Add a simple button such as:

   “Clear Chat History” or

   “Reset Gemini… more

   147 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

   11 comments  ·  Gemini in Firebase  ·  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. Session Management & Device Visibility for Firebase Authentication

   Add optional session management to Firebase Authentication that creates and tracks individual login sessions per user, allowing developers/users to view active sessions with device and operating system information (derived from the User-Agent), approximate location (city/country), session creation time, and last active timestamp. The feature would enable per-device logout and selective session revocation via the Firebase Admin SDK, with optional read-only access for clients to build “logged-in devices” security UIs, while remaining privacy-safe, opt-in, and configurable without exposing raw IP addresses or User-Agent strings.

   View Complete Proposal/Request here: https://gist.github.com/12fahed/42e802890b5b887b93c66d94ceadeb2d

   30 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

   2 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

4. Enable Firebase Authentication Pre-PIN Entry on Android Devices (Android direct boot aware SDK)

   Background:
   Our application relies heavily on Firebase Authentication for seamless user experiences and data synchronization. However, we have encountered a significant limitation when the Android lock screen PIN is enabled. After a device reboot, Firebase Authentication becomes inaccessible until the user enters the PIN. This restriction disrupts our ability to interface with Firebase services immediately upon reboot.

   Issue:
   In discussions with Google, it was clarified that Firebase Authentication support is not available until the PIN is entered. This limitation impacts all our major customers who have enabled the Android lock screen PIN, causing operational delays and affecting user satisfaction.

   Request:
   We propose an enhancement to the Firebase Android SDK to enable Firebase Authentication functionality even before the user enters the PIN on reboot. This feature is urgently needed to ensure continuous authentication and access to Firebase services such as Firestore.

   Benefits:

   Continuous Access: This feature would allow our application to maintain uninterrupted access to Firebase, ensuring seamless user experiences and reliable data synchronization.

   Improved Reporting: It would facilitate real-time reporting to the cloud and enable monitoring of database changes without waiting for PIN entry.

   Consistent Ecosystem: By implementing this feature, we can avoid seeking alternative solutions, maintaining our reliance on Firebase’s robust ecosystem.

   Impact:
   The implementation of this feature will significantly enhance the usability of Firebase for applications that depend on authentication and data synchronization, especially in environments where security measures like PIN are essential.

   We believe this enhancement will greatly benefit developers and users alike, and we appreciate your consideration of this request.

   Thank you for your attention and support.

   Background:
   Our application relies heavily on Firebase Authentication for seamless user experiences and data synchronization. However, we have encountered a significant limitation when the Android lock screen PIN is enabled. After a device reboot, Firebase Authentication becomes inaccessible until the user enters the PIN. This restriction disrupts our ability to interface with Firebase services immediately upon reboot.

   Issue:
   In discussions with Google, it was clarified that Firebase Authentication support is not available until the PIN is entered. This limitation impacts all our major customers who have enabled the Android lock screen PIN, causing operational delays and affecting user satisfaction.

   Request:… more

   70 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

   19 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

5. More Advanced Filter on FPM

   Current filter in FPM dashboard is too simple with little option. The only device-based is either based on the exact model or based on OS version. I want to see more complete categories like on the Android Vital, which provides filtering based on RAM, CPU, SoC, GPU, etc.

   This way we can see which performance categories that affected the most and takes decision based on that. For example, maybe there are 2 performance issues, 1 issue only happens on 2 GB devices while the other also happens on devices with 4-6 GB RAM. This data can be matched to Play Console install base data. Lets say 50% of our use has 4-6 GB RAM while only 5% of them use device with lower than 4 GB RAM. We can prioritise to fix/improve the issue that happens on majority device first.

   Current filter in FPM dashboard is too simple with little option. The only device-based is either based on the exact model or based on OS version. I want to see more complete categories like on the Android Vital, which provides filtering based on RAM, CPU, SoC, GPU, etc.

   This way we can see which performance categories that affected the most and takes decision based on that. For example, maybe there are 2 performance issues, 1 issue only happens on 2 GB devices while the other also happens on devices with 4-6 GB RAM. This data can be matched to Play… more

   24 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  ·  Performance Monitoring  ·  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. App Testing agent (iOS)

   Hello. I really like your testing agent for Android. Please tell me if there are any plans to develop an agent for iOS?

   32 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

   3 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

7. Review the Ai Coding Output

   Review the code output of the built in Ai and Gemini 3.0 flash preview , i have recently created multiple new projects and then instructed gemini to produce my ideas and 9x/10 the app is somewhat built and with many errors and mistakes in the firebase code the app will only make it to a certin point and then suddenely it is destoryed forcing the ai to try to recover the damage it has no idea what its trying to fix and then instead of working on your own project your ai is trying to rebuild the firebase app infrastructure just to run correctly.. this is extremely frustrating but somewhat understanding currently as the firebase studio is still in preview development. also from this i feel the ai isnt designing real apps it is mostly building a simulation app that is not ready for production without a real human paid developer to take over and finalise as a home user this is very frustrating also... #betafeedback. #ijustwanttotry&buildarealworkingappnow!

   Review the code output of the built in Ai and Gemini 3.0 flash preview , i have recently created multiple new projects and then instructed gemini to produce my ideas and 9x/10 the app is somewhat built and with many errors and mistakes in the firebase code the app will only make it to a certin point and then suddenely it is destoryed forcing the ai to try to recover the damage it has no idea what its trying to fix and then instead of working on your own project your ai is trying to rebuild the firebase app infrastructure… more

   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

   7 comments  ·  Gemini in Firebase  ·  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

8. Data Connect Event Triggers on Emulator

   Support Data Connect Event Triggers on emulator for local development. With the risk outlined in the event trigger documentation regarding infinite loops, we ought to be able to test our event triggers on emulator. Data Connect supports great local development except for the triggers, so this would be top notch!

   11 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

   2 comments  ·  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

9. Realtime Query Updates

   Subscribe to realtime updates for a limited subset of queries, for example retrieving updates to specific rows or getting new items for a simple timeline.

   388 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

   40 comments  ·  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

10. Geo Querying in Data Connect

    Add extensions to allow querying by location radius. This is important for making apps especially social apps.

    10 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  ·  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

11. Live content powered by Firebase

    Just tell me: “build it” or “make it a business plan” 🚀

    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

    3 comments  ·  Cloud 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

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

    56 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

    9 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

13. firebase test files

    Our app is a file manager, and it would be great to be able to test its functionality in Firebase Test Lab by providing some simple test files and directories. Without any files, the tests are relatively useless.

    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  ·  Test Lab  ·  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. Autofill suggested indexes from query insights

    With the legacy firestore any complex query required indexing to be able to get the documents, nowadays with firestore entreprise that is not require but still the optimization is required for large collections and aggregation queries. The new query insights help you keep track of the performance and can list each query, but unlike legacy firestore they require you to manually set the details of any new index even if the modal opens from a specific query (It seems like an incomplete ux). Being able to perform this tedious task with the click of a button will be amazing.

    About the new tool: https://firebase.google.com/docs/firestore/enterprise/query-insights

    With the legacy firestore any complex query required indexing to be able to get the documents, nowadays with firestore entreprise that is not require but still the optimization is required for large collections and aggregation queries. The new query insights help you keep track of the performance and can list each query, but unlike legacy firestore they require you to manually set the details of any new index even if the modal opens from a specific query (It seems like an incomplete ux). Being able to perform this tedious task with the click of a button will be amazing.

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

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

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

16. publish a GCP / firebase documentation MCP server

    Enable fetch and query tools in an MCP server for the whole GCP, or the firebase documentation.

    9 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  ·  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

17. Firebase Payments SDK — A Unified, Platform-Agnostic Payment Service for Firebase

    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 which run counter to Firebase's core promise of letting developers ship faster.

    The Proposal: Firebase Payments SDK

    I'd like to propose a Firebase Payments service with the following capabilities:

    1. Unified Currency Management

       • Automatic multi-currency support with real-time exchange rate handling
       • Locale-aware price display (formatting, symbols, decimal conventions)
       • A single price definition in the Firebase Console that renders correctly in any region

    2. Subscription Management

       • First-class APIs for creating, updating, pausing, resuming, and cancelling subscriptions
       • Built-in support for free trials, grace periods, and proration
       • Subscription state synced automatically to Firestore, accessible via standard Firebase SDKs

    3. Platform Agnosticism

       • SDKs for Web (JS/TS), Android, iOS/macOS, and Flutter
       • No platform-specific payment logic — one unified API surface regardless of where the app runs
       • Compatibility with existing Firebase Auth (tie payments directly to Firebase user UIDs)

    4. One-Time Payments & Invoicing

       • Support for single-charge transactions alongside subscriptions
       • Optional invoice generation and email delivery

    5. Firebase Console Integration

       • A dedicated Payments dashboard showing revenue, churn, active subscribers, and failed payments
       • Webhook/event triggers via Cloud Functions (e.g., onPaymentSucceeded, onSubscriptionCancelled)
       • Firebase Extensions support for quick setup with popular processors (Stripe, PayPal, etc.)

    6. Security & Compliance

       • PCI-DSS compliant by design, similar to how Firebase Auth handles credential security
       • Firestore Security Rules extensions to gate content access behind payment status
       • Built-in SCA (Strong Customer Authentication) support for EU/UK compliance

    Why This Fits Firebase's Vision

    Every major SaaS backend platform is moving toward monetization primitives — RevenueCat for mobile, Paddle for web, Lemon Squeezy for indie developers. Firebase is uniquely positioned to offer this natively, deeply integrated with Auth, Firestore, Cloud Functions, and Remote Config (for paywall experimentation). It would close the last major gap in Firebase's backend coverage and reduce the need for developers to leave the ecosystem.

    Impact

    This feature would directly benefit indie developers, startups, and enterprise teams building subscription-based apps, marketplaces, and SaaS products on Firebase. It would also strengthen Firebase's competitive positioning against Supabase, AWS Amplify, and Back4App, all of which are gaining ground on developer mindshare.

    I'd be happy to elaborate further, provide use-case examples, or participate in any early feedback program or beta. Thank you for considering this suggestion — Firebase has been a core part of my development workflow, and this addition would make it indispensable.

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

18. Integrate with Play Integrity Standard API

    Current Firebase App Check is using the classic play integrity API, which results in rate limit easily. As a result, the token decode will fail easily as the QPS limit by play integrity api. Why not migrate to the Standard Play Integrity API which suggested by Google Play?

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

19. Email OTP Verification Code

    We should open a Firebase community discussion about Email OTP authentication.

    Firebase currently does not support native email-based OTP login (only email link or password auth).

    I want to build a passwordless system where:

    • Users sign in with email only
    • A one-time code (OTP) is sent to email
    • No passwords are stored
    • Same OTP flow is used for login, signup, and account actions

    This would provide a simpler and more secure authentication method without requiring phone numbers or passwords.

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

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

    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

    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