2385 results found

1. change the firebase project the the prototype workspace is working on

   i think that it would be nice to change the project that i'm using in the prototype to an existing project that i already created in the firebase console so when i want to publish my prototype i can publish it in a project that already have all of my data and configuration in one place with my hosting to

   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

   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

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

3. godot game engine support

   free and open source

   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

   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

4. I suggested

   I want my app to be validated

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

5. 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  ·  Dynamic Links  ·  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. Playwright

   Please support playwright test framework

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

7. Create an app

   Help me create a Chat 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

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

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

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

9. Conversation history with save and edit points

   I was asked to go find my gemini api key which made me lose the original tab. When i came back i only had the IDE and zero conversation history. The vibe flow was gone. I was bummed, not vibed. Anyway, conversation history should be permanent, and link that with save and edit points. This should also go towards memory.

   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

   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

10. Miniosu Elena Mariana
    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  ·  Firebase Studio  ·  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. Galeria

    Cantar

    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

    3 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

12. Firebase App Distribution Permissions Change

    Currently, the automated testing feature within Firebase App Distribution mandates that the user executing the test possess either the Project Owner or Project Editor IAM role. This requirement is overly broad and presents a significant operational barrier for organizations managing a large number of projects (e.g., 1,000+) where granting such high-level permissions is often restricted due to security policies and standard practices. Attempts confirmed that even users with high-privilege roles like Organization Admin and Firebase Admin were unable to run these tests, indicating the check is strictly limited to Owner/Editor.

    This limitation prevents teams from effectively utilizing the automated testing feature. We request the ability to run Firebase App Distribution automated tests using more granular permissions. Ideally, this would involve either identifying a specific set of minimum required permissions that can be bundled into a custom role or providing a new, less privileged predefined IAM role specifically for this purpose. Enabling finer-grained access control is crucial for the adoption and practical use of this feature in enterprise environments. Google Support acknowledged this limitation is known, on the product roadmap without a specific ETA, and filed an internal bug/request.

    Currently, the automated testing feature within Firebase App Distribution mandates that the user executing the test possess either the Project Owner or Project Editor IAM role. This requirement is overly broad and presents a significant operational barrier for organizations managing a large number of projects (e.g., 1,000+) where granting such high-level permissions is often restricted due to security policies and standard practices. Attempts confirmed that even users with high-privilege roles like Organization Admin and Firebase Admin were unable to run these tests, indicating the check is strictly limited to Owner/Editor.

    This limitation prevents teams from effectively utilizing the automated testing… more

    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  ·  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. Add support for country-based user targeting in Firebase SDK

    It would be very helpful if the Firebase SDK included built-in support for targeting users based on their country. Currently, we have to handle this manually using workarounds or backend logic. Native support in the SDK for accessing the user’s country (based on IP or locale) and using it for feature targeting, in-app messaging, or remote config conditions would streamline country-specific personalization and improve the user experience.

    This feature would allow us to:

    Show different content or messages to users based on their country.

    Better segment users for A/B testing or campaigns.

    Reduce backend dependency for basic geographic targeting.

    Please consider adding this functionality directly in the Firebase SDK

    It would be very helpful if the Firebase SDK included built-in support for targeting users based on their country. Currently, we have to handle this manually using workarounds or backend logic. Native support in the SDK for accessing the user’s country (based on IP or locale) and using it for feature targeting, in-app messaging, or remote config conditions would streamline country-specific personalization and improve the user experience.

    This feature would allow us to:

    Show different content or messages to users based on their country.

    Better segment users for A/B testing or campaigns.

    Reduce backend dependency for basic geographic targeting.

    Please… more

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

14. Instant Error Fix & Always-On Connection

    Make Error Solving Quickly and very quick response, no disconnect issue on lower device, also user mind visual for happiness

    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

    1 comment  ·  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. New products of instant support software for solving and making decisions

    Instant programs to support decision-making in various fields, whether business, entertainment, health, food, or even worship.

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

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

17. Live preview of a change before making it.

    If developing a small part of the app, like a table, or container with buttons, the prototyper could show a live preview of that feature to more quickly optimize the design before updating the whole code. This would be limited to features that don't integrate with the rest of the prototyped app, or would have dumb buttons instead of actionable buttons.

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

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

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

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