2041 results found

1. Google play store

   update all application

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

2. Subject: UI-Based Context Management to Prevent Token Limit Errors - Suggestion for App Prototyper Enhancement

   Subject: UI-Based Context Management to Prevent Token Limit Errors - Suggestion for App Prototyper Enhancement

   I am writing to you as a community of active App Prototyper users who greatly appreciate its capabilities. Recently, I've encountered a challenge that we believe will become increasingly common for users: the "input token count exceeds" error ([GoogleGenerativeAI Error]: ... The input token count (...) exceeds the maximum number of tokens allowed (...)). This issue arises from the accumulation of conversation history within the capra-context-state.json file.

   A community member (as discussed in this forum post: https://community.firebasestudio.dev/t/temporary-workaround-for-error-due-to-exceeding-input-token-count-unofficial/12457) conducted a detailed investigation and proposed a manual workaround involving direct editing of the capra-context-state.json file to reduce the conversation history sent as context to the Gemini model. While effective, this manual solution carries risks and requires a level of technical expertise that may not be accessible to all users.

   The Identified Problem:

   After analysis, based on the current functionality and the content of capra-context-state.json (an example of its structure is provided below), confirms that the complete history of interactions, particularly within agentHistories["app-prototyping-agent: edit-app-agent"], is re-sent with each new prompt. With continued use, this history grows, inevitably leading to the model's token limit being exceeded.

   Example of the relevant capra-context-state.json structure (simplified):
   ```json
   {
   // ... other sections like currentProposalObject ...
   "agentHistories": {
   "app-prototyping-agent: edit-app-agent": [
   {
   "role": "user",
   "content": [{"text": "User message 1..."}]
   },
   {
   "role": "model",
   "content": [{"text": "Model response 1..."}]
   },
   {
   "role": "user",
   "content": [{"text": "User message 2 (reporting error)..."}]
   },
   {
   "role": "model",
   "content": [{"text": "Model response 2 (suggesting fix)..."}]
   }
   // ... more interactions ...
   ]
   },
   "currentState": "edit-app"
   }

   The Proposal: UI-Integrated Context Management

   To make context history management safer, more intuitive, and accessible to all users, we propose implementing features directly within the App Prototyper interface. I believe this would significantly enhance the user experience and the long-term usability of the tool.

   Suggest including buttons that could appear next to each message or interaction block (user prompt + model response) in the chat window, possibly on hover to keep the interface clean:

   'Delete' (or 'Remove from Context') Button:

   Functionality: Would allow the user to select a specific message or an interaction pair (user prompt + model response) and remove it from the corresponding array in agentHistories within capra-context-state.json.

   Impact: Directly reduces the token count.

   Considerations:

   A confirmation dialog would be essential.

   Ideally, the removal would also be reflected in capra-thread.json (history view), or at least the message would be visually marked as "not included in context."

   Removing a pair (user/model) seems to be the most natural approach, as observed by the community.

   'Edit' Button:

   Functionality: Would allow the user to modify the text of a previous user message within the context. This would be useful for shortening long prompts or correcting information without removing the entire interaction.

   Impact: Allows for finer control over token content.

   'Refresh Context' (or similar) Button:

   Functionality: After performing deletions or edits, this button would ensure that the App Prototyper uses the updated capra-context-state.json for the next submitted prompt, avoiding the behavior of the "Retry" button which, as understood, uses the pre-modification context. It could also clear the new prompt input field.

   Benefits of Implementation:

   Accessibility: Empowers all users, regardless of technical expertise, to manage context and avoid token errors.

   Safety: Reduces the risk of JSON file corruption from manual editing.

   Improved User Experience (UX): Offers an integrated and seamless solution to a recurring problem.

   Maintained Productivity: Allows users to continue using the Prototyper for longer periods without interruption.

   Next Steps and Collaboration:

   I understand that the project is open source. As users with technical capabilities, I am willing to explore the possibility of contributing to the implementation of these features if it aligns with the team's interests. I already have a good understanding of the data structures involved and a VM with code access for prototyping.

   I would appreciate hearing your thoughts on this proposal and whether there are any internal plans or considerations regarding this issue. I am available to discuss this further, provide more details about the analysis, or collaborate in a way that is most productive.

   Thank you for your time and for the excellent tool that the App Prototyper is.

   Sincerely,

   Subject: UI-Based Context Management to Prevent Token Limit Errors - Suggestion for App Prototyper Enhancement

   I am writing to you as a community of active App Prototyper users who greatly appreciate its capabilities. Recently, I've encountered a challenge that we believe will become increasingly common for users: the "input token count exceeds" error ([GoogleGenerativeAI Error]: ... The input token count (...) exceeds the maximum number of tokens allowed (...)). This issue arises from the accumulation of conversation history within the capra-context-state.json file.

   A community member (as discussed in this forum post: https://community.firebasestudio.dev/t/temporary-workaround-for-error-due-to-exceeding-input-token-count-unofficial/12457) conducted a detailed investigation and proposed a… more

   4 votes

   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

3. easy hosting

   Hi, I completely understand that Firebase Studio is fantastic for "vibe-coding" – even for experienced developers! However, after quickly building a front-end, I've found myself stuck on the next steps.

   I've been trying for weeks to deploy a fully functional app but struggle with the backend aspects. I've explored Firebase Hosting, Firestore, Realtime Database, and Authentication, but for a non-coder who was excited by the "vibe-coding" concept, these backend tasks are incredibly challenging. It would be amazing if there were easier ways to handle this, perhaps as simple as filling out a form or using natural language requests. While I know this might not be easy to implement, making the backend truly accessible is where "vibe-coding" could become a real game-changer.

   Hi, I completely understand that Firebase Studio is fantastic for "vibe-coding" – even for experienced developers! However, after quickly building a front-end, I've found myself stuck on the next steps.

   I've been trying for weeks to deploy a fully functional app but struggle with the backend aspects. I've explored Firebase Hosting, Firestore, Realtime Database, and Authentication, but for a non-coder who was excited by the "vibe-coding" concept, these backend tasks are incredibly challenging. It would be amazing if there were easier ways to handle this, perhaps as simple as filling out a form or using natural language requests. While I… more

   4 votes

   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

4. Allow users to select important milestones for restoration.

   I recently found that the looooooooong chat was removed and it improved the response time of coding. That was great. But there was a downside to it. I lost many important milestones, that i might have wanted to restore back to. It will be great if you allow the users to mark important milestones to retain when the cleaning of chat happens. That way they will be able to restore back to preferred versions in case required.

   Or they will be stuck with the experimental request that led to more damage than good.

   3 votes

   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

5. messagerie
   2 votes

   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

6. GSM BUSINESS
   2 votes

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

   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

8. add support for flutter publish to app store connect

   add support for flutter publish to app store connect

   2 votes

   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

9. Firebase Studio precisaria de um botão para voltar o projeto antes da alteração

   Eu acho que o Firebase Studio precisaria de um botão para voltar o projeto antes da alteração, muitos vezes ele faz algo errado e edita vários componentes que não necessitavam de alteração, se demos restore em um prompt anterior que não alterou esses arquivos, ele apenas restaura aquele componente especifico, um botão de voltar a versão antes com certeza seria um dos recursos mais valiosos de momento, tal como o Horizon da Hostinger, um simples icone para voltar a versao anterior antes do ultimo prompt era ideal.
   Tenho certeza que muitas pessoas tem o projeto em um bom caminho e do nada o firebase studio altera algo que nao deveria e o quao chato e conseguir voltar o projeto todo atras se nao tiver um backup, mesmo com backup tem que voltar a editar componente por componente, pois o chat nao intende o que e refatorar, ele faz tudo menos refatorar.

   Eu acho que o Firebase Studio precisaria de um botão para voltar o projeto antes da alteração, muitos vezes ele faz algo errado e edita vários componentes que não necessitavam de alteração, se demos restore em um prompt anterior que não alterou esses arquivos, ele apenas restaura aquele componente especifico, um botão de voltar a versão antes com certeza seria um dos recursos mais valiosos de momento, tal como o Horizon da Hostinger, um simples icone para voltar a versao anterior antes do ultimo prompt era ideal.
   Tenho certeza que muitas pessoas tem o projeto em um bom caminho e… more

   2 votes

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

    Xvkxc

    1 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

11. Actualización

    Actualizado de aplicaciones

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

12. I just want to be verified in LinkedIn

    YoungEnterprises@gmail.com

    2 votes

    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

13. Gemini in code mode

    It would be helpful to see Gemini's output when in code mode instead of only prototype mode. Currently copying and pasting into Word to reference what Gemini has said.

    3 votes

    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

14. Bad instance server UTC Timestamp

    When I asked to add as a start of Gemini answers (in a conversation) the current timestamp.
    I was surprised that the answer was "I take as reference the timestamp of the server where I am running and for me UTC is 202310-27 (while we are in France for Paris today 202401-07)

    8 votes

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

    Galeri

    2 votes

    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

16. Provide Gemini AI suggestion and fixes to LightHouse result

    It is nice to generate Lighthouse report in Firebase Studio but it doesn't offer AI assistant after the report.

    I believe this is a product gap that could be easily resolved by plugging Gemini to provide fixes to the problems highlighted in the report.

    2 votes

    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

17. Infinite loop/recursion detection

    It's possible to make a mistake that causes a function to trigger itself (for example, an onDocumentWritten Firestore trigger that writes to the same document). If Cloud Functions for Firebase could detect this and shut down the infinite loop, it could prevent runaway bills.

    It could also be a feature in the emulator suite so that we could check for them before deploying to production.

    2 votes

    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

18. Hello, I’m a high school student and I’ve noticed that the Firebase Cloud Android Studio VM shuts down after some time. Is there a way to ke

    Hello, I’m a high school student and I’ve noticed that the Firebase Cloud Android Studio VM shuts down after some time. Is there a way to keep it running 24/7? If possible, could I get 24/7 active access for my workspace named 'my-studio-49173518'? I would be very thankful

    3 votes

    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

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

    2 votes

    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

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

    3 votes

    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