2357 results found

1. Integrate with Play Integrity Standard API

   Current Firebase App Check is using the classic play integrity API, which results in rate limit easily. As a result, the token decode will fail easily as the QPS limit by play integrity api. Why not migrate to the Standard Play Integrity API which suggested by Google Play?

   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

2. Download IPA/APK files from Download link on Desktop

   Allow users opening the Download link for a Firebase App Distribution Release to access and download the app file through desktop browsers instead of arbitrarily blocking it.

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

3. Critical Feedback: Reconsider the Sunsetting of Firebase Studio (Preserve the All-in-One Developer Experience)

   🌟 TO THE DEVELOPER COMMUNITY: If Firebase Studio is critical to your daily workflow across Web, Mobile, Backend, or ML, please click the VOTE at the top of this page to escalate this issue to the Google Product Team.

   To the Google & Firebase Product Teams,

   The recent announcement to sunset Firebase Studio on March 22, 2027, and transition users to Google AI Studio or Antigravity, has sparked deep concern across the global developer community.

   While we fully support Google’s vision for an AI-driven future, we strongly believe that deprecating Firebase Studio is a step backward for core developer productivity.

   Here is why Firebase Studio remains irreplaceable for the ecosystem:

   1. The "Single Pane of Glass" Ecosystem
      Firebase’s greatest triumph is unifying Web, Mobile (iOS/Android), Backend logic, and Databases (Firestore/Realtime DB) under one roof. Firebase Studio is the control center for this ecosystem. Forcing developers to migrate to general-purpose or AI-first platforms risks fragmenting a workflow that is currently seamless, intuitive, and frictionless.

   2. Not Every Project is an AI Project
      Millions of production applications rely on Firebase strictly for rock-solid core infrastructure: Authentication, CRUD operations, Push Notifications, and Cloud Functions. Developers building these foundational, data-driven applications need a dedicated, focused environment. Cluttering this experience with AI-centric interfaces we may not need will drastically reduce our efficiency.

   3. The Burden of Migration and Retraining
      Deprecating a central tool imposes a massive tax on developers, startups, and enterprises. Transitioning away from Firebase Studio means rebuilding established CI/CD pipelines, rewriting internal documentation, and retraining teams on unproven platforms (like Antigravity), pulling valuable time away from actual product development.

   4. The Core Identity of Firebase
      Firebase became the industry standard because it was the easiest, fastest way to go from a blank canvas to a scalable app. Firebase Studio embodies that "simplicity-first" philosophy. Removing it threatens to erode the very Developer Experience (DX) that made developers choose Google Cloud in the first place.

   Our Proposed Solutions:
   We respectfully urge the product team to consider the following alternatives before the 2027 deadline:

   Option A: Cancel the sunset and continue maintaining Firebase Studio as the dedicated hub for core backend/mobile/web infrastructure.

   Option B: Guarantee a dedicated, 1:1 "Firebase Classic Mode" within the new platforms that retains the exact simplicity and feature parity of the current Studio, completely isolated from AI noise.

   Please listen to the community that built its foundations on your platform. Protect the tools that help us build the modern digital world.

   SaveFirebaseStudio #Firebase #WebDev #MobileDev #Backend #GoogleCloud

   🌟 TO THE DEVELOPER COMMUNITY: If Firebase Studio is critical to your daily workflow across Web, Mobile, Backend, or ML, please click the VOTE at the top of this page to escalate this issue to the Google Product Team.

   To the Google & Firebase Product Teams,

   The recent announcement to sunset Firebase Studio on March 22, 2027, and transition users to Google AI Studio or Antigravity, has sparked deep concern across the global developer community.

   While we fully support Google’s vision for an AI-driven future, we strongly believe that deprecating Firebase Studio is a step backward for core developer productivity.

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

4. Web preview for Flutter apps in Firebase Studio should support stateful hot reload

   When I made a change to my Flutter code in Firebase Studio, the web preview perform a full reload - which loses the state of the app and takes multiple seconds.

   It would be good if it did (or had an option to do) a hot reload for the web preview, so that the state was maintained and the reload would be sub-second.

   5 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 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. Subject: Project IDX needs a "Mobile Companion Mode" like Replit App ​Hi IDX Team, ​I moved my project to IDX, but the mobile experience via

   Subject: Project IDX needs a "Mobile Companion Mode" like Replit App
   ​Hi IDX Team,
   ​I moved my project to IDX, but the mobile experience via browser is currently unusable (blocking me from using IDX on the go).
   ​My Use Case: I don't write code manually on mobile. I use the AI Agent (Gemini) to prompt changes, review the code diffs, and check the preview.
   ​The Problem: The current responsive web view is too cluttered. I cannot see the Chat, the Code, and the Terminal effectively on a phone screen. It's painful compared to the competition.
   ​The Feature Request: Please look at the Replit Mobile App. They have solved this perfectly by separating:
   ​AI Chat Tab: Full screen for prompting.
   ​Code Tab: For reviewing generated changes.
   ​Preview/Console Tab: For checking results.
   ​If IDX wants to be the best AI-first IDE, we need a "Mobile Agent Mode" or a native app that allows us to manage and prompt our workspace from a phone without the desktop UI clutter.

   Subject: Project IDX needs a "Mobile Companion Mode" like Replit App
   ​Hi IDX Team,
   ​I moved my project to IDX, but the mobile experience via browser is currently unusable (blocking me from using IDX on the go).
   ​My Use Case: I don't write code manually on mobile. I use the AI Agent (Gemini) to prompt changes, review the code diffs, and check the preview.
   ​The Problem: The current responsive web view is too cluttered. I cannot see the Chat, the Code, and the Terminal effectively on a phone screen. It's painful compared to the competition.
   ​The Feature Request: Please look… more

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Native support for RBAC (Role-Based Access Control)

   Native RBAC (Role-Based Access Control) management
   Currently, to manage roles (admin, editor, client), you have to use Custom Claims via the Admin SDK (Node.js) or store the roles in Firestore. This is cumbersome for a beginner.

   The improvement: Being able to define roles directly from the Firebase console and have them automatically appear in the request.auth object of Security Rules without additional code.

   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  ·  Authentication  ·  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. Raise the number of workspaces limit

   Hey Project IDX team,

   I don't want to have a limit of 2 workspaces in project IDX. Can you lift the limit of two workspaces to maybe 50-100? I want to draft a lot of flutter, angular, and react projects in project IDX. Thanks.

   • Dino
   159 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

   11 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. let developer enforce schema if wanted on the serverside

   provide an option for the developer enforce a schema in the firebase console. At least on the firestore enterprise edition. Mongo Atlas had this offering. rightnow, we are having to manage schema at the app level and then again at the cloudfunctions level. Making it hard to manage.

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

9. make firebase studio as fullstack developer which can create powerful apps with ai

   In firebase studio ai everybody can create fullstack apps with this ai

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Improve Firebase Auth integration with Server side rendering (Next.js)

    Hey, hi, I’m a Next.js developer, and the only problem I’m having with Firebase is with the Firebase Auth integration. I’d like to see improvements to the documentation for Next.js and its integration with server-side rendering. The problem I’ve encountered is that we need to save the token generated on the frontend to pass it to the backend. And the Next.js documentation recommends creating the token on the backend as “HttpOnly” for better security, but Firebase Auth doesn’t follow this pattern, and there isn’t much documentation about it or how Firebase handles cookie security.

    I hope Firebase will consider my feedback.

    Hey, hi, I’m a Next.js developer, and the only problem I’m having with Firebase is with the Firebase Auth integration. I’d like to see improvements to the documentation for Next.js and its integration with server-side rendering. The problem I’ve encountered is that we need to save the token generated on the frontend to pass it to the backend. And the Next.js documentation recommends creating the token on the backend as “HttpOnly” for better security, but Firebase Auth doesn’t follow this pattern, and there isn’t much documentation about it or how Firebase handles cookie security.

    I hope Firebase will consider my… 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  ·  Authentication  ·  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. Firebase studio built in mod assistant extension

    You guys are a since you guys are sunset firebase studio so please release the extension the Gemini AI assistant code that can work I can send photo and it is understanding and built-in mode there can I can code unlimited so other student I can learn and do my easily just normal your model not powerful one and

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

12. A Key Adjustment to Avoid Errors and Code Loss (Refactoring) in a Firebase Studio Project

    I've been developing a large-scale project using Firebase, still in the experimentation, testing, and evaluation phase of Firebase Studio's functionalities. However, I've observed that small changes made to specific parts of the project end up significantly impacting other areas that shouldn't be affected.

    This behavior creates insecurity in the development process, as minor adjustments end up compromising stable functionalities, even when there's no direct correlation between the modules.

    It's quite frustrating to see that, because of a minimal code flaw, the project can stop working completely—compromising months of work in a matter of seconds. As a safety measure, I've been making several duplications of the project to preserve functional versions. However, this quickly consumes all the contracted space and is not a sustainable solution.

    It would be extremely important to have a mechanism similar to a "restore point" or "rollback," allowing the project to revert to a previous stable state if a critical error occurs. This would guarantee greater security, control, and continuity in development, preventing isolated corrections from compromising the entire system.

    Therefore, I request an evaluation of the possibility of implementing a native internal restoration or versioning feature that protects projects against unexpected failures and minimizes impacts on the development environment.

    For example: when requesting AI to make a correction or adjustment to the code, a copy of the code would be created, the adjustment or implementation would be made, then the changes would be presented to the developer, and once the developer confirms, the functionality would be assigned to the original code, deleting the copy. If something goes wrong, the code would simply be deleted without altering the original structure, so as not to have to create copies of the project occupying server space.

    I've been developing a large-scale project using Firebase, still in the experimentation, testing, and evaluation phase of Firebase Studio's functionalities. However, I've observed that small changes made to specific parts of the project end up significantly impacting other areas that shouldn't be affected.

    This behavior creates insecurity in the development process, as minor adjustments end up compromising stable functionalities, even when there's no direct correlation between the modules.

    It's quite frustrating to see that, because of a minimal code flaw, the project can stop working completely—compromising months of work in a matter of seconds. As a safety measure, I've been… more

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Narottam
    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 Distribution  ·  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. Realtime database, change default tab order

    Reorder the tabs in Realtime DB to prioritize displaying the rules or a landing page before the data.

    New users and analytics management find that loading the Realtime Database section from the web console impacts bandwidth usage for reads. This behavior is not ideal and could be separated from the Realtime Database landing page, especially when editing or inspecting the rules, as it requires loading larger chunks of the database before the user switches tabs.

    13 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

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

15. Github auto feed to firebase conle backend

    After deployment in firebase studio, app hosting require backend to rollout. However GitHub has to feed firebase console the code in repo. That request is now done manually and can miss critical steps that lead to frustration

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

    I can give my voice over to control

    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

    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

18. Save files to local as zip file

    Please add a feature where we can download the files into a zip files from firebase studio

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

19. Feature Request: One-Click "Export to APK" in Firebase Studio for Educational Projects

    Hello Firebase Team,
    I am an 11-year-old developer building a child safety ecosystem. I use Firebase Studio (Cloud Workstations) because it’s powerful, but it has one big barrier for young students: The Terminal.
    To see my project on a real Android device, I have to use CLI commands, manage hosting, and use third-party wrappers. This is very difficult for 5th-grade students and beginners.
    My Proposal:
    Please add a simple button in the Firebase Studio interface (perhaps under the "Project" menu or a "Build" tab) called "Export as Android APK".
    How it should work:
    User clicks "Export as APK".
    Enters App Name and Package ID.
    Firebase builds the project in the cloud and provides a direct download link or a QR code for the phone.
    This would make Firebase the #1 tool for STEM education and help kids like me build tools for internet safety (like my project for blocking gambling and toxic content) much faster.
    Let's make mobile development accessible to everyone, regardless of their terminal skills!

    Hello Firebase Team,
    I am an 11-year-old developer building a child safety ecosystem. I use Firebase Studio (Cloud Workstations) because it’s powerful, but it has one big barrier for young students: The Terminal.
    To see my project on a real Android device, I have to use CLI commands, manage hosting, and use third-party wrappers. This is very difficult for 5th-grade students and beginners.
    My Proposal:
    Please add a simple button in the Firebase Studio interface (perhaps under the "Project" menu or a "Build" tab) called "Export as Android APK".
    How it should work:
    User clicks "Export as APK".
    Enters App… 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  ·  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

20. Missing Primitives: Transaction Awareness and Trusted Server Metadata in Security Rules

    Firestore Security Rules currently lack two capabilities that force developers to choose between security, performance, and maintainability.

    1. Lack of Transaction/Batch Awareness Rules cannot verify if a write is part of an atomic batch or transaction. This makes it impossible to enforce multi-document integrity constraints natively.

    The Fallout: Developers must either trust the client to perform all parts of an operation (unsafe) or move logic to Cloud Functions. This introduces latency and cold-starts, but more importantly, it fragments security logic. Concise, native rules bolster security because they are easier to audit and are implemented correctly more often than fragmented, multi-layered workarounds.

    1. No "Middle Ground" for Server-Side Operations Currently, a server must either use the Admin SDK (which results in a full administrative bypass of all rules) or Identity Platform to impersonate a user. There is no way for a server to provide "partial validation" for a request that must still remain failable if it violates standard Rule constraints.

    The Fallout: Current limitations incentivize the use of "shared secrets"—checking for specific plain text properties or "magic strings" within the document data to signal that a server has "blessed" the write. This pattern may be adopted because it is more efficient than the alternatives, but it is brittle and mimics security without the actual structural protection of the Rules engine.

    Use Case Examples
    Relational Integrity (The "Escrow" Logic): A Purchase document must be created if and only if the Product status is simultaneously updated to sold in the same atomic transaction.

    External Validation (The "Verified Invite"): A server validates a one-time invite code against a 3rd-party API and "stamps" the request as valid. The Rules then check this stamp alongside request.auth to ensure the user isn't on a blacklist. The server validates the code; the Rules validate the user.

    State Synchronization (The "Booking Lock"): A user booking a hotel room must create a Booking doc and update the Room availability timestamp in one batch. Without is_transaction, rules cannot prevent "orphaned" bookings.

    Requested Features
    request.is_transaction: A boolean allowing rules to reject non-atomic "partial" updates to sensitive multi-document states.

    request.auth.token.server_assertions: A way for the Admin SDK to attach non-forgeable, temporary metadata to a user-authed request. This allows the server to act as a co-validator without needing a full administrative bypass.

    Appendix: Proposed Rule Syntax Examples
    A. Multi-Document Invariants

    JavaScript
    // Ensure a product status isn't flipped without a corresponding purchase record
    match /products/{productId} {
    allow update: if request.resource.data.status == 'sold'
    && request.istransaction == true
    && existsAfter(/databases/$(database)/documents/purchases/$(request.auth.uid)$(productId));
    }
    B. Co-Validation (Failable Requests)

    JavaScript
    // Server verifies the invite, Rules verify the user identity and blacklist status
    match /workspaces/{workspaceId}/members/{memberId} {
    allow create: if request.auth.uid == memberId
    && request.auth.token.serverassertions.inviteverified == true
    && !get(/databases/$(database)/documents/blacklist/$(memberId)).exists();
    }
    Summary: Firestore needs a way to combine user auth with trusted server assertions and transaction visibility. Without these, secure patterns are significantly harder to implement than unsafe ones.

    Firestore Security Rules currently lack two capabilities that force developers to choose between security, performance, and maintainability.

    1. Lack of Transaction/Batch Awareness Rules cannot verify if a write is part of an atomic batch or transaction. This makes it impossible to enforce multi-document integrity constraints natively.

    The Fallout: Developers must either trust the client to perform all parts of an operation (unsafe) or move logic to Cloud Functions. This introduces latency and cold-starts, but more importantly, it fragments security logic. Concise, native rules bolster security because they are easier to audit and are implemented correctly more often than fragmented, multi-layered workarounds.

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