1163 results found

1. Adasa

   Eleve

   1 vote

   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 →
   declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

   Thank you so much for taking the time to share your idea with us and for participating in our community.

   
   

   Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

   
   

   We appreciate your support and understanding as we transition to our next chapter.

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

   5 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 →
   declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

   Thank you so much for taking the time to share your idea with us and for participating in our community.

   
   

   Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

   
   

   We appreciate your support and understanding as we transition to our next chapter.

   
   

3. I
   1 vote

   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 →
   declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

   Thank you so much for taking the time to share your idea with us and for participating in our community.

   
   

   Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

   
   

   We appreciate your support and understanding as we transition to our next chapter.

4. Futuro de ideas 💡

   Excelente prototipo actualizador

   1 vote

   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 →
   declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

   Thank you so much for taking the time to share your idea with us and for participating in our community.

   
   

   Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

   
   

   We appreciate your support and understanding as we transition to our next chapter.

5. Support other stack when using Prototype an app with AI

   • Instead of only supporting nextjs, tailwindcss. It can also support Vite, Angular, etc...
   • Also add option to help switch between normal workspace and being able to use Prototype an app with AI
   • Add Github management section: to be able to connect once, and then each workspace can connect automatically (create repository, push, ...), can be select existed repository when create new workspace
   5 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 →
   declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

   Thank you so much for taking the time to share your idea with us and for participating in our community.

   
   

   Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

   
   

   We appreciate your support and understanding as we transition to our next chapter.

   
   

6. Transformer une PWA en application native android et iOS

   Pouvoir transformer une PWA en application native android et iOS

   3 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 →
   declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

   Thank you so much for taking the time to share your idea with us and for participating in our community.

   
   

   Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

   
   

   We appreciate your support and understanding as we transition to our next chapter.

   
   

7. NuxtJS

   I see that NextJS Reactive framework is available.. it would be awesome if Nuxt would be available too, given that Vue is available, then Nuxt would be a nice addition. :)

   2 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 →
   declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

   Thank you so much for taking the time to share your idea with us and for participating in our community.

   
   

   Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

   
   

   We appreciate your support and understanding as we transition to our next chapter.

8. Auto build Dev.nix preview for any project that is started with git hub Repo

   When a user create a new project and link it with a github repo , it should create dev.nix file and preview automatically by reading the project instead user needed this to build manually.
   Same should be done if user uploaded a project to firebase studio.

   3 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 →
   declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

   Thank you so much for taking the time to share your idea with us and for participating in our community.

   
   

   Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

   
   

   We appreciate your support and understanding as we transition to our next chapter.

   
   

9. Prototype an app with AI seems to only allow NextJS + Tailwind. Let it use clientside frameworks such as react or vue.

   Right now, you can only do nextjs + tailwind. However firebase hosting works best with single page apps like react or vue. No matter what you prompt however you can't get that.

   I'd love to see it allow you to build a vue + vuetify app that uses firebase functions for backend functions.

   Obviously i can built it myself, but the whole point of the vibe coding is i don't need to. Why call it a "firebase" product if it doesn't want to use the firebase way of building apps?

   6 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 →
   declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

   Thank you so much for taking the time to share your idea with us and for participating in our community.

   
   

   Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

   
   

   We appreciate your support and understanding as we transition to our next chapter.

10. Add an option to open a project directly in code view

    There is no option in Firebase studio, to open a project directly in code view. If you wish to do so, first you have to click on a project, opens in prototyper mode, but then you have to quickly switch to code view.

    3 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 →
    declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

    Thank you so much for taking the time to share your idea with us and for participating in our community.

    
    

    Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

    
    

    We appreciate your support and understanding as we transition to our next chapter.

    
    

11. beautiful landing pages

    should be able to make top tier beautiful landing pages... would truly disrupt an entire category of business and provide a huge convenience for entrepreneurs.

    3 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

    2 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
    declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

    Thank you so much for taking the time to share your idea with us and for participating in our community.

    
    

    Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

    
    

    We appreciate your support and understanding as we transition to our next chapter.

    
    

12. Firebase studio to support source code in google drive.

    That's when it would start feeling like VSCode. I would even go further and suggest, all the gcp artifacts could reside on my google drive folder hierarchy.

    1. source code files
    2. artifact registry
    3. infra automation code
    4. static hosting files.
    5. Resource usage and billing on google sheets.

    If that's a big ask, provide a way to map the above GCP resources as a google drive.

    It gives so much comfort that all is in my drive and I can search/copy/paste with file explorer !!

    3 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 →
    declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

    Thank you so much for taking the time to share your idea with us and for participating in our community.

    
    

    Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

    
    

    We appreciate your support and understanding as we transition to our next chapter.

    
    

13. Google remote desktop instead of vnc

    I think using google remote desktop instead of vnc will not only work better but also be less laggy, that is one of the biggest reazons i dont move for windows, google remote desktop is just better than other alternatives, and i dont understand why google, being the creator of that tecnology does not implement it.

    8 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 →
    declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

    Thank you so much for taking the time to share your idea with us and for participating in our community.

    
    

    Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

    
    

    We appreciate your support and understanding as we transition to our next chapter.

14. Firebase Studio needs to have revertable checkpoints after every Gemini edit
    8 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 →
    declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

    Thank you so much for taking the time to share your idea with us and for participating in our community.

    
    

    Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

    
    

    We appreciate your support and understanding as we transition to our next chapter.

15. attaching a google doc

    I wrote my entire req in a google doc and i can't attach it. It's easier to write in a google doc than in the prompt box.

    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 →
    declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

    Thank you so much for taking the time to share your idea with us and for participating in our community.

    
    

    Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

    
    

    We appreciate your support and understanding as we transition to our next chapter.

    
    

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

    5 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 →
    declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

    Thank you so much for taking the time to share your idea with us and for participating in our community.

    
    

    Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

    
    

    We appreciate your support and understanding as we transition to our next chapter.

    
    

17. Enhance Go Development Support for Integrated GUI Applications in Remote/Cloud IDEs

    Enhance Go Development Support for Integrated GUI Applications in Remote/Cloud IDEs

    To the Google Firebase/Cloud Platform Team,

    I am writing to provide critical feedback on the current Go development experience within cloud-based IDE environments (such as Cloud Workstations or Cloud Shell Editor) and to propose a significant feature enhancement that aligns with modern full-stack development trends.

    1. Summary of the Strategic Goal: Go for End-to-End Applications

    Our objective is to leverage the performance and cross-compilation capabilities of Go (Golang) for developing integrated, full-stack applications—specifically, those combining high-performance Go backends with modern Go-based Graphical User Interfaces (GUIs).

    The ability to rapidly prototype, debug, and run Go-based frontends (e.g., using toolkits like Fyne, Wails, or Gioui) within the same remote environment used for backend and cloud service development is an essential step toward achieving a truly unified, holistic cloud development workflow for the Go ecosystem.

    1. The Technical Limitation: The Headless Barrier

    While the remote IDE is robust for compiling and executing server-side Go services, it fundamentally fails when attempting to execute applications that require access to a display server.

    The Issue Encountered (Proof of Concept Failure):

    When attempting to run a simple application built with fyne.io/fyne/v2, the process fails at two stages:

    Build Stage Failure: Compilation initially fails due to the absence of crucial underlying system dependencies (e.g., OpenGL, X11 header files, and required C/C++ tooling) that Go GUI toolkits rely on for linking.

    Runtime Stage Failure (Root Cause): Even after manually installing the necessary dependency libraries (e.g., libgl1-mesa-dev, xorg-dev), the application executable cannot launch because the Cloud IDE container is a "headless" environment that lacks an active X Display Server or Wayland compositor. The application terminates with errors indicating it cannot open a display connection (e.g., $DISPLAY not set).

    This structural limitation restricts Go's utility on the platform exclusively to CLI and API-only development.

    1. Impact and Value Proposition

    This limitation creates a significant friction point for Go developers:

    Fragmented Workflow: Developers are forced to compile their backend remotely but must switch to a local machine to compile, run, and debug the corresponding GUI or desktop-style frontend. This breaks the promise of a seamless, cloud-native development experience.

    Restricted Market Adoption: It limits the platform's appeal for developers who choose Go specifically for its strong cross-platform GUI options (desktop, mobile, WebAssembly).

    Loss of Debugging Efficiency: The powerful remote debugging tools available in the IDE cannot be effectively utilized for the user-facing portion of a Go application.

    The Opportunity: By solving the display server problem, Google Cloud can position Go as a premier language for truly integrated full-stack development, appealing to users who value the concurrency and single-binary deployment advantages Go offers.

    1. Proposed Solution: Integrated Virtual Display Streaming (The Key Feature)

    The most robust solution involves integrating a mechanism to provision and stream a virtual graphical environment directly into the user's browser.

    Primary Feature Ask: Virtual Display and Streaming

    We request the implementation of a service that automatically handles the graphical runtime environment:

    Virtual Display Service: Automatically initialize and manage a virtual display server (such as Xvfb or a similar in-memory display buffer) within the development container.

    Dependency Pre-configuration: Ensure that all standard Go development environments (or a dedicated "Go GUI" template) are pre-installed with the required X11, OpenGL, and C/C++ development libraries necessary for major Go GUI toolkits to compile successfully.

    Low-Latency Streaming: Implement a low-latency, WebSockets-based streaming solution (e.g., leveraging VNC/noVNC principles) that captures the output of the virtual display and renders it in a dedicated browser tab or pane within the Cloud IDE, allowing for full mouse and keyboard interaction.

    Execution Flow: A developer should be able to simply execute a Go GUI application (e.g., go run main.go), and the IDE automatically starts the necessary forwarding/streaming process, showing the interactive application window.

    Minimum Requirement: Clear Guidance and Pre-configuration

    At a minimum, if real-time streaming is not immediately feasible, we request:

    Pre-configured Base Images: Offer official container images that include the necessary system dependencies (libgl1-mesa-dev, xorg-dev, etc.) to guarantee that Go GUI applications can at least successfully compile and be packaged/built for local deployment, eliminating the "missing dependency" build errors.

    Clear Documentation: Provide prominent documentation explicitly detailing the headless limitation and directing users toward the supported cross-compilation workflow for Go GUI applications.

    By integrating the Virtual Display Streaming capability, you will transform the developer experience for a growing segment of the Go community and significantly expand the scope of application development supported by the Firebase and Google Cloud platforms.

    Thank you for your review and consideration of this strategic enhancement.

    Enhance Go Development Support for Integrated GUI Applications in Remote/Cloud IDEs

    To the Google Firebase/Cloud Platform Team,

    I am writing to provide critical feedback on the current Go development experience within cloud-based IDE environments (such as Cloud Workstations or Cloud Shell Editor) and to propose a significant feature enhancement that aligns with modern full-stack development trends.

    1. Summary of the Strategic Goal: Go for End-to-End Applications

    Our objective is to leverage the performance and cross-compilation capabilities of Go (Golang) for developing integrated, full-stack applications—specifically, those combining high-performance Go backends with modern Go-based Graphical User Interfaces (GUIs).

    The ability to rapidly prototype,… more

    1 vote

    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 →
    declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

    Thank you so much for taking the time to share your idea with us and for participating in our community.

    
    

    Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

    
    

    We appreciate your support and understanding as we transition to our next chapter.

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

    6 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 →
    declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

    Thank you so much for taking the time to share your idea with us and for participating in our community.

    
    

    Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

    
    

    We appreciate your support and understanding as we transition to our next chapter.

19. Clear parts of context

    If I rollback a change to the project, but the previous change is still in context then future changes are poisoned. I need a way to clear part of the context. Or even just resetting the context would help.

    5 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 →
    declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

    Thank you so much for taking the time to share your idea with us and for participating in our community.

    
    

    Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

    
    

    We appreciate your support and understanding as we transition to our next chapter.

    
    

20. Enhanced Git Branch Integration in Prototyping View

    Hello Firebase Team,

    I'd like to propose a feature enhancement for the Prototyping view in Firebase Studio that would significantly improve the development workflow.

    My suggestion consists of two parts:

    1. Current Branch Visibility: Display the name of the active Git branch somewhere visible within the Prototyping UI. This would prevent confusion and eliminate the need to switch back to the terminal or IDE to confirm the current branch.

    2. In-UI Branch Switching: Add a dropdown menu or a similar control that allows developers to quickly switch between their local Git branches directly from the Prototyping view.

    Implementing this would streamline the process of testing and comparing different feature branches, making development much more efficient. Thank you for your consideration.

    Hello Firebase Team,

    I'd like to propose a feature enhancement for the Prototyping view in Firebase Studio that would significantly improve the development workflow.

    My suggestion consists of two parts:

    1. Current Branch Visibility: Display the name of the active Git branch somewhere visible within the Prototyping UI. This would prevent confusion and eliminate the need to switch back to the terminal or IDE to confirm the current branch.

    2. In-UI Branch Switching: Add a dropdown menu or a similar control that allows developers to quickly switch between their local Git branches directly from the Prototyping view.

    Implementing this would streamline the… more

    2 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 →
    declined  ·  AdminSeba Gnagnarella (Admin, Google, LLC - Firebase) responded

    Thank you so much for taking the time to share your idea with us and for participating in our community.

    
    

    Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.

    
    

    We appreciate your support and understanding as we transition to our next chapter.