2103 results found

1. Working together

   I think it would be so much better if we can see who is online in the project, where is their cursor, and what are their working in. Like in google docs. So we can collaborating making a project simulteneously. No need to worry about the commit and conflict.

   294 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

   14 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
   planned  ·  AdminKirupa (Product Manager, Google, LLC - Firebase) responded

   This is something we are actively looking into!

2. App Distribution should have at least basic management of email notifications

   There is no option to set email preferences for tester groups in Firebase App Distribution. It is unnecessary to pester everyone with emails when they can find the last app version in App Tester.

   51 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

   8 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

3. App Testing agent (iOS)

   Hello. I really like your testing agent for Android. Please tell me if there are any plans to develop an agent for iOS?

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

4. More space for IDX projects 100GB

   We can't complete a basic yarn install our monorepo at work. We run into the following error.

   ENOSPC: no space left on device

   While trying to complete the yarn install. I've returned several times to the IDX project and have finally given up trying to do practical work for our live production projects with IDX as we can't even install our packages at work to get our projects running. What an absolute collosal waste of time.

   Please for the love of christ increase the project capacity so we can get our commercial projects running in IDX.

   44 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

   10 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. Event Triggers

   Trigger a Cloud Function when data in a table type is created (via insert or upsert), updated (via update or upsert), or deleted.

   252 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

   18 comments  ·  Data Connect  ·  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. Disables support for TLS 1.0 and TLS 1.1 as these are vulnerable versions

   Is there a plan to disable support for TLS 1.0 and 1.0 version across the domains e.g. firebase console, fcm.googleapis.com and other services?

   32 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  ·  Other  ·  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. Allow multiple developers to manage, build, and deploy

   Enable collaborative development in Google IDX by integrating team management through Google Cloud IAM. This allows multiple developers to manage, build, and deploy immersive experiences collaboratively, enhancing project efficiency.

   109 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

8. Alert on live activity updates

   Live Activity pushes are meant to be completely silent background updates, so Firebase’s requirement for an alert field is technically incorrect and creates unnecessary sound/vibration issues.

   When sending APNs messages with "apns-push-type": "liveactivity" via Firebase Cloud Messaging (FCM), the service currently requires an "aps.alert" field to be present in the payload.

   However, Live Activity updates are designed by Apple to be silent background updates, they should not display alerts, play sounds, or trigger any user-visible notification behavior.

   Because FCM enforces the presence of "aps.alert", developers are forced to include dummy or empty alert values (e.g. "alert": {}), which can still cause unwanted side effects or violate Apple’s Live Activity design guidelines.

   Live Activity pushes are meant to be completely silent background updates, so Firebase’s requirement for an alert field is technically incorrect and creates unnecessary sound/vibration issues.

   When sending APNs messages with "apns-push-type": "liveactivity" via Firebase Cloud Messaging (FCM), the service currently requires an "aps.alert" field to be present in the payload.

   However, Live Activity updates are designed by Apple to be silent background updates, they should not display alerts, play sounds, or trigger any user-visible notification behavior.

   Because FCM enforces the presence of "aps.alert", developers are forced to include dummy or empty alert values (e.g. "alert": {}), which can still… more

   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

   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

9. Enable support for iPad/Tablets using Browser apps Chrome/Safari/Firefox etc.

   I should be able to use IDX on my chrome app on my iPad.

   178 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

   19 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. Cloud Firestore Datasource

    Support Cloud Firestore as a datasource for Data Connect in addition to Cloud SQL. Support data model mapping (e.g. @collection) and querying via GraphQL

    177 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

    11 comments  ·  Data Connect  ·  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. Integrate Gemini 2.5 Pro into Code Editor with Increased Daily Usage

    While Gemini 2.5 Pro has improved the prototyping experience in Firebase Studio, its utility is limited when working with custom projects. Uploading or replacing a project with custom files often restricts Gemini's functionalities, and essential development tools like Git integration, extensions, and server setup aren't accessible within the prototyping mode.

    Proposal:

    Integrate Gemini 2.5 Pro into the Code Editor as well: Extending Gemini 2.5 Pro's capabilities to the code editor would provide consistent AI assistance throughout the development process.

    Increase Daily Usage Limit: Raising the daily action limit from 25 to 50 would accommodate more extensive development sessions, enhancing productivity without overwhelming system resources.

    I beleive that, by implementing these enhancements would solidify Firebase Studio's position as a comprehensive, full-stack development tool.

    While Gemini 2.5 Pro has improved the prototyping experience in Firebase Studio, its utility is limited when working with custom projects. Uploading or replacing a project with custom files often restricts Gemini's functionalities, and essential development tools like Git integration, extensions, and server setup aren't accessible within the prototyping mode.

    Proposal:

    Integrate Gemini 2.5 Pro into the Code Editor as well: Extending Gemini 2.5 Pro's capabilities to the code editor would provide consistent AI assistance throughout the development process.

    Increase Daily Usage Limit: Raising the daily action limit from 25 to 50 would accommodate more extensive development sessions, enhancing productivity… more

    19 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

12. Let Gemini Handle Everything in the Firebase Console

    It would be amazing if Gemini could handle everything in the Firebase Console directly. For example, if I ask something in the Firebase Studio chat, it should be able to do all the backend setup on its own—like authentication, database setup, rules, Realtime Database, or anything else needed to make an app fully functional.

    For people like me who don’t know coding or have much tech knowledge, the Firebase Console can feel super overwhelming. There are so many features and tools, and I honestly don’t know what most of them do. If Gemini could just take care of all that for us, it would make things way easier and way more user-friendly.

    It would be amazing if Gemini could handle everything in the Firebase Console directly. For example, if I ask something in the Firebase Studio chat, it should be able to do all the backend setup on its own—like authentication, database setup, rules, Realtime Database, or anything else needed to make an app fully functional.

    For people like me who don’t know coding or have much tech knowledge, the Firebase Console can feel super overwhelming. There are so many features and tools, and I honestly don’t know what most of them do. If Gemini could just take care of all that… more

    15 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. Make the Agent Response Faster

    The agent response is pretty slow in Firebase Studio Prototyper mode as the project is growing. Wish we can fix this issue.

    14 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

    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

14. Improvement Suggestion for Firebase Studio - Third-Party AI Integration

    Observed Problem:

    Currently, the integrated Gemini assistant in Firebase Studio tends to lose context during long development sessions. This context loss, likely exacerbated by a large chat history, leads to a degradation in the relevance of suggestions and code corrections.

    It is often observed that external AI models (such as ChatGPT, Claude, etc.) can more effectively identify and resolve certain complex code issues. This forces developers to copy-paste their code outside of the Firebase environment, which disrupts the workflow and reduces productivity.

    Proposed Solution:

    Allow developers to connect and use third-party AI models directly within the Firebase Studio interface.

    This feature could take the form of:

    An AI Model Selector: Add a dropdown menu or a configuration panel where the user could choose the AI engine to use for code analysis and generation (e.g., Gemini by default, or a third-party model).

    Configuration via API Key: Integration could be achieved simply by allowing the user to provide their own API key for their chosen AI service (e.g., OpenAI, Anthropic, etc.).

    Benefits of this Feature:

    Flexibility and Power: Developers could choose the best tool for a specific task, leveraging the strengths and specializations of each AI model.

    Improved Productivity: By centralizing the workflow within Firebase Studio, this reduces the need to juggle multiple windows and tools.

    Context Continuity: If Gemini struggles with a specific point, the user could switch to another model without losing the current session's context.

    Better Solutions: The ability to "audit" or request a second opinion on a piece of code from another AI would lead to more robust and optimized solutions.

    In summary, this flexibility would transform Firebase Studio into an even more powerful and adaptable AI-assisted development platform, tailored to the real and varied needs of developers.

    Observed Problem:

    Currently, the integrated Gemini assistant in Firebase Studio tends to lose context during long development sessions. This context loss, likely exacerbated by a large chat history, leads to a degradation in the relevance of suggestions and code corrections.

    It is often observed that external AI models (such as ChatGPT, Claude, etc.) can more effectively identify and resolve certain complex code issues. This forces developers to copy-paste their code outside of the Firebase environment, which disrupts the workflow and reduces productivity.

    Proposed Solution:

    Allow developers to connect and use third-party AI models directly within the Firebase Studio interface.

    This… more

    11 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

15. new chat feature in prototyper

    i suggest that firebase studio comes with the ability to clear the text chat (start a new chat) in the prototyper, additionally if a chat got too long, a part of the previous conversation doesnt have to be loaded, instead include a button to load the very past chats so perhaps it can enhance the performance

    15 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

16. Offline Support

    Allow data to be cached and accessible offline. Offline data may have limited query and write capabilities compared to online data

    161 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

    9 comments  ·  Data Connect  ·  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. Change Firebase Studio AI Region for Better Ping

    Hey Firebase Studio AI users,

    Want faster performance? We’re exploring a new feature to let you switch your project’s region to one closer to your users, reducing ping and boosting app speed.

    To make this happen:

    Check Region: View your current region in Firebase Console > Project Settings.
    Test Latency: Ping Google Cloud regions (e.g., ping us-central1-gce.cloud.google.com) to find the best fit.
    Migrate Project: Create a new project in the desired region and transfer data manually.
    Optimize with CDN: Use Firebase Hosting’s global CDN to cache content for even faster delivery.
    This could be a game-changer for latency-sensitive apps.

    20 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

18. Request for Flutter Support with iOS Simulator in IDX

    Please include support for the iOS simulator within IDX for Flutter projects. This addition would greatly simplify the process of testing and debugging iOS apps directly within IDX, eliminating the need for external tools or complex setups. If iOS support is disabled, kindly provide a reason for the decision. Thank you for considering this request.

    232 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

    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

19. Android/ios native app, code from app on your phone connects to idx

    native apps for making it easy for on the go

    24 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. Fastlane - Get automatically app key from google-services.json

    All Android application that included Firebase have mandatory this file : google-services.json

    When we want automatize delivery with fastlane on Firebase, we need to provide many informations on the lane such like "app", "servicecredentialsfile",...

    In fact, many Android projects has one or more build flavors and the delivery can be harder with the configuration on which target we want to deploy.

    We need to store many sensitive informations like key on the env file.
    We not push this file on the repository and it's not a good practice to have them has CI variables.

    The purpose of this feature request is to automatize the retrieve of app key from google-services.json.
    For this, we just need few informations on env / CI file :
    - location of google-services.json (that can be split in an other feature) *1;
    - package name declared on env / CI file.

    Only with your package name, you can retrieve (or not) your app key from google-services.json.
    This is a snippet of code for make this one :

    Parse the JSON content

    jsondata = JSON.parse(filecontent)

    Search for the appid corresponding to the packagename

    appid = ""
    jsondata["client"].each do |client|
    if client["clientinfo"]["androidclientinfo"]["package_name"] == targetpackagename
    appid = client["clientinfo"]["mobilesdkapp_id"]
    break
    end
    end

    All Android application that included Firebase have mandatory this file : google-services.json

    When we want automatize delivery with fastlane on Firebase, we need to provide many informations on the lane such like "app", "servicecredentialsfile",...

    In fact, many Android projects has one or more build flavors and the delivery can be harder with the configuration on which target we want to deploy.

    We need to store many sensitive informations like key on the env file.
    We not push this file on the repository and it's not a good practice to have them has CI variables.

    The purpose of this… more

    11 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