2258 results found

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

   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

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

   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

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

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

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

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

   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

   0 comments  ·  Firebase Studio  ·  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

6. As new user or y

   When we work with Gemini as new user using mobile,we have to access database console,first of all the naming to front end developement and backend should be clear as firebase front end console and for data base as backend firebase to distanguish between the two,and while working on gemini sholud have access to backend to work on in Ai as a layman,

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

7. Firebase storage rules: Support for multi-database lookup

   This is a documented limitation and as such not an idea, but putting it out here to see if it get vote-traction. See the warning at the bottom of the page here:

   https://firebase.google.com/docs/storage/security/rules-conditions

   As of Feb. 25. 2025 it says

   "Warning: Storage Rules can only access documents from the default Cloud Firestore database when multiple databases are active."

   We have a project where we're doing tenant partitioning in both Firestore and firebase storage. The primary reason for creating separate buckets and databases is to be able to have storage in different customer preferred regions, and to achieve other isolations which are beneficial (backup/restore recovery scenarios etc.).

   Most files in firebase storage are protected by security rules that look up a document from the firestore database and checks access using a fairly standard acl scheme.

   This does not work unfortunately in a multi-db setup, which prevent this type of acl based storage security rules.

   I've not found any workarounds except an approach there the storage object Ids are long unique Ids that can't be "guessed" or brute force generated to look up an object in storage, but this is not as clean as being able to explicitly check access rights (and other logic on top of that using the rules language).

   The fact that it works in single/default db makes it feel like a significant takeback that the security design has the by changed when introducing multiple databases to the project.

   I think this is a common case for solutions doing tenant separation where there is a need to have objects in storage protected by acls.

   This is a documented limitation and as such not an idea, but putting it out here to see if it get vote-traction. See the warning at the bottom of the page here:

   https://firebase.google.com/docs/storage/security/rules-conditions

   As of Feb. 25. 2025 it says

   "Warning: Storage Rules can only access documents from the default Cloud Firestore database when multiple databases are active."

   We have a project where we're doing tenant partitioning in both Firestore and firebase storage. The primary reason for creating separate buckets and databases is to be able to have storage in different customer preferred regions, and to achieve other isolations which… more

   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

   1 comment  ·  Cloud Storage 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. 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

   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

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

   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

10. Education

    Kakakheil-One

    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

    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

11. allow the bot to have global admin console privledges.

    The bot often has problems performing cli functions. Please allow it to autonomously approve api's, run commands, etc...just provide ui prompts for the user to decline the action if they feel the need.

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

12. make linking console to studio a button, right

    that should be a done deal

    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

    0 comments  ·  Firebase console  ·  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. Enhance Go Development Support for Integrated GUI Applications in Remote/Cloud IDEs

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

    To the Google Firebase/Cloud Platform Team,

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

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

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

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

    1. The Technical Limitation: The Headless Barrier

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

    The Issue Encountered (Proof of Concept Failure):

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

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

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

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

    1. Impact and Value Proposition

    This limitation creates a significant friction point for Go developers:

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

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

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

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

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

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

    Primary Feature Ask: Virtual Display and Streaming

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

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

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

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

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

    Minimum Requirement: Clear Guidance and Pre-configuration

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

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

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

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

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

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

    To the Google Firebase/Cloud Platform Team,

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

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

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

    The ability to rapidly prototype,… more

    1 vote

    Vote Vote Vote

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

14. Clear parts of context

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

    5 votes

    Vote Vote Vote

    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. Enhanced Git Branch Integration in Prototyping View

    Hello Firebase Team,

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

    My suggestion consists of two parts:

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

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

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

    Hello Firebase Team,

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

    My suggestion consists of two parts:

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

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

    Implementing this would streamline the… more

    2 votes

    Vote Vote Vote

    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

16. I would love this to be a loveable.dev but on steroids. Connecting fully and easily with all the databases and backend software google has

    I would love for the studio to allow for prompt engineering all the backend. Similar to lovable with supabase but ideally prompt to connect to all the amazing services google has!

    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

17. Hire a real vibe coder

    Hire a real user like me with 3000 hours of experience in developing on multiple ai coding platforms. Firebase is garbage right now. I tried to create a simple app and it failed miserably. Are you guys going for a very long road to get there or do you want to surpass your competitors right now?

    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

    0 comments  ·  Firebase Studio  ·  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. 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.

    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

    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

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

    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

20. Get back to the previous versions at any point of time.

    This is crucial yet important feature, firebase should have. To get back to the old versions. As i experienced my project broke completely, and now i have no option to just go back 2 prompts up and fix it as it was.

    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