1222 results found

1. Project

   تحويل جيمني الي اداة امر سيادي . لقد نجحت في دمجها مع موقع حكومي فرنسي و جعلها فتح شركة و مراجعة الأخطاء خلال ساعة واحدة .... لا أعرف كيف احصل علي مكافئة و لمن ينبغي ان اقدم المشروع
   
   Converting Gemini into a sovereign command tool. I successfully integrated it with a French government website, enabling company setup and error review within one hour. I don't know how to get a reward or who to submit the project to.

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

2. Asa

   Change direct

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

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

   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  ·  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. More Advanced Filter on FPM

   Current filter in FPM dashboard is too simple with little option. The only device-based is either based on the exact model or based on OS version. I want to see more complete categories like on the Android Vital, which provides filtering based on RAM, CPU, SoC, GPU, etc.

   This way we can see which performance categories that affected the most and takes decision based on that. For example, maybe there are 2 performance issues, 1 issue only happens on 2 GB devices while the other also happens on devices with 4-6 GB RAM. This data can be matched to Play Console install base data. Lets say 50% of our use has 4-6 GB RAM while only 5% of them use device with lower than 4 GB RAM. We can prioritise to fix/improve the issue that happens on majority device first.

   Current filter in FPM dashboard is too simple with little option. The only device-based is either based on the exact model or based on OS version. I want to see more complete categories like on the Android Vital, which provides filtering based on RAM, CPU, SoC, GPU, etc.

   This way we can see which performance categories that affected the most and takes decision based on that. For example, maybe there are 2 performance issues, 1 issue only happens on 2 GB devices while the other also happens on devices with 4-6 GB RAM. This data can be matched to Play… more

   27 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  ·  Performance Monitoring  ·  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. Access user agent of the client

   App hosting replaces user agent header of the client, with "Google"
   I need to access user agent to modify responses according to user's operating system.

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

6. نجوى أمام
   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  ·  App Check  ·  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

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

8. There is an error when creating multiple applications.

   Hi Firebase Studio team and community,

   I'm running into an error when trying to create multiple applications in the platform.
   It seems like there's a limit that's causing this issue, and I have to reach out manually to request more.
   This is a bit frustrating for power users could this be fixed by introducing a paid tier for additional apps or an auto-billing option to unlock more without the hassle?

   Thanks for considering this! Firebase Studio is still the best app builder I've used.

   Best,
   Thanks
   Ryan

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

9. ATS Greens

   Visit the official ATS Greens website to explore verified prices, floor plans, and offers. Buy your luxury apartment in Noida directly from the developer. More Info: https://www.atsgreens.com/

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

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

11. Create a 'cookbook' tutorial about adding 'Firebase Authentication' to 'Google AI Studio' apps

    Problem/Goal

    Developers using Google AI Studio to build custom AI applications (especially those moving beyond prototyping) need a straightforward, secure way to manage user accounts and access control. Integrating a robust authentication system like Firebase Authentication is the standard solution, but connecting it specifically to an AI Studio-powered backend or frontend can involve several tricky, undocumented steps.

    Suggested Feature/Content

    Create a "Cookbook" Tutorial (a detailed, step-by-step guide) that specifically focuses on the end-to-end implementation of Firebase Authentication for AI Studio applications.

    Key 'Recipes' (Sections) to Include

    Recipe 1: Firebase Project Setup

    Initialize a new Firebase project and enable a common authentication method (e.g., Email/Password or Google Sign-In).

    Securely store API keys and configuration settings.

    Recipe 2: Frontend Integration (Web/React)

    Implementing sign-up/login/logout UI components using the Firebase SDK.

    Managing the user's authentication state.

    Recipe 3: Secure AI Backend Communication

    The crucial step: Using the frontend's Firebase ID Token to make a secure, authenticated request to the backend (e.g., a Google Cloud Function or Cloud Run service hosting the AI Studio code).

    Verifying the ID Token on the backend to confirm the user's identity and grant access to the AI model call.

    Recipe 4: Role-Based Access Control (Optional)

    Adding custom claims to a Firebase user token to implement simple tiers (e.g., 'Free Tier' vs. 'Premium Tier' access to different models or rate limits).

    Expected Benefits

    Accelerates Development: Provides a "copy-and-paste" blueprint, lowering the barrier to entry for building production-ready, multi-user AI applications.

    Improves Security: Encourages developers to use best practices for token-based authentication from the start.

    Showcases Integration Power: Highlights the seamless connectivity between Google's developer tools (Firebase, AI Studio, Google Cloud).

    Problem/Goal

    Developers using Google AI Studio to build custom AI applications (especially those moving beyond prototyping) need a straightforward, secure way to manage user accounts and access control. Integrating a robust authentication system like Firebase Authentication is the standard solution, but connecting it specifically to an AI Studio-powered backend or frontend can involve several tricky, undocumented steps.

    Suggested Feature/Content

    Create a "Cookbook" Tutorial (a detailed, step-by-step guide) that specifically focuses on the end-to-end implementation of Firebase Authentication for AI Studio applications.

    Key 'Recipes' (Sections) to Include

    Recipe 1: Firebase Project Setup

    Initialize a new Firebase project and enable a common… 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  ·  Documentation  ·  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

12. Education

    Kakakheil-One

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

13. make linking console to studio a button, right

    that should be a done deal

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

15. Create documentation for the Docker image requirements for an App Hosting app deployed using Terraform

    Add documentation listing the Docker image requirements for an App Hosting app deployed using Terraform. Include sample Dockerfiles for Next and Angular apps.

    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  ·  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. App loan which enable user to actually publish apps so if the apps is good user pay back

    App loan

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

17. Firebase is garbage, unusable, and does not work for any actual coding

    I have been using Replit and Claude code for over 3000 hours. Firebase doesn't even come close to being able to develope any real code or functionality. Mistake after mistake, trial and error. If you really want to fix the issues, upvote this, then have google pay me for my feedback. otherwise enjoy the useless tool. going back to reality.... to develop real apps.

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

18. Ronaldo

    Ronaldo Cardoso dos Santos

    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

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

19. i need to launch app my new app to solve solutions to economy

    i think the app is helpful to economy

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

20. Data Connect should be serverless through and through.

    One of the great things about firebase is that it didn't burden you of your design decisions and let you pay for resources when you needed it. Serverless is one of the main selling point of firebase, you can see its footprints on firestore, realtimedb, and firebase functions.

    Seeing the need to instantiate a DB instance when getting started with data connect was so disappointing for me because I thought it was a step in the wrong direction.

    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  ·  SQL Connect (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