2325 results found

1. Une fonction pour directement télécharger
   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

2. I would like to import the source code of an existing GitHub repository from Firebase Studio Prototyper Gemini so that I can modify it. This

   I would like to import the source code of an existing GitHub repository from Firebase Studio Prototyper Gemini so that I can modify it. This feature is very useful, so please consider it.

   As a specific example, I would like to import the source code of the following GitHub repository so that I can modify it from Firebase Studio Prototyper Gemini.
   https://github.com/okamoto53515606/homepage

   PS)
   Until the above feature is available, I plan to proceed as follows:
   1. Instruct Firebase Studio Prototyper to create a dummy app (with minimal functionality).
   2. Press the "Publish" button to create app hosting for the dummy app (with minimal functionality).
   3. Open a terminal in Firebase Studio.
   4. In the Firebase Studio terminal, download and unzip the tar.gz file from GitHub.
   5. Run npm install again in the Firebase Studio terminal.
   6. Run "Restart" from Firebase Studio to rebuild your Firebase Studio development environment.
   7. Have prototyper gemini review the contents of the new docs folder and understand the structure of your app.
   8. Ask prototyper gemini to make any corrections.

   I would like to import the source code of an existing GitHub repository from Firebase Studio Prototyper Gemini so that I can modify it. This feature is very useful, so please consider it.

   As a specific example, I would like to import the source code of the following GitHub repository so that I can modify it from Firebase Studio Prototyper Gemini.
   https://github.com/okamoto53515606/homepage

   PS)
   Until the above feature is available, I plan to proceed as follows:
   1. Instruct Firebase Studio Prototyper to create a dummy app (with minimal functionality).
   2. Press the "Publish" button to create app hosting for the dummy… 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

3. Please communicate the following information to Gemini, the prototyper, in advance. Please also provide Gemini with a development preview UR

   Please communicate the following information to the prototyper, Gemini, in advance. Please also provide the development preview URL to the prototyper, Gemini, in advance.

   Firebase Studio Development Environment Workflow and Knowledge

   This document summarizes the knowledge required for AI development partners (App Prototypers) to understand the characteristics of this development environment and work smoothly with users.

   1. Terminal and Command Execution

   Available Command Line Tools

   The following main commands are available in the terminal of this environment.

   • git: Version control
   • gcloud: Google Cloud resource operations
   • firebase: Firebase project operations

   How to Execute Commands

   In dialogue with the user, the AI ​​presents commands to be executed.

   • `bash Markdown: When commands are presented in this format, an execute button (▶) appears in the user interface. The user can execute the command simply by pressing this button.
   • AI Cannot Execute Directly: The AI ​​itself does not have the permission to execute commands directly. The basic workflow is a collaborative one: the user executes a command, communicates the results to the AI, and then proceeds to the next step.

   2. Deployment and URL

   Deployment Flow

   • Pushing to Production: By pressing the "Publish" button in the upper right corner of the UI, the developed application is deployed to Firebase App Hosting and pushed to the production environment.

   Environment URL

   • AI Doesn't Know URLs: By default, the AI ​​does not know the development preview URL or the production URL.
   • User-Provided Information: The user can run a command such as firebase apphosting:backends:list and provide the AI ​​with the URL identified from the command. The AI ​​can then remember that information as context and use it for future development (such as CORS configuration).
   • Example of URL confirmed:
   • Preview URL: https://9000-firebase-studio-*.cloudworkstations.dev/
   • Production URL: URL confirmed using the firebase apphosting:backends:list command

   3. Infrastructure Configuration Workflow Example

   In addition to code, Firebase and Google Cloud infrastructure configuration can also be performed in conjunction with AI.

   1. User specifies the goal: (Example: "I want to securely set the service account's private key as an environment variable.")
   2. AI plans and suggests commands:
   3. Check the account with gcloud iam service-accounts list.
   4. Use gcloud iam service-accounts keys create - ... to output the key to standard output without saving it to a file.
   5. User executes command: Executes the suggested command and optionally provides feedback to the AI ​​with the results.
   6. Continuous Operation Through Collaboration: The AI ​​suggests the next step based on feedback.

   This workflow allows users unfamiliar with commands to safely and accurately configure infrastructure with the assistance of the AI.

   4. Version Control (Git) Workflow Example

   How Auto-Commit Works

   The AI ​​suggests file changes, and once they're applied, the changes are automatically committed to Git. The commit message contains the AI's instructions (user prompts).

   Reverting to a Specific Commit

   You can also revert a project to a specific past state through interaction with the AI.

   1. AI suggests a history check command: The AI ​​suggests a command such as git log --oneline.
   2. User executes a command and shares the results: The user executes a command and shares the displayed commit history with the AI.
   3. User specifies the commit to revert to: The user identifies the commit in the history to which they want to revert.
   4. AI suggests a rollback command: The AI ​​suggests a command to return to a specified state, such as git reset --hard <commit ID>.
   5. User executes a command: The user executes the command, reverting the project's files to a previous version.

   I would like to see the prototyper gemini be able to execute terminal commands directly.
   I would appreciate your consideration.

   Please communicate the following information to the prototyper, Gemini, in advance. Please also provide the development preview URL to the prototyper, Gemini, in advance.

   Firebase Studio Development Environment Workflow and Knowledge

   This document summarizes the knowledge required for AI development partners (App Prototypers) to understand the characteristics of this development environment and work smoothly with users.

   1. Terminal and Command Execution

   Available Command Line Tools

   The following main commands are available in the terminal of this environment.

   • git: Version control
   • gcloud: Google Cloud resource operations
   • firebase: Firebase project operations

   How to Execute Commands

   In dialogue with the… 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

4. Put the collection name in the beginning of the page title of the Firebase web console

   Right now it goes "Project Name - Database - Data - Firebase console" which can get confusing when i have multiple tabs open.

   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  ·  Firestore  ·  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. allow app hosting without a cloud billing account

   Firebase app hosting without a cloud billing account should be possible.
   Also to have a custom subdomain for the app url.
   Most people use Google and other tools without any billing account. So there is a high potential of firebase users for this feature. Also to simplify to publish the app without needing to know how CLI works within the firebase studio.

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

6. Support Request – Firebase Studio Preview & Environment Variables Subject: Firebase Studio Preview does not allow setting custom environmen

   Support Request – Firebase Studio Preview & Environment Variables

   Subject: Firebase Studio Preview does not allow setting custom environment variables (Admin SDK / Service Account issue)

   Hello Firebase Studio Support Team,

   I’m using Firebase Studio (Cloud Workstations) with a Next.js (App Router, Server Actions) project that uses Firebase Admin SDK to write to Firestore.

   I’m encountering a blocking issue with environment variable management in Firebase Studio Preview.

   🔍 Problem Description

   My application requires a service account to initialize Firebase Admin SDK.
   Normally this is done via an environment variable such as:

   FIREBASESERVICEACCOUNT_KEY=<base64-encoded service account JSON>

   However, in Firebase Studio Preview:

   There is no UI or documented way to define custom environment variables or secrets

   Preview automatically injects GOOGLEAPPLICATIONCREDENTIALS

   This causes Admin SDK to fall back to Application Default Credentials (ADC)

   ADC fails in Preview with errors like:

   Getting metadata from plugin failed
   Could not refresh access token (HTTP 500)

   Even when using dotenv or runtime logic, this cannot be overridden because the env is injected before the Node process starts.

   📜 What I Tried

   Removing GOOGLEAPPLICATIONCREDENTIALS from .env

   Forcing credentials in code (cert(serviceAccount))

   Using dotenv

   Using Firebase CLI (functions:config:set)

   Restarting / rebuilding Preview

   Searching for Preview env / secrets configuration

   None of these allow injecting a custom env variable into the Preview runtime.

   ❓ Questions

   Is it currently supported to define custom environment variables or secrets for Firebase Studio Preview?

   If yes, where is this documented or configured?

   If not, is there a recommended workflow for projects using:

   Next.js Server Actions

   Firebase Admin SDK

   Firestore writes

   Is Preview intended only as a frontend-only viewer, not a backend runtime?

   🎯 Impact

   This limitation prevents:

   Testing Admin SDK logic

   Firestore write operations

   Any backend logic that depends on secure credentials

   At the moment, the only working solution is local development or Cloud Run/App Hosting, which defeats the purpose of Preview for full-stack apps.

   Thank you for your help.
   Clarification or documentation on this would be very valuable.

   Best regards,
   Murat

   Support Request – Firebase Studio Preview & Environment Variables

   Subject: Firebase Studio Preview does not allow setting custom environment variables (Admin SDK / Service Account issue)

   Hello Firebase Studio Support Team,

   I’m using Firebase Studio (Cloud Workstations) with a Next.js (App Router, Server Actions) project that uses Firebase Admin SDK to write to Firestore.

   I’m encountering a blocking issue with environment variable management in Firebase Studio Preview.

   🔍 Problem Description

   My application requires a service account to initialize Firebase Admin SDK.
   Normally this is done via an environment variable such as:

   FIREBASESERVICEACCOUNT_KEY=<base64-encoded service account JSON>

   However, in Firebase… 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

   1 comment  ·  Firebase CLI  ·  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. NEW ALL-ROUNDER AI CREATION self by FIREBASE,Android,Replit etc . ALL cooperated

   by FIREBASE,Android,Replit etc . and then make that AI Go its Developments on its own and on and so on ....make fire studio do everything to make an AI that independent and strong enough tdo everything for their own developments?

   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

8. Add a CLI flag for hosting project previous release count option

   I have an ecommerce SAAS company where each client/tenant website is hosted on Firebase Hosting. We have over 80 websites hosted across six Firebase projects.

   We create each new site using the Firebase CLI:

   firebase hosting:sites:create [options] <siteId>

   The only options for this command are:

   --app <appId> specify an existing Firebase Web App ID
   -h, --help display help for command

   I'd like to request an additional option to set the "previous releases to keep", aka "previous release count".

   After I create a new site, I have to deploy the new website to Firebase hosting before I can set the previous release count on the Firebase Hosting website. The website won't let me set the release count before deploying my first release.

   If I can set this previous release count when creating the site, then I don't have to wait until after I complete these two required steps (plus remember to do it).

   If I forget to set the previous release count, then I'll end up with too many previous releases that I'm paying for that I'll never use.

   Basically, this would eliminate one of the many little annoying steps I need to do manually when launching a new tenant website.

   I have an ecommerce SAAS company where each client/tenant website is hosted on Firebase Hosting. We have over 80 websites hosted across six Firebase projects.

   We create each new site using the Firebase CLI:

   firebase hosting:sites:create [options] <siteId>

   The only options for this command are:

   --app <appId> specify an existing Firebase Web App ID
   -h, --help display help for command

   I'd like to request an additional option to set the "previous releases to keep", aka "previous release count".

   After I create a new site, I have to deploy the new website to Firebase hosting before I can set the previous… 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  ·  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

9. Don't require Github integration for App Hosting Backends

   I'm using Cloud Build and deploying to App Hosting using the CLI. We don't have an option when running firebase apphosting:backends:create to not connect a github repo, even though with the CLI deploy option the integration is not necessary. We're able to script setup of Hosting backends, but the github connection requirement in App Hosting disables our ability to script setup of our App Hosting Backends.

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

10. AI agent

    The AI agent testing is very basic. It cannot access external urls . It does n ot let me upload files like (pdf,xml etc) to test my application. Hope it gets upgraded in the future

    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  ·  Test Lab  ·  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. Nano Banana Pro

    I realised when adding my Gemini 3 Pro Preview API in the code the chat assistant doesnt recognize it.
    Also it cant use Nano Banana Pro still. Please add it ASAP. It´s a Google feature and Firebase is also Google.

    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

12. Here is a **strong, complete, production-ready prompt** you can paste into any advanced LLM (GPT/Claude/LLaMA) to generate a **full tokenisa
    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  ·  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. I wish if i can integrate ai from aistudio.google.com to ai from firebase. and they can interconnect and share requirements.

    I wish if i can integrate ai from aistudio.google.com to ai from firebase. and they can interconnect and share requirements.

    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

14. Enable Identity Aware Proxy within Firebase Studio UI

    We’re exploring Firebase Studio as a replacement for platforms like Replit, Bolt, and Lovable for vibe-coding applications, especially because it offers seamless connectivity to private VPCs. However, one major concern is that apps become publicly accessible by default once published.

    Most vibe-coders learn cybersecurity the hard way and often end up blaming the platform, so having secure defaults is crucial. We fully support the direction Google is taking with Firebase Studio, but this issue needs to be addressed. Ideally, Firebase Studio apps should require Google authentication by default, with an explicit option for developers to make an app public only when they choose to.

    EDIT: Provide a simple option to enable Identity Aware Proxy (IAP) within the Firebase Studio UI!

    We’re exploring Firebase Studio as a replacement for platforms like Replit, Bolt, and Lovable for vibe-coding applications, especially because it offers seamless connectivity to private VPCs. However, one major concern is that apps become publicly accessible by default once published.

    Most vibe-coders learn cybersecurity the hard way and often end up blaming the platform, so having secure defaults is crucial. We fully support the direction Google is taking with Firebase Studio, but this issue needs to be addressed. Ideally, Firebase Studio apps should require Google authentication by default, with an explicit option for developers to make an app public only… 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

15. Support for Proper 404 Status Codes and Multiple 404 Pages Based on URL Patterns on Firebase Hosting

    Currently, when using a custom 404 page (e.g., 404.html), Firebase Hosting always responds with a 200 status code, even when the page is served via a rewrite rule.
    This differs from behavior on traditional servers (e.g., Nginx with the internal directive), where the server can correctly return a 404 while still serving a custom error page.

    Why this matters:
    - Proper HTTP status codes are essential for SEO.
    - Search engines may incorrectly index 404 pages if they return 200.
    - Client applications and monitoring tools rely on correct status codes.

    Additionally, In many multilingual or multi-section sites, different parts of a website require different 404 pages.
    At the moment, the only workaround is to use rewrite rules, such as:

    {
      "rewrites": [
        { "source": "/es/**", "destination": "/es/404.html" }
      ]
    }
    

    However, this still returns 200 instead of 404, which causes the same issue as above.

    Requested enhancement:
    - Allow developers to define multiple 404 handlers depending on URL patterns (e.g. /es/** → /es/404.html, /fr/** → /fr/404.html)
    - Ensure each of these handlers can return a real 404 status code

    These two capabilities would significantly improve:
    - SEO accuracy
    - Error analytics
    - User experience for multilingual or multi-section websites
    - Parity with traditional server behavior

    Thank you for considering these enhancements!

    Currently, when using a custom 404 page (e.g., 404.html), Firebase Hosting always responds with a 200 status code, even when the page is served via a rewrite rule.
    This differs from behavior on traditional servers (e.g., Nginx with the internal directive), where the server can correctly return a 404 while still serving a custom error page.

    Why this matters:
    - Proper HTTP status codes are essential for SEO.
    - Search engines may incorrectly index 404 pages if they return 200.
    - Client applications and monitoring tools rely on correct status codes.

    Additionally, In many multilingual or multi-section sites, different parts… 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  ·  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. BUILD

    LOVE

    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  ·  Authentication  ·  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. BUILDING

    LETS BUILD

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

18. Security

    Secure measures for impersonation helping keeping privacy an personal information secured from malware or attackers who are skilled am deve'

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

19. Github code review should also be done in firebase studio

    Github code review should also be done in firebase studio, like allow firebase studio be added as code reviewer

    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

20. Spanish version for Firebase studio

    It would be very beneficial to have a platform geared towards the Spanish-speaking world, both for receiving prompts and for providing responses and comments. Currently, this section is only available in English, which limits participation for many people.

    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