2073 results found

1. We need to integrate robust Flutter coding within Firebase Studio to streamline our development process and enhance app performance.

   The proposal focuses on uniting the powerful front-end development capabilities of Flutter with the comprehensive backend management offered by Firebase Studio. By embedding Flutter’s efficient coding environment into the workflow of Firebase Studio, developers can seamlessly design and implement dynamic user interfaces while simultaneously leveraging Firebase’s robust real-time databases, authentication services, cloud storage, and analytics tools. This integration not only accelerates the development cycle by enabling rapid testing and deployment but also ensures that both the client-side and server-side systems work harmoniously. Ultimately, this strategy aims to create scalable, performance-optimized applications with a unified platform that simplifies project management, enhances collaboration across development teams, and adapts flexibly to evolving project requirements.

   The proposal focuses on uniting the powerful front-end development capabilities of Flutter with the comprehensive backend management offered by Firebase Studio. By embedding Flutter’s efficient coding environment into the workflow of Firebase Studio, developers can seamlessly design and implement dynamic user interfaces while simultaneously leveraging Firebase’s robust real-time databases, authentication services, cloud storage, and analytics tools. This integration not only accelerates the development cycle by enabling rapid testing and deployment but also ensures that both the client-side and server-side systems work harmoniously. Ultimately, this strategy aims to create scalable, performance-optimized applications with a unified platform that simplifies project management, enhances… more

   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

2. Firebase Studio needs to have revertable checkpoints after every Gemini edit
   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

3. Add npm workspace support for monorepos

   App Hosting already supports nx based monorepos, but it would be great to have basic npm workspace support. I tried to take the plunge and convert my repo to nx tooling but I failed spectacularly 🙂 npm workspaces are super simple to get started with and other than not being able to deploy to App Hosting, they haven't come up short for me in a way that would convince me to try nx again.

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

4. DeepDarkWEB

   $13!

   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

5. It would be nice if there were a way to roll back to a state when the application was working.

   I would find it helpful to be able to roll back when needed to a state where the app in development functioned. Particularity useful when trying to add features that stall out and break the app.

   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

   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

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

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

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

   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

   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. Confirmation Before Firebase AI Applies Changes

   With the rise of AI-assisted development, many of us are used to casually chatting with AI — sometimes just asking for suggestions or even giving compliments. However, in Firebase, I’ve noticed that AI often directly applies comments/requests to the project without asking for confirmation.

   This can be frustrating and risky, since a casual message can unintentionally trigger real changes to the project.

   Suggestion:

   Add a confirmation dialog (or toggle in settings) that controls whether Firebase AI should:

   Directly implement all requests automatically, or

   Confirm with the developer first before making any changes.

   Benefits:

   Prevents accidental or unintended project changes.

   Lets developers choose between fast auto-implementation or a safer confirm-first workflow.

   Provides more control, especially when experimenting or casually interacting with Firebase AI.

   With the rise of AI-assisted development, many of us are used to casually chatting with AI — sometimes just asking for suggestions or even giving compliments. However, in Firebase, I’ve noticed that AI often directly applies comments/requests to the project without asking for confirmation.

   This can be frustrating and risky, since a casual message can unintentionally trigger real changes to the project.

   Suggestion:

   Add a confirmation dialog (or toggle in settings) that controls whether Firebase AI should:

   Directly implement all requests automatically, or

   Confirm with the developer first before making any changes.

   Benefits:

   Prevents accidental or unintended project changes.

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

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

11. : “Make Firebase the best home for AI + Media: Vector Search, AI Studio (Genkit), India‑first Auth, and Media Extensions”

    We’re building LegacyVerse Studio—a global, culture‑rooted AI platform (clones, memories, voice, and music). To keep Firebase at the heart of our stack, we need:

    1. Managed Vector Search for Firestore (embeddings + whereNear()),

    2. Firebase + Genkit “AI Studio” in Console (flows, tools, evals, deploy, cost dashboard),

    3. Official AI Media Extensions: Gemini TTS/STT, audio transcode to HLS/MP3, normalization, subtitles,

    4. India‑first Phone Auth improvements (DLT, fallback providers, better deliverability & pricing clarity),

    5. Edge Functions on Hosting with streaming (SSE) for low‑latency AI,

    6. Firestore TTL + simple archival tier for cost control,

    7. Built‑in multi‑tenant RBAC patterns for orgs/workspaces,

    8. Native full‑text search (Indic aware) with realtime updates,

    9. Project‑level budget & quota controls (caps, per‑user limits, AI usage analytics),

    10. Regions & data sovereignty parity in India (Auth/Functions/Extensions).

    These make Firebase the definitive platform for AI + media + multilingual apps, especially in India.
    We’re happy to share real workloads and test these features in beta. 🙏

    We’re building LegacyVerse Studio—a global, culture‑rooted AI platform (clones, memories, voice, and music). To keep Firebase at the heart of our stack, we need:

    1. Managed Vector Search for Firestore (embeddings + whereNear()),

    2. Firebase + Genkit “AI Studio” in Console (flows, tools, evals, deploy, cost dashboard),

    3. Official AI Media Extensions: Gemini TTS/STT, audio transcode to HLS/MP3, normalization, subtitles,

    4. India‑first Phone Auth improvements (DLT, fallback providers, better deliverability & pricing clarity),

    5. Edge Functions on Hosting with streaming (SSE) for low‑latency AI,

    6. Firestore TTL + simple archival tier for cost control,

    7. Built‑in multi‑tenant RBAC patterns for orgs/workspaces,

    8. Native full‑text search (Indic aware) with… 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  ·  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. 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

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

14. Travail intellectuelle

    Je vais un travail

    1 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  ·  Remote Config  ·  Edit…  ·  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. Add a Preview environment for App Hosting deployments.

    As a developer, I want to be able to deploy my Next.js web app hosted using App Hosting to a Preview "channel", similar to firebase hosting:channel:deploy in hosting.
    Thanks.

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

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

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

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

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

20. “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