2335 results found

1. Bulk Topic Subscription Operations

   In some apps, it is desirable for a user to subscribe to multiple topics by default, and it also is desireable to allow users to subscribe to/unsubscribe from many topics at once. For example, "I want all/no weather notifications" may entail subscribing/unsubscribing to "thunderstorm-warnings", "thunderstorm-watches", "tornados-warnings", "tornado-watches", etc, for all the topics of that type in your app.

   Currently, you have to make one API call for each of these. This is very slow, has unnecessary network overhead, and complicates calling code.

   My proposed feature: add "subscribeToTopics" and "unsubscribeFromTopics" methods to the SDKs. The signature would be (depedning on the language): (topics: Array<string>) => Promise<void> and would subscribe to/unsubscribe from the passed topics in one call.

   In some apps, it is desirable for a user to subscribe to multiple topics by default, and it also is desireable to allow users to subscribe to/unsubscribe from many topics at once. For example, "I want all/no weather notifications" may entail subscribing/unsubscribing to "thunderstorm-warnings", "thunderstorm-watches", "tornados-warnings", "tornado-watches", etc, for all the topics of that type in your app.

   Currently, you have to make one API call for each of these. This is very slow, has unnecessary network overhead, and complicates calling code.

   My proposed feature: add "subscribeToTopics" and "unsubscribeFromTopics" methods to the SDKs. The signature would be (depedning on the… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Cloud Messaging  ·  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. Proposal for long term, low footprint (minimize tokens) written memory of conversations, tasks and goals.

   I propose a long term feature that allows users to enable an auto-management of a "diary" that logs session activities and summarizes as you use studio.

   There is the short term and long term aspect of this feature. During the current session, since its ephemeral, when major conversation topic shifts or efforts shift, we notate that in the short term memory; every time we reload a new session, we review the past short term, summarize/compress , and add it to our long term "memory" or diary. Then we start fresh for the day, with some context of the past efforts. And if there was an active goal or task at hand, we can have that marked as the "current topic" or maybe track a few topics at the same time. The goal is to have a low footprint, writte, non-ephemeral diary, connected to your workspace and project, that will keep a log/diary of your events in a simple way that mimics long term understanding of the goal of the user without parsing through logs and logs of data, files and files of the project, or volumes of markdown documentation, just to work on your project.

   The expected results will be that everytime Firebase studio crashes, or we reconnect, gemini prototyper, or gemini CLI, or even Gemini Code Assist, can read this diary and quickly be up to speed on the project definition, project goals, status and most recent conversation/tasks --- AND --- uses the most minimal amount of tokens needed to process the next set of queries and conversations.

   I propose a long term feature that allows users to enable an auto-management of a "diary" that logs session activities and summarizes as you use studio.

   There is the short term and long term aspect of this feature. During the current session, since its ephemeral, when major conversation topic shifts or efforts shift, we notate that in the short term memory; every time we reload a new session, we review the past short term, summarize/compress , and add it to our long term "memory" or diary. Then we start fresh for the day, with some context of the past efforts.… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

   🧠 Core Strategy

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

   2. Integrate with Firebase Emulator Suite + Edge Cache

   3. Enable automatic sync with Firebase Cloud

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

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

   ---

   ✅ Key Benefits Overview

   Feature Benefit

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

   ---

   ⚙️ Recommended Components

   Component Purpose

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

   ---

   💡 Real-World Use Cases & Advantages

   🛍️ Point-of-Sale (POS) App

   Works offline in restaurants or kiosks

   Syncs sales data to Firebase Cloud when online

   Supports local printers and receipt scanners directly

   🛡️ Security or IoT System

   Sensors log data to local Firestore (offline)

   No internet needed for core functionality

   Syncs logs or events to Firebase Cloud daily

   🏫 Education System / LMS

   Operates in classrooms without stable WiFi

   Tracks student progress locally

   Syncs to cloud at home or when reconnected

   ---

   🔧 Bonus Features (Optional Add-ons)

   Add-on Description

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

   ---

   🔥 Summary

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

   🧠 Core Strategy

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

   2. Integrate with Firebase Emulator Suite + Edge Cache

   3. Enable automatic sync with Firebase Cloud

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

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

   ---

   ✅ Key Benefits Overview

   Feature Benefit

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

   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  ·  Cloud Functions for Firebase  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Allow to convert a Set() to a List() in the Firestore rules

   There is a very annoying limitation in the Firestore rules: you cannot convert a Set() to a List().

   This prevents a lot of possibility especially when using Map().diff().affectedKeys(): there is no way to access the first element for example.

   My use case is the following:
   On my client side, I am incrementing the value of a map element, ie:
   MapFieldValue resources;
   resources["gold"] = FieldValue::Increment(-amount);

   And on the rules side, I want to ensure that the resulting value is always positive (ie you cannot spend more gold than you have, even concurrently!):

   let updatedKeys = (resource.data.diff(request.resource.data).affectedKeys());
   return (updatedKeys.size() == 1 && request.resource.data[updatedKeys.toList()[0]] >= 0);

   But without the "toList()" function, I cannot get the value of the updated key in the Map. There is no way to access a Set() element other than by knowing the key.

   My actual workaround is to set a "temporary" String field in the request with the value of the updated key, but this is more a "hack"...

   There is a very annoying limitation in the Firestore rules: you cannot convert a Set() to a List().

   This prevents a lot of possibility especially when using Map().diff().affectedKeys(): there is no way to access the first element for example.

   My use case is the following:
   On my client side, I am incrementing the value of a map element, ie:
   MapFieldValue resources;
   resources["gold"] = FieldValue::Increment(-amount);

   And on the rules side, I want to ensure that the resulting value is always positive (ie you cannot spend more gold than you have, even concurrently!):

   let updatedKeys = (resource.data.diff(request.resource.data).affectedKeys());
   return (updatedKeys.size() == 1 &&… 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  ·  Firestore  ·  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

5. Firebase Should Work With Kotlin Multiplatform

   KMP is now getting stable and the Firebase should be able to be used in these projects

   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  ·  SDKs  ·  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. Superior Version

   I propose creating a "Superior Paid Option" that would provide subscribers with technical developer assistance in situations where the built-in LLM is not capable of overcoming complex tasks. It could be a simple Chat Option, but at the very least, an email option to allow creative people with great ideas (but lack the technical ability) to flourish. The "Paid Option" could also provide for better LLM options and can go towards more dedicated software improvements to make this application "Ultra" amazing!

   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

7. please back the android studio cloud option

   the option cloud android studio project it is very helpfull even we use it for many purpose please i request google to back it please

   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

8. Able to drop more from templates

   Able to post more projects

   15 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

9. Tại sao hệ thống aI nguồn gốc tạo ra 1 thế hệ phát phiển bẳng cách nào

   AI

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

10. 제발 오류 조치 좀 해줘요

    잘 돌아가던게 어느 순간부터, 꼬이기 시작해서 동일 오류를 계속 반복적으로 조치를 못하고 개발 포기 상태까지 입니다, 운영에 배포한 것인데, 벌써 2주일째 오류 해결을 못하고 있어요,
    https://console.firebase.google.com/project/juseomjuseom-02131985-1d311
    -> API 키 관련사항인 둣 하는데,,

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

11. meraestore

    Aap store Play store Google service Google product

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

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

13. Separate windows and agents for different concerns : ASK, DEVELOP and EXECUTE

    Should have 4 different modes ASK, Develop, Commit and Execute each having different color windows. And all 4 should be working simultaneously. And i should be able to use what ever model i want in each of them.

    And what should happen should also be very clear in each of those categories.

    Ask (General Agent) means no code development, just planning, and asking on anything and everything.

    Develop means code will be created, but user has to approve it. And the Studio should be aware of what fragment or portion of the code got approval or none of it.

    Execute(Agent + Run currently) agent for making changes without approval.

    Commit agent for carrying out regular commit tasks to the github without much ceremony.

    Right now we have 3 modes, but the modes dont have a boundary or definition which is 100% solid. Ask tries to develop and develop tries to execute. And it does not even know whether its suggestions got approved or not, just assumes that they all did.

    Similarly there should be CI/CD agent/window.

    And then there should be a SDLC agent/window where I can do project management decision.

    The purpose of each should be very well defined with proper system level prompts by Firebase studio itself. To minimize hallucinations.

    Allow people do open more than one chats simultaneously if they are developing 2 or more features at the same time.

    You can have an orchestrator agent which can call all these agents to do this and respective updates in their chat windows. if some poeple will find it too many agents to deal with.

    further a QA agent mode would be also useful .

    But real devs want certainity and not playing with Fire.

    Should have 4 different modes ASK, Develop, Commit and Execute each having different color windows. And all 4 should be working simultaneously. And i should be able to use what ever model i want in each of them.

    And what should happen should also be very clear in each of those categories.

    Ask (General Agent) means no code development, just planning, and asking on anything and everything.

    Develop means code will be created, but user has to approve it. And the Studio should be aware of what fragment or portion of the code got approval or none of it.

    Execute(Agent… 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

14. تصميم تطبيق فيه جميع خدمات تواصل اجتماعي

    Story Water

    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

    3 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

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

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

16. AdMob

    (Google Ads Display & Video 360)

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

17. crownedsupremetriple777@gmail.com

    Gmail app

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

    I am app developer my name shubham

    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  ·  Other  ·  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. Japanese IME Enter key submits messages during composition in Firebase Studio

    When typing messages in Gemini within Firebase Studio with a Japanese IME enabled,
    the Enter key pressed during text composition is incorrectly handled as message submission,
    which frequently causes accidental sends.

    While composing text, the Enter key should be used only to confirm conversion
    and must not trigger message submission.
    Please align this behavior with that of other common services.

    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