Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

2320 results found

  1. It's difficult to work from a mobile phone it's be great if we could format it for mobile use

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. In other Ai coding studios, there is a discussion button in the chat. This means you can ask a question of the Ai without it making changes to your app. This reduces errors and enables the user to clarify with the AI particular functions or ideas before implementing them.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. I’ve faced repeated issues in Firebase where making updates or major changes can lead to fatal errors. The biggest frustration is that even the rollback request often fails, leaving no reliable way to restore the project to a stable state.

    Because of this, the only solution I’m forced to use is creating a full duplicate of the entire project every time I want to make major changes. This is inefficient, time-consuming, and increases the risk of inconsistencies.

    • * * Suggestion:

    Introduce built-in versioning for apps (e.g., 1.0.0.01, following semantic versioning best practices).

    Each update/deployment should automatically create a new version…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Firestore rules tab should allow deploying multiple tabs so that all rules are not in the same rules container in the UI. This will allow us to create separation of concerns(collections) to their own tabs. To prevent massive running list of rules.

    As an example:

    I have 2 collections

    Users
    Pets

    I should be able to write my rules for Users in a tab.
    Then in a completely separate tab, write the rules for Pets

    Then deploy them individually or all at the same time.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Has option to switch to partial no-code like Adalo, where developers can select the type of layouts, colors, move or drag the options, as it would be more easy to do for some cases than chatting/vibe coding

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Add the option to edit the UI of the current project in the preview window (Like Lovable) For example, once the code is generated for a landing page, allow me to edit the text directly in the preview window as opposed to doing this in the code directly.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Currently, any gql files placed in schema folder generate one FDC schema in FDC console, which generates associated tables in postgres PUBLIC schema. Putting tables there is not ideal.

    It would be nice if creating additional subfolders within schema source folder (or some other mechanism) could allow mapping to developer defined postgres schemas other than PUBLIC. For example, the following folder structure:

    schema/appname/*.gql

    would map to APPNAME schema in Postgres and tables would be created there.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. ضغط الملفات في بيئة التطوير للتقيل من حجم البيانات المرسلة عبر المشغل عندما يقوم بقراءة ملفات المشروع في كل مرة لتنفيذ المطالبة الأخيرة والرجوع بالنتائج في عملية المعالجة المطالبة

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Firebase Studio permet de générer une application web en quelques minutes à partir d'un simple prompt.

    Mon idée est d'élargir le champ des possibles (vous n'avez pas idée à quel point cela sera révolutionnaire) en permettant de développer des applications mobiles avec Firebase Studio.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. In some apps, it is desirable for a user to subscribe to multiple topics by default, and it also is desireable to allow users to subscribe to/unsubscribe from many topics at once. For example, "I want all/no weather notifications" may entail subscribing/unsubscribing to "thunderstorm-warnings", "thunderstorm-watches", "tornados-warnings", "tornado-watches", etc, for all the topics of that type in your app.

    Currently, you have to make one API call for each of these. This is very slow, has unnecessary network overhead, and complicates calling code.

    My proposed feature: add "subscribeToTopics" and "unsubscribeFromTopics" methods to the SDKs. The signature would be (depedning on the…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. I propose a long term feature that allows users to enable an auto-management of a "diary" that logs session activities and summarizes as you use studio.

    There is the short term and long term aspect of this feature. During the current session, since its ephemeral, when major conversation topic shifts or efforts shift, we notate that in the short term memory; every time we reload a new session, we review the past short term, summarize/compress , and add it to our long term "memory" or diary. Then we start fresh for the day, with some context of the past efforts.…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. When we work with Gemini as new user using mobile,we have to access database console,first of all the naming to front end developement and backend should be clear as firebase front end console and for data base as backend firebase to distanguish between the two,and while working on gemini sholud have access to backend to work on in Ai as a layman,

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. ・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…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Subject: Proposal for Improving Firebase Studio for Developers with Basic Knowledge

    To the Firebase Studio Team at Google,

    I would like to offer several ideas for improving the platform, with an emphasis on making it more accessible to developers who are at the beginning of their professional journey or who have a basic level of development knowledge. Firebase Studio is a powerful tool with immense potential, and it can be made even more user-friendly and intuitive for this audience.

    The main challenge for a developer with basic knowledge is that the intelligent agent and the work environment assume a high…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. mcp-playwright integration

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  MCP Server  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. (Google Ads Display & Video 360)

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. I'm trying to start the Firebase storage, but I get the following error: "An unknown error occurred. Please update the page and try again." But when I checked the browser console, I found this message: "{
    "error": {
    "code": 403,
    "message": "The caller does not have permission",
    "status": "PERMISSION_DENIED"
    }
    }"
    The strange thing is that I'm trying to do this with the owner user. Does anyone know exactly what's going on?

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Currently people cannot work on separate branches simultaneously. Only one branch is active even if multiple people are using the project in the studio. It would be a good feature to have where different people can work on different branches at a time. with each branch being locked to a specific user and other user cannot changes until that branch is released. Team collaboration will be much more effecient and people can work on different features at the same time.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?