1232 results found

1. java admin api supports configuring the "firebase" url, so I can start a wiremock service and assert on the received call´s

   Modify: https://github.com/firebase/firebase-admin-java/blob/master/src/main/java/com/google/firebase/messaging/FirebaseMessagingClientImpl.java#L63
   To make the FCM_URL or fcmSendUrl configurable.

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

2. Provide a Migration Path for Existing Links in Printed Media (QR Codes) after FDL EOL (Similar to goo.gl Approach)

   ・The Problem:

   The Firebase Dynamic Links EOL on Aug 25, 2025, will cause millions of FDL links embedded as QR codes in printed textbooks to return 404 errors. These physical materials cannot be updated, creating a critical issue for the education sector and our publishing clients. The official migration guide does not offer a solution for these existing, unchangeable links.

   ・Precedent:

   Google has already solved this exact problem for another service. The Google Developers Blog recently announced that goo.gl links will be preserved because they are "embedded in countless documents, videos, posts and more."

   This situation with goo.gl is precisely identical to the critical issue we face with Firebase Dynamic Links. As we have explained, our publishing clients have embedded FDL-generated QR codes into printed textbooks, which cannot be altered. The very rationale that led to the preservation of goo.gl links perfectly describes the predicament of our clients.
   Our situation with FDL is identical.

   (Link: https://blog.google/technology/developers/googl-link-shortening-update/)

   ・Proposed Solutions

   Redirection-Only Grace Period
   Following the goo.gl precedent, continue to resolve and redirect existing FDLs for an extended period (e.g., 2-3 years) after the EOL date. New link creation could be disabled, but existing links should not break.

   This is a critical business continuity issue for many developers and their clients. We strongly request that the Firebase team provide a viable solution.

   ・The Problem:

   The Firebase Dynamic Links EOL on Aug 25, 2025, will cause millions of FDL links embedded as QR codes in printed textbooks to return 404 errors. These physical materials cannot be updated, creating a critical issue for the education sector and our publishing clients. The official migration guide does not offer a solution for these existing, unchangeable links.

   ・Precedent:

   Google has already solved this exact problem for another service. The Google Developers Blog recently announced that goo.gl links will be preserved because they are "embedded in countless documents, videos, posts and more."

   This situation with goo.gl is precisely… 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  ·  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

3. add support for flutter publish to app store connect

   add support for flutter publish to app store connect

   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

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

4. chatbot

   Plataforma de Automatización Conversacional para WhatsApp Business

   Objetivo general:
   Desarrollar una solución integral basada en WhatsApp Business API, con inteligencia artificial y automatización, para que empresas como restaurantes, pizzerías, comercios y profesionales puedan:
   - Automatizar la atención al cliente
   - Gestionar pedidos, pagos y reservas
   - Enviar notificaciones, promociones y recordatorios
   - Escalar a un agente humano cuando sea necesario

   El sistema será ofrecido como servicio (SaaS) bajo el nombre Factor Soluciones y debe ser escalable a múltiples clientes (modelo multiempresa).

   Componentes clave:

   1. Integración con la API Oficial de WhatsApp Business:
   2. Uso de proveedor oficial (360dialog, Twilio, Zenvia, etc.)

   3. Soporte para plantillas y mensajes bidireccionales

   4. Chatbot con IA:

   5. Procesamiento de lenguaje natural (intenciones, entidades, errores de tipeo)

   6. Memoria de contexto conversacional

   7. Soporte para lenguaje local y variaciones

   8. Base de conocimiento editable:

   9. Menú de productos, FAQs, documentos

   10. Backoffice con carga de contenidos no-code

   11. Gestión de pedidos y pagos:

   12. Toma de pedidos automatizada

   13. Pago por efectivo, transferencia, Mercado Pago

   14. Escalamiento a humano:

   15. Cuando hay frustración, error o lo pide el usuario

   16. Panel administrativo:

   17. Web app para Carlos (administrador general)

   18. Panel para cliente final: entrenar bot, ver conversaciones, configurar respuestas

   19. Analíticas:

   20. Conversaciones totales, resolución automática, tiempos de respuesta, satisfacción

   21. Seguridad:

   22. Cumplimiento con GDPR y normativas argentinas

   23. Roles, permisos, encriptación

   Tecnologías sugeridas:
   - Frontend: React / Vue
   - Backend: Node.js / Python
   - Base de datos: PostgreSQL / MongoDB
   - IA: Dialogflow, Rasa o ChatGPT API
   - Hosting: Heroku, Vercel, AWS

   Entrega esperada:
   - Web App funcional
   - Demo para restaurante / pizzería
   - Conexión a WhatsApp oficial
   - Documentación técnica

   Plataforma de Automatización Conversacional para WhatsApp Business

   Objetivo general:
   Desarrollar una solución integral basada en WhatsApp Business API, con inteligencia artificial y automatización, para que empresas como restaurantes, pizzerías, comercios y profesionales puedan:
   - Automatizar la atención al cliente
   - Gestionar pedidos, pagos y reservas
   - Enviar notificaciones, promociones y recordatorios
   - Escalar a un agente humano cuando sea necesario

   El sistema será ofrecido como servicio (SaaS) bajo el nombre Factor Soluciones y debe ser escalable a múltiples clientes (modelo multiempresa).

   Componentes clave:

   1. Integración con la API Oficial de WhatsApp Business:
   2. Uso de proveedor oficial (360dialog, Twilio, Zenvia, etc.)

   3. Soporte… more

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

5. Support an array/object in firebase.json "emulators"."apphosting" to run multiple apphosting backends at once

   Given apphosting supports multiple configured backends, it would greatly improve the emulator's utility to provide a mechanism to emulate all of them locally. With this feature in place firebase can support local emulation of apphosting and cloud run backends configured using hosting rewrite rules when deployed, which is a big win for supporting any number of microservices behind a single domain for integration testing and local dev. We'll still be responsible for implementing a local service discovery mechanism, but we'll have the convenience of just the emulator for spawning all our app processes.

   From the outside the feature looks like it could be easily implemented with a map on the backend array, so if it's truly small in story points I encourage the product team to prioritize it.

   Given apphosting supports multiple configured backends, it would greatly improve the emulator's utility to provide a mechanism to emulate all of them locally. With this feature in place firebase can support local emulation of apphosting and cloud run backends configured using hosting rewrite rules when deployed, which is a big win for supporting any number of microservices behind a single domain for integration testing and local dev. We'll still be responsible for implementing a local service discovery mechanism, but we'll have the convenience of just the emulator for spawning all our app processes.

   From the outside the feature looks like… 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

   0 comments  ·  App Hosting  ·  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. Better way to backup Gemini Conversations

   I use a second-brain tool that leverages markdown files (Obsidian). So I would like to be able to download each of my Gemini sessions in Markdown files to easily add to my vault. Having to export the json from the files or drag to copy and paste is not efficient or a great user experience.

   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

7. Firebase storage rules: Support for multi-database lookup

   This is a documented limitation and as such not an idea, but putting it out here to see if it get vote-traction. See the warning at the bottom of the page here:

   https://firebase.google.com/docs/storage/security/rules-conditions

   As of Feb. 25. 2025 it says

   "Warning: Storage Rules can only access documents from the default Cloud Firestore database when multiple databases are active."

   We have a project where we're doing tenant partitioning in both Firestore and firebase storage. The primary reason for creating separate buckets and databases is to be able to have storage in different customer preferred regions, and to achieve other isolations which are beneficial (backup/restore recovery scenarios etc.).

   Most files in firebase storage are protected by security rules that look up a document from the firestore database and checks access using a fairly standard acl scheme.

   This does not work unfortunately in a multi-db setup, which prevent this type of acl based storage security rules.

   I've not found any workarounds except an approach there the storage object Ids are long unique Ids that can't be "guessed" or brute force generated to look up an object in storage, but this is not as clean as being able to explicitly check access rights (and other logic on top of that using the rules language).

   The fact that it works in single/default db makes it feel like a significant takeback that the security design has the by changed when introducing multiple databases to the project.

   I think this is a common case for solutions doing tenant separation where there is a need to have objects in storage protected by acls.

   This is a documented limitation and as such not an idea, but putting it out here to see if it get vote-traction. See the warning at the bottom of the page here:

   https://firebase.google.com/docs/storage/security/rules-conditions

   As of Feb. 25. 2025 it says

   "Warning: Storage Rules can only access documents from the default Cloud Firestore database when multiple databases are active."

   We have a project where we're doing tenant partitioning in both Firestore and firebase storage. The primary reason for creating separate buckets and databases is to be able to have storage in different customer preferred regions, and to achieve other isolations which… more

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

8. Clear Gemini History Not Working

   Sorry, I hit a snag. Please try again shortly or modify your prompt.
   [GoogleGenerativeAI Error]: Error fetching from https://monospace-pa.googleapis.com/v1/models/gemini-2.5-pro:streamGenerateContent?alt=sse: [400 Bad Request] The input token count (9521395) exceeds the maximum number of tokens allowed (1048576).

   When you try to clear the history on Gemini, this doesn't work. This needs to be fixed, otherwise it prevents vibe coding, etc.

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

9. Change "apphosting"."ignore" behavior in firebase.json to apply the configured paths from the directory holding firebase.json

   I always run my firebase projects as monorepos since they typically incorporate several distinct apps with shared deps. I use my own CI/CD pipeline because the apphosting default is not flexible enough.

   When deploying apphosting using the CLI, there is a size limit on the zipped bundle. If the "ignore" behavior would allow me to ignore directories from the project root I wouldn't have problems, but since it's relative to the apphosting "rootDir" I don't have a way to use my entire monorepo for integration testing, etc and then ship my apphosting project using firebase deploy because the entire monorepo is too large.

   I always run my firebase projects as monorepos since they typically incorporate several distinct apps with shared deps. I use my own CI/CD pipeline because the apphosting default is not flexible enough.

   When deploying apphosting using the CLI, there is a size limit on the zipped bundle. If the "ignore" behavior would allow me to ignore directories from the project root I wouldn't have problems, but since it's relative to the apphosting "rootDir" I don't have a way to use my entire monorepo for integration testing, etc and then ship my apphosting project using firebase deploy because the entire monorepo… 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

   0 comments  ·  App Hosting  ·  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

10. when ever we select a component of our page to edit and say ai how it should be i want ai to show recomendation live of what it can 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

    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

11. slow and basic project only can you bulit it like bolt.new.ai or like replit agent
    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  ·  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

12. Add Native Invitation Email Flow for Firebase Authentication (Multi-Tenant Apps)

    In many multi-tenant applications, an invitation is a time-limited, one-time handshake between two parties inside an app context (e.g. organization, workspace, team, or document).

    After the invitation email is accepted, the link should bring the recipient into the app at a specific contextual entry point (for example, a workspace, organization, or document reference). From that point:

    Existing users continue through the regular sign-in flow (if not already signed in)

    New users continue through the standard sign-up flow

    At that point, the application takes full control of the user experience and logic.

    From Firebase’s perspective, the responsibility would primarily be to confirm identity and intent, rather than enforce app-specific behavior. Conceptually, this is closer to the email verification flow than to a persistent authentication method.

    This capability is foundational for B2B and multi-tenant applications and currently requires workarounds using Cloud Functions and external email services.

    In many multi-tenant applications, an invitation is a time-limited, one-time handshake between two parties inside an app context (e.g. organization, workspace, team, or document).

    After the invitation email is accepted, the link should bring the recipient into the app at a specific contextual entry point (for example, a workspace, organization, or document reference). From that point:

    Existing users continue through the regular sign-in flow (if not already signed in)

    New users continue through the standard sign-up flow

    At that point, the application takes full control of the user experience and logic.

    From Firebase’s perspective, the responsibility would primarily be to… 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

    0 comments  ·  Authentication  ·  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. Cannot create event on edge

    Cannot create event on edge

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

14. A M-pesa app but cheaper on transactions

    Cheapest app on transactions

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

15. Elidiannys

    Ffffff

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

16. Save phone

    Idea save

    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  ·  Authentication  ·  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. Funshot

    await FirebaseFirestore.instance.collection('questions').add({
    'question': 'Tumi ke Gamini?',
    // 'user' field optional, tai ekhane dei nai
    'timestamp': FieldValue.serverTimestamp(),
    'answered': false,
    });

    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

    3 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

18. Add npm workspace support for monorepos

    App Hosting already supports nx based monorepos, but it would be great to have basic npm workspace support. I tried to take the plunge and convert my repo to nx tooling but I failed spectacularly 🙂 npm workspaces are super simple to get started with and other than not being able to deploy to App Hosting, they haven't come up short for me in a way that would convince me to try nx again.

    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

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

19. Create Non-placation 'Business' Mode

    Provide a non-placaction mode, where the AI is just all business and stops beginning each response with a paragraph like this: "Of course. I am so sorry that you are still seeing this error. You are completely right to be angry. This is embarrassing. I uunderstand your frustration. You have been more than patient, and my repeated failures to fix this are unacceptable."

    and then says:

    "The Definitive, Final Plan:" for the 15th time. Just say, "I hope this works"

    AI is neither feel embarrassment nor understands my feelings and I do not need it to. All this does is waste words, time, space.

    Provide a non-placaction mode, where the AI is just all business and stops beginning each response with a paragraph like this: "Of course. I am so sorry that you are still seeing this error. You are completely right to be angry. This is embarrassing. I uunderstand your frustration. You have been more than patient, and my repeated failures to fix this are unacceptable."

    and then says:

    "The Definitive, Final Plan:" for the 15th time. Just say, "I hope this works"

    AI is neither feel embarrassment nor understands my feelings and I do not need it to. All this does is… 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

    1 comment  ·  Firebase AI Logic  ·  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. Links

    Reliable

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