1214 results found

1. messagerie
   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  ·  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

2. Support for "Facebook Login for Business"

   For normal apps, one can add the "product" Facebook Login.

   For apps that are categorized as "business", Facebook has this preferred auth mechanism called Facebook Login for Business (ref: https://developers.facebook.com/docs/development/create-an-app/other-app-types#step-3--select-an-app-type)

   However, the latter has more requirements than the former and doesn't seem wo work in Firebase Auth

   Users have to create a Login Configuration (which gives you a configuration id)
   When using the SDK, pass the configuration id:
   Documentation says:
   When invoking the login dialog and setting the redirect URL, include your configuration ID as an optional parameter (although scope can still be included, we recommend that you do not use it).

   For normal apps, one can add the "product" Facebook Login.

   For apps that are categorized as "business", Facebook has this preferred auth mechanism called Facebook Login for Business (ref: https://developers.facebook.com/docs/development/create-an-app/other-app-types#step-3--select-an-app-type)

   However, the latter has more requirements than the former and doesn't seem wo work in Firebase Auth

   Users have to create a Login Configuration (which gives you a configuration id)
   When using the SDK, pass the configuration id:
   Documentation says:
   When invoking the login dialog and setting the redirect URL, include your configuration ID as an optional parameter (although scope can still be included, we recommend that you do… 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  ·  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

3. Auth onUpdate trigger for v1 and v2 functions

   In the same way, we have onCreate and onDelete, it will be very helpful to have an onUpdate option. For example, so we can react to an email address change.

   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

   5 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

4. Auto-Configurable Feature Builder for Firebase/Gemini Studio

   Core Problem

   Right now, even with tools like Firebase Studio or Gemini Studio’s new AI-driven app generation, you still have to:
   • Manually configure core features like authentication (email, Google, phone, etc.), payments, and billing.
   • Navigate separate dashboards, enable/disable providers, copy keys, deploy, and wire up security.
   • There’s no “preview mode” where you can test/skip auth/payment flows during development, nor an easy toggle to include/exclude these features on the fly.

   Proposed Solution

   Auto-Configurable Feature Builder:
   A single unified interface in Firebase Studio/Gemini Studio that lets you:
   1. Describe the feature in plain language (e.g., “Add signup with Google and email, skip phone for now” or “Add monthly payments via Stripe with cancel anytime”).
   2. Instant option selector appears: You pick what providers you want (Google, email, phone, Apple, etc.), what payment models (one-time, subscription, trial, etc.), and app will auto-wire everything.
   3. Preview Toggle:
   • Enable/disable auth and payment gates with a simple toggle during dev.
   • Instantly preview the login, sign-up, or paywall screen as a user would see it.
   • Optionally, auto-generate test/demo accounts or “skip login” for rapid prototyping.
   4. Zero Manual Dashboard Setup:
   • All required back-end setup (enabling providers, rules, callbacks, webhooks, etc.) is handled behind the scenes.
   • No more jumping between consoles or copying API keys!
   5. One-click Deploy:
   • Once happy, click “Deploy” and the full flow is production-ready—no extra config.
   6. Security/Compliance Awareness:
   • The builder recommends best practices (MFA, GDPR, SCA for payments, etc.) and lets you enable them in one click.

   Bonus Features
   • Dynamic Feature Toggles: Easily turn features (auth/payment/onboarding flows) on/off for different environments (dev, staging, prod) without code changes.
   • Audit Trail: See exactly what the builder set up behind the scenes for transparency/compliance.
   • AI-Generated Docs: Instantly generate documentation of your current auth/payment flows for your team or compliance.

   ⸻

   Example Workflow
   1. You say:
   “Add a login page with Google and email, but let me preview the app without login until I’m ready for real users.”
   2. Studio responds:
   • Presents toggle options for Google, email, phone.
   • Shows instant visual preview.
   • Offers “Skip auth in dev mode?” toggle.
   3. You confirm.
   • Studio auto-wires Firebase Auth, sets up providers, adjusts rules, and deploys.
   • When you turn off “Skip auth,” the real login is enforced.
   • Same pattern for payments, notifications, etc.

   Second-Order Impact & Benefits
   • Radically faster MVP cycles: No more lost hours on setup.
   • Reduced errors/security holes: Automated best-practice configs.
   • Much lower barrier for non-experts: Solo founders and small teams can ship pro-level features.
   • Scalable and robust: Easily evolve from prototype to prod with zero migration pain.
   • Adaptive: As Firebase/Gemini adds new providers or flows, they’re instantly available.

   Who else wants this? What other features would make your life easier in app prototyping and deployment?

   Core Problem

   Right now, even with tools like Firebase Studio or Gemini Studio’s new AI-driven app generation, you still have to:
   • Manually configure core features like authentication (email, Google, phone, etc.), payments, and billing.
   • Navigate separate dashboards, enable/disable providers, copy keys, deploy, and wire up security.
   • There’s no “preview mode” where you can test/skip auth/payment flows during development, nor an easy toggle to include/exclude these features on the fly.

   Proposed Solution

   Auto-Configurable Feature Builder:
   A single unified interface in Firebase Studio/Gemini Studio that lets you:
   1. Describe the feature in plain language (e.g., “Add signup with Google… more

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

5. Bd

   Xvkxc

   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

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

6. View Firestore Total Space Used

   Currently, billing/usage only shows usage for reads/writes/deletes. We are also being billed for total storage space. Can you please add observability into how much space is currently being used across each Firestore Database?

   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

   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

7. Gemini in Firebase Studio doesnt examine screenshots as well for troubleshooting

   Gemini when used in gemini.google.com or cursor readily examines screenshots for errors or context toward troubleshooting. Gemini in firebase studio seems to ignore the screenshots.

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

8. Consistent and documented behavior for on*WithAuthContext

   When Functions use e.g. onDocumentCreatedWithAuthContext to handle Firestore event triggers, the meaning of event.authType and event.authId are not documented and are inconsistent between the production and emulator environments.

   The documentation [https://firebase.google.com/docs/functions/firestore-events?gen=2nd#auth-context](here) says "For information about the data available in the authentication context, see..." and links to a page that is not specific to Firebase. That page lists some possible values, but it's not clear what values would be used. The most sensible guess is that authType would be "appuser" or "user" if the document was created from the client-side web SDK, and "serviceaccount" if created from a Cloud Function. But those are not the values used.

   In production, if the document is created from the client-side web SDK, authType is "api_key" and authId is the ID of the logged in user. If it's created from a Cloud Function, authType is "unknown" and authId is the ID of the default service account. Thus it is possible to tell the difference, although since the behavior is undocumented, we can't assume that the behavior won't change.

   In the emulator environment, authType is always "unknown" and authId is always "fake-auth-id@gmail.com". This is inconsistent with the production environment and makes it impossible to tell how the document was created.

   The behavior should be consistent and sensible and well documented.

   When Functions use e.g. onDocumentCreatedWithAuthContext to handle Firestore event triggers, the meaning of event.authType and event.authId are not documented and are inconsistent between the production and emulator environments.

   The documentation [https://firebase.google.com/docs/functions/firestore-events?gen=2nd#auth-context](here) says "For information about the data available in the authentication context, see..." and links to a page that is not specific to Firebase. That page lists some possible values, but it's not clear what values would be used. The most sensible guess is that authType would be "appuser" or "user" if the document was created from the client-side web SDK, and "serviceaccount" if created from a… more

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

9. Improve Billing Verification and Support for New Firebase Users

   Many new Firebase users face serious issues when trying to activate the Blaze plan due to strict and non-transparent billing verification processes.

   In my case:
   • I attempted to verify my billing using a Revolut card (registered under my name);
   • All payment confirmations were approved through the Revolut mobile app (4–5 times), yet the verification still failed;
   • No clear error explanation was provided, and I had no way to resolve the issue;
   • I tried adding a backup Korean card, but the verification message never arrived in the Korean mobile banking app (SMS also didn’t arrive because my Korean phone number is inactive);
   • After these attempts, my billing account was suspended and my project was blocked.

   Suggested improvements:
   1. Allow users to upload supporting documents to verify card ownership;
   2. Provide clear error messages when billing verification fails;
   3. Prevent automatic suspension after just a few failed attempts — especially when the card is verified by the bank;
   4. Offer a direct way to contact Firebase Billing Support for real-time help;
   5. Add an option to manually request a billing review instead of locking out users.

   This problem affects many developers who are just starting to use Firebase. Without proper verification and support tools, it’s nearly impossible to access key features like Cloud Functions and Hosting. Please consider improving this part of the onboarding process.

   If others have experienced similar issues — please vote for this idea. Let’s make Firebase more accessible for everyone.

   Many new Firebase users face serious issues when trying to activate the Blaze plan due to strict and non-transparent billing verification processes.

   In my case:
   • I attempted to verify my billing using a Revolut card (registered under my name);
   • All payment confirmations were approved through the Revolut mobile app (4–5 times), yet the verification still failed;
   • No clear error explanation was provided, and I had no way to resolve the issue;
   • I tried adding a backup Korean card, but the verification message never arrived in the Korean mobile banking app (SMS also didn’t arrive because my… more

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

10. Boom Boom Dating App
    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  ·  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

11. Add Support for Aggregation Functions and Regex Filtering in Firebase Realtime Database

    Firebase Realtime Database currently lacks support for aggregation functions (like sum, count, average) and regex-based data filtering. These features would simplify querying, reduce client-side processing, and improve performance, especially with large datasets. While Firestore offers some of these capabilities, Realtime Database remains the preferred choice for real-time syncing. Native support for these functionalities would greatly enhance its potential and usability.

    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

    0 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

12. I need to withdraw
    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  ·  Other  ·  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

13. We want the code editor to be free for everyone.

    If it was free for everyone, we would be able to create beautiful and different projects, and the subscription should only be on Fire, or data storage, or Google's digital cloud. The code editor should not have a monthly subscription. It should be free for everyone, and this is the meaning of technology, that the basis should be free, but the dependencies should be paid. If it is necessary, for example, a free artificial intelligence model should be placed for the code editor, and also make it paid. But the code editor should be free for everyone, and this is an idea that will help everyone, and other than that, it will build a very huge community.

    If it was free for everyone, we would be able to create beautiful and different projects, and the subscription should only be on Fire, or data storage, or Google's digital cloud. The code editor should not have a monthly subscription. It should be free for everyone, and this is the meaning of technology, that the basis should be free, but the dependencies should be paid. If it is necessary, for example, a free artificial intelligence model should be placed for the code editor, and also make it paid. But the code editor should be free for everyone, and this is… more

    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  ·  Analytics  ·  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. AI MODEL HYBRID VERSION SEARCH ENGINES MIX IN ALL AI MODEL HYBRID VERSION INFINITE UNLIMITE TIME INFINITE UNLIMITE UNIVERSAL WORLD SPACE

    AI MODEL HYBRID VERSION SEARCH ENGINES MIX IN AII AI MODEL HYBRID VERSION INFINITE UNLIMITE TIME INFINITE UNLIMITE UNIVERSAL WORLD SPACE BASE

    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

    1 comment  ·  Other  ·  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. make partner
    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

16. Prototyper Setup

    Before we get into prototyper, we can set what we want prototyper to Do, like Next.js, Python, and even customize what we want proto to do!

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

17. Local (or GitHubActions) build and deploy

    Currently, the only option is the Cloud Run build, why not to add the possibility of doing a local build and deploy the dist files...Very useful for GitHub Actions also.

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

18. From Firebase Studio to the app stores:

    It would be great if Firebase already had the functionality to export the app in the required formats for publishing to the Google and Apple app stores. Since Firebase is part of the Google pipeline, sending it directly from Firebase to the Google Play Store would already be a great help.

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

19. Order field by Descending Nulls Last

    Provide order by option that moves nulls to the end of results per postgresql docs NULLS LAST (https://www.postgresql.org/docs/current/queries-order.html#QUERIES-ORDER)

    Nulls are last for ASC sorts by default, so it's only needed for DESC, so I'd propose adding a new DESC_NULLS_LAST prop to the OrderDirection enum (https://firebase.google.com/docs/reference/data-connect/gql/enum#OrderDirection)

    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  ·  SQL Connect (Data Connect)  ·  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. https://studio.firebase.google.com/studio-8297471099

    https://studio.firebase.google.com/studio-8297471099

    use this or help me please...

    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

    1 comment  ·  Other  ·  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