2320 results found

1. One click Auth setup

   like lovable+supabase

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

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

   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

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

   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

4. Nizarnoal87@gmail.com

   Nice

   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

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

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

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

6. The annimations can be better

   Please Use Codepen.io

   Thanks!

   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

7. you must add php Support and Mysql

   you must add php Support and Mysql and project improt from Github

   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

8. unity support

   because making unity app is so resource comsuming for a normal computer( open project about 1 min ) compile it first time for 15 min and every time i use it my computer have fans running sounds . so i think it would be better so have unity support just like android support

   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

9. Firebase Studio source code files need revertible edit histories
   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

10. .NET based desktop/mobile app

    • .NET MAUI

    • Uno Platform.

    • Avalonia UI

    Any of those 3 support desktop and mobile. The language is C#/XAML.

    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

    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

11. Add the ability for Gemini to read the problems pane and other aspects of the editor

    Gemini should be able to read more information directly from the editor and especially the problems pane as that would make troubleshooting much more convenient. Eventually integration directly with previews would be cool so that it can read straight from those as well

    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

    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

12. Elimde bulunan hali hazır da uygulama projemi buraya yükleyip devam etmek

    Yapay zeka ile oluşturduğumuz Mobil uygulama veya her hangi bir hali hazırda başlanmış olan proje dosyasını buraya yükleyip kaldığımız yerden buradan devam etmek istiyorum var mı yok mu bilmiyorum

    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

    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

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

    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. PERSIST FIRESTORE COLLECTION SORTING CONDITIONS
    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

    2 comments  ·  Firestore  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. add support for biometrics authorization test from the browser IDE
    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

16. ram

    Could you please add an option to get more RAM for our workspaces? The current amount (seems around 8GB) often isn't enough when running bigger Android projects, especially with the emulator and build tools going at the same time. Things can get pretty slow.

    It would be really helpful if we could choose a higher RAM configuration, maybe 16GB or 32GB, even if it's an upgrade option. This would make developing larger apps in Project IDX much smoother.

    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

17. Recomendaciones para Mejorar Firebase Studio

    Recomendaciones para Mejorar Firebase Studio:

    Mejora en la Interpretación de Solicitudes Complejas:

    Firebase Studio debe mejorar su capacidad para interpretar solicitudes complejas y multifacéticas.
    Se debe prestar especial atención a la identificación y el cumplimiento de las especificaciones tecnológicas (por ejemplo, lenguajes de programación, frameworks, bases de datos) proporcionadas por el usuario.
    Implementar un sistema de "confirmación" donde la herramienta, antes de generar el codigo, muestre las tecnologias que usara, y el usuario pueda aceptar, o rechazar.
    Generación de Código Más Precisa y Completa:

    La herramienta debe generar código que sea más preciso y completo, abarcando todas las funcionalidades solicitadas por el usuario.
    Se debe prestar especial atención a la generación de código para funcionalidades clave como la autenticación de usuarios, la gestión de bases de datos, la implementación de APIs y la integración de servicios externos.
    Se debe mejorar la capacidad de la IA para generar codigo, que siga la estructura de carpetas que se le indica.
    Incorporación de Comentarios y Explicaciones Detalladas:

    El código generado debe incluir comentarios claros y concisos que expliquen la lógica y el propósito de cada sección.
    Se deben proporcionar explicaciones detalladas de las decisiones de diseño y las implementaciones técnicas.
    Se debe implementar la internacionalización de los textos que se le muestran al usuario.
    Se debe generar la documentación del codigo generado.
    Mejora en la Documentación Generada:

    La documentación generada debe ser completa, clara y concisa, y debe incluir:
    Una descripción general de la aplicación.
    Detalles técnicos sobre la arquitectura, las tecnologías utilizadas y la implementación de las funcionalidades.
    Instrucciones para la instalación, configuración y uso de la aplicación.
    Traducción de la documentación a los idiomas del usuario.
    La documentación debe estar actualizada y ser accesible para todos los desarrolladores involucrados en el proyecto.
    Mayor Flexibilidad y Control para el Usuario:

    Firebase Studio debe proporcionar a los usuarios una mayor flexibilidad y control sobre el código generado.
    Se deben ofrecer opciones para personalizar la arquitectura, las tecnologías y las funcionalidades de la aplicación.
    Se debe implementar, la opcion para que el usuario pueda seleccionar las versiones de las librerias que desea usar.
    Retroalimentación Continua y Mejora Iterativa:

    Google debe establecer un proceso de retroalimentación continua para recopilar opiniones y sugerencias de los usuarios.
    Firebase Studio debe mejorar de forma iterativa, incorporando la retroalimentación de los usuarios y adaptándose a las nuevas necesidades del mercado.

    Recomendaciones para Mejorar Firebase Studio:

    Mejora en la Interpretación de Solicitudes Complejas:

    Firebase Studio debe mejorar su capacidad para interpretar solicitudes complejas y multifacéticas.
    Se debe prestar especial atención a la identificación y el cumplimiento de las especificaciones tecnológicas (por ejemplo, lenguajes de programación, frameworks, bases de datos) proporcionadas por el usuario.
    Implementar un sistema de "confirmación" donde la herramienta, antes de generar el codigo, muestre las tecnologias que usara, y el usuario pueda aceptar, o rechazar.
    Generación de Código Más Precisa y Completa:

    La herramienta debe generar código que sea más preciso y completo, abarcando todas las funcionalidades solicitadas… 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

    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

18. "I need to talk with them using audio or video.", live streem audio and video sharing

    "I need to talk with them using audio or video.", live streem audio and video sharing

    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

    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

19. Private Repo import similar to IDX

    I noticed that currently only public repositories are supported. Are there any plans to support private repositories as well?

    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

20. needs a restore button

    Above each prompt, add a restore button to restore code back to point before prompt. Then you can restore, re-write prompt, and see what happens with the next prompt.

    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