2111 results found

1. Allow users to select important milestones for restoration.

   I recently found that the looooooooong chat was removed and it improved the response time of coding. That was great. But there was a downside to it. I lost many important milestones, that i might have wanted to restore back to. It will be great if you allow the users to mark important milestones to retain when the cleaning of chat happens. That way they will be able to restore back to preferred versions in case required.

   Or they will be stuck with the experimental request that led to more damage than good.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Cloning my app or tool or website

   Being able to clone my work would allow me to reuse something I built and that works instead of forcing me to reinvent the wheel again and again if I need to build something similar for someone else.

   5 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

3. Automatic commits on change

   When making changes via the chat, sometimes there are errors that interrupt it halfway through, sometimes I make changes and regret the choice, whatever.

   I've been able to solve this by making sure to commit before/after each set of instructions, but this should be automated. The commit content can include Geminis reasoning or just keep track of versions

   6 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

4. Built-in App Versioning & Rollback Feature

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

   Provide a version history dashboard to easily track changes, along with the commands/prompts that triggered them.

   Add a rollback mechanism to fully restore a previous version of the app (even if restoring the entire project takes time).

   • * * Benefits:

   Eliminates the need to manually duplicate projects for backup.

   Gives developers confidence to make major updates without fear of unrecoverable errors.

   Provides transparency and accountability in the development workflow.

   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… more

   2 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

5. Rashed

   Rashed

   5 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

   7 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. Firebase studio project restoration from trash if deleted

   There should be a trash box

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. 🚀 Advanced Proposal: Hybrid Firebase Architecture for Optimized Performance, Offline Access & Cloud Resilience

   🧠 Core Strategy

   1. Deploy Firebase Studio locally (on-premise or VM)

   2. Integrate with Firebase Emulator Suite + Edge Cache

   3. Enable automatic sync with Firebase Cloud

   4. Allow direct access to local services (filesystem, DB, devices)

   5. Use secure reverse tunnels and proxy APIs for controlled cloud interactions

   ---

   ✅ Key Benefits Overview

   Feature Benefit

   ✅ Offline First Use Firebase Emulator Suite to run Firestore, Auth, Hosting, Functions entirely offline
   ✅ Faster Performance Local queries eliminate latency from cloud round-trips
   ✅ Access Local Resources Direct access to local files, OS services, SQLite, or PostgreSQL
   ✅ Data Control Comply with GDPR/PDPA by keeping sensitive data local
   ✅ Failsafe Operations Local Firebase runs even when internet is unavailable
   ✅ Auto Cloud Sync Sync local Firestore changes to Firebase Cloud when connected
   ✅ Edge Firebase Deploy Firebase Studio app via Cloudflare Workers/Fly.io for global low-latency access
   ✅ Multi-Environment Support Seamlessly test across local, edge, and cloud environments
   ✅ Security Tightened Use Firebase rules + local VPN + JWT-protected API proxy

   ---

   ⚙️ Recommended Components

   Component Purpose

   🔸 Firebase Emulator Suite Local Firestore, Functions, Hosting, and Auth
   🔸 Dockerized Firebase Studio Containerized deployment on any server or laptop
   🔸 Edge Caching (Cloudflare/Fly.io) For performance + reduced global latency
   🔸 Secure API Proxy (NGINX + JWT) Gatekeeper for accessing cloud endpoints
   🔸 Local DB (e.g. SQLite, PostgreSQL) Optional secondary storage/mirror
   🔸 Sync Engine (Node.js/Cloud Functions) Automated bidirectional sync to Firebase Cloud
   🔸 Local Admin Panel (Optional) UI to manage users, data, and deployments offline

   ---

   💡 Real-World Use Cases & Advantages

   🛍️ Point-of-Sale (POS) App

   Works offline in restaurants or kiosks

   Syncs sales data to Firebase Cloud when online

   Supports local printers and receipt scanners directly

   🛡️ Security or IoT System

   Sensors log data to local Firestore (offline)

   No internet needed for core functionality

   Syncs logs or events to Firebase Cloud daily

   🏫 Education System / LMS

   Operates in classrooms without stable WiFi

   Tracks student progress locally

   Syncs to cloud at home or when reconnected

   ---

   🔧 Bonus Features (Optional Add-ons)

   Add-on Description

   🔁 Realtime Sync Layer Use tools like Replicache or PouchDB for smooth 2-way sync
   🔐 Local Audit Logging Keep full trace of all data and user actions offline
   🧠 Offline AI Integration Use ONNX or local ML models without cloud inference

   ---

   🔥 Summary

   This goes beyond just deploying Firebase Studio locally. We're talking about building a resilient, high-performance Firebase hybrid ecosystem — one that operates seamlessly offline, scales globally via edge servers, and syncs intelligently to the cloud.

   🧠 Core Strategy

   1. Deploy Firebase Studio locally (on-premise or VM)

   2. Integrate with Firebase Emulator Suite + Edge Cache

   3. Enable automatic sync with Firebase Cloud

   4. Allow direct access to local services (filesystem, DB, devices)

   5. Use secure reverse tunnels and proxy APIs for controlled cloud interactions

   ---

   ✅ Key Benefits Overview

   Feature Benefit

   ✅ Offline First Use Firebase Emulator Suite to run Firestore, Auth, Hosting, Functions entirely offline
   ✅ Faster Performance Local queries eliminate latency from cloud round-trips
   ✅ Access Local Resources Direct access to local files, OS services, SQLite, or PostgreSQL
   ✅ Data Control Comply with GDPR/PDPA by keeping sensitive data local… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Cloud Functions for Firebase  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. How to download my files or scripts from Firebase Studio

   How to download my files or scripts from Firebase Studio

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   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

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

    5 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

11. Add support for Google Play "automatic protection"

    Currently, manual steps on the play store developer console is required to create an application that has Play Store "automatic protection" enabled:
    https://support.google.com/googleplay/android-developer/answer/10183279

    We have found that "automatic protection" is error-prone in multi-process applications and applications that include native libraries/code. It would be really helpful to our manual QA process to be able to programmatically distribute applications with "automatic protection" enabled on them.

    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

    0 comments  ·  App Check  ·  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. Support Markdown format for release notes files

    When attaching release notes to a release using App Distribution, it would be great if Markdown files were supported and rendered (release emails, inside the Tester app, in the Console, etc).

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

13. Physical device support

    Add support for running the flutter Projects on the user's phyical deice connected through ADB

    148 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

    5 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. New products of instant support software for solving and making decisions

    Instant programs to support decision-making in various fields, whether business, entertainment, health, food, or even worship.

    3 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

15. Links

    Reliable

    2 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  ·  Extensions  ·  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. easy hosting

    Hi, I completely understand that Firebase Studio is fantastic for "vibe-coding" – even for experienced developers! However, after quickly building a front-end, I've found myself stuck on the next steps.

    I've been trying for weeks to deploy a fully functional app but struggle with the backend aspects. I've explored Firebase Hosting, Firestore, Realtime Database, and Authentication, but for a non-coder who was excited by the "vibe-coding" concept, these backend tasks are incredibly challenging. It would be amazing if there were easier ways to handle this, perhaps as simple as filling out a form or using natural language requests. While I know this might not be easy to implement, making the backend truly accessible is where "vibe-coding" could become a real game-changer.

    Hi, I completely understand that Firebase Studio is fantastic for "vibe-coding" – even for experienced developers! However, after quickly building a front-end, I've found myself stuck on the next steps.

    I've been trying for weeks to deploy a fully functional app but struggle with the backend aspects. I've explored Firebase Hosting, Firestore, Realtime Database, and Authentication, but for a non-coder who was excited by the "vibe-coding" concept, these backend tasks are incredibly challenging. It would be amazing if there were easier ways to handle this, perhaps as simple as filling out a form or using natural language requests. While I… more

    5 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 Hosting  ·  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. Support for Java

    Project IDX should support Java due to its versatility and widespread use in developing various applications across different domains, from web development to mobile applications.

    129 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

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

    We have released a preview version of our Java support for you all to try out! :-)

    
    

    https://community.idx.dev/t/check-out-our-new-backend-focused-templates/746

    
    

    Feel free to reply in the forums itself with your feedback.

18. “Support Drupal”

    Please support development with the Drupal Content Management Framework, at least at the level that it is supported by Jetbrains and Microsoft.

    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  ·  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. Support geographic area and proximity searches with PostGIS

    Add GeoPoint and GeoBox scalar types and enable rich geo searching queries including indexing, "search within area", "find closest to point within radius", etc.

    35 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

    4 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

20. MariaDB Vector

    Latest version of MariaDB has support for vectors. I need that for implementing RAG solutions. Please add MariaDB as a database template!

    7 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