2365 results found

1. Add feature for upload local project & github import feature in (Prototype an app with AI) area.

   If possible add project upload from local storage & github import for firewase studio prompt section/feature.Currently only image upload available. You have this option in work space area but i am talking about (Prototype an app with AI) area.If will help the users much more.

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  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. Way to handle doom loop coding

   I've been running into an issue repeatedly letting Firebase Studio AI try to fix an error that it keeps re-detecting. It acknowledges that it's a persistent issue, but none of the fixes seem to work. I'm not sure how to fix it either. Maybe it would be good to have a way for the AI at some point engage human support on the Google side? Or maybe open up for a request to identify and investigate problems the AI seems to be struggling with?
   Here's the particular error in this instance:

   "Runtime Error

   Error: ./nodemodules/@opentelemetry/sdk-trace-node/nodemodules/@opentelemetry/context-async-hooks/build/src/AsyncHooksContextManager.js:20:20
   Module not found: Can't resolve 'asynchooks'
   18 | exports.AsyncHooksContextManager = void 0;
   19 | const api1 = require("@opentelemetry/api");

   20 | const asyncHooks = require("asynchooks");
   | ^^^^^^^^^^^^^^^^^^^^^^
   21 | const AbstractAsyncHooksContextManager1 = require("./AbstractAsyncHooksContextManager");
   22 | class AsyncHooksContextManager extends AbstractAsyncHooksContextManager_1.AbstractAsyncHooksContextManager {
   23 | constructor() {..."

   I've been running into an issue repeatedly letting Firebase Studio AI try to fix an error that it keeps re-detecting. It acknowledges that it's a persistent issue, but none of the fixes seem to work. I'm not sure how to fix it either. Maybe it would be good to have a way for the AI at some point engage human support on the Google side? Or maybe open up for a request to identify and investigate problems the AI seems to be struggling with?
   Here's the particular error in this instance:

   "Runtime Error

   Error: ./nodemodules/@opentelemetry/sdk-trace-node/nodemodules/@opentelemetry/context-async-hooks/build/src/AsyncHooksContextManager.js:20:20
   Module not found:… 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  ·  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. Adding GPU Capability will Boost the Productivity

   GPU and Parallel Processing power is very essential for better AI development. Moreover, GPU capability will enhance the App productivity as the new Apps require more computing as well as graphics processing power so I highly recommend to add GPU capability in Firebase Studio. It would be very helpful for the developers

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  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. Make Firebase Test Suite available for the Firebase Studio

   The problem a facing is: I'm a solo developer with limited resources who want to use Firebase as my entire Back-End solution, but I don't want to need to move to the Blaze plan just to test my integrations with externals APIs (not from Google), exclusively during the development stage.

   It would be good to have an alternative to Firebase Local Suite on Firebase Studio. It could have the same resources of the Spark plan and work only on Firebase Studio's workspaces, but with the addition of being able to connect to external APIs, such as Stripe and others.

   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  ·  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. Support mobile app prototyping on Firebase Studio

   Support mobile app prototyping for Flutter and React Native + Expo

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

6. Dashboard Background Queue

   A background processing queue with a status indicator for more complex or time-consuming AI tasks. It would certainly make the process feel more transparent and less like a potential crash if a request is taking a while.

   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  ·  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. Filtering crashes for the latest release shouldn't change time range

   When pressing "Filter crashes" on the info banner about the latest release, the time selection also silently changes from "Last 7 days" to "Last 24 hours".

   It would be easier to compare between all crashes and crashes from the latest release if the time span didn't change unasked like that.

   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  ·  Crashlytics  ·  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. Database function like Wordpress

   While selecting proceed with this prototype it should have option to create or link database similar to wordpress so that user can create fullstack app with database

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  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. One click Auth setup

   like lovable+supabase

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

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

    Core Problem

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

    Proposed Solution

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

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

    ⸻

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

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

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

    Core Problem

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

    Proposed Solution

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

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Gemini in Firebase  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

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

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Gemini in Firebase  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Nizarnoal87@gmail.com

    Nice

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

14. The annimations can be better

    Please Use Codepen.io

    Thanks!

    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  ·  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. you must add php Support and Mysql

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

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