1244 results found
-
13 votes
-
In-place Firestore Standard → Enterprise migration
Description:
Add an in-place upgrade from Firestore Standard to Enterprise edition — a single button in the console (or a
gcloudflag) that converts our existing database, with no downtime and no application code changes.Today there's no in-place path. The edition is fixed at creation, so the only route is to provision a new Enterprise database and copy data over via export/import or the Dataflow
firestore-to-firestoretemplate. The problems:- It's a point-in-time copy, not a live cutover — so there's effective downtime unless we build our own dual-write/backfill.
- Only documents move; indexes, TTL policies, and other settings must be…
12 votes -
Table Event Triggers
In additional to the
onMutationExecuted, we would love to have events on table mutations.onRowUpdatedonRowCreatedonRowDeleted
onMutationExecutedis already launched in Nov 2026. https://firebase.blog/posts/2025/11/dataconnect-nov2512 votes -
publish a GCP / firebase documentation MCP server
Enable fetch and query tools in an MCP server for the whole GCP, or the firebase documentation.
12 votes -
Supabase intergation
Linking supabase into Firebase like a MCP server
12 votes -
Download ipa/apk files on Desktop
Allow a Download link for a build uploaded to Firebase App Distribution to be opened and the file downloaded on a desktop machine instead of only mobile devices, allowing the sharing of apps with third parties that cannot access email or google accounts on the target devices. It's the same basic functionality that already exists, simply allowed on desktop as well instead of arbitrarily blocked.
Given the nearly ubiquitous presence of this as an option with other app distributors, it's somewhat shocking this wasn't already an option.
12 votes -
Add support for Google Play "automatic protection"
Currently, manual steps on the play store developer console is required to create an application that has Play Store "automatic protection" enabled:
https://support.google.com/googleplay/android-developer/answer/10183279We have found that "automatic protection" is error-prone in multi-process applications and applications that include native libraries/code. It would be really helpful to our manual QA process to be able to programmatically distribute applications with "automatic protection" enabled on them.
12 votes -
GitLab support for Firebase App Hosting
We (and I'm sure many others) have large data repositories in GitLab using its CI system, and for technical and political reasons, we do not plan to migrate to any other code repository.
Firebase App Hosting seems to be tightly integrated with GitHub only. Extending its support to GitLab (or other Git repositories) would greatly help with adoption, even if it requires manual CI configuration.
12 votes -
custom remote git support
Support for self hosted gitlab or other git remote sources
12 votes -
Turning Off Auto Login when creating New User
The Firebase createUserWithEmailAndPassword function currently auto-logs in the newly created user. However, it's crucial to have an option to turn off auto-login, especially in admin panel scenarios. This can help prevent issues where the admin session expires due to the new user login. Providing such an option will enhance flexibility and control in user management.
12 votes -
The ability too see when an index was last accessed
When a project grows to a certain size, you'll likely have many indexes with associated queries.
However, queries change, or get removed, and currently there's no way to see if an index could be safely removed, after a query is; which would be a great feature.
12 votes -
TTL for Realtime DB
Realtime DB is very similar to Redis functionality. It would be very valuable to enable real caching behaviour by adding time to live to an entry.
12 votes -
12 votes
Anonymous responded
-
12 votes
-
12 votes
-
Evaluate Mutation Results in Realtime Refresh Conditions & Support Mutation-Side Triggers
Currently, when configuring a refresh condition on a query, the condition can only evaluate the triggering mutation's variables and auth (uid/token). We cannot check the actual result (response) of the mutation.
This creates a significant friction point when mutations are executed from non-client environments, such as a Cloud Function triggered by another backend service (e.g., Firebase Storage). Because the Cloud Function executes without the end-user's auth context, the only way to accurately filter the query refresh is to pass the userId into the mutation's variables. This feels like an unnecessary workaround just to satisfy the refresh condition.
To make real-time…
11 votes -
Firebase Payments SDK — A Unified, Platform-Agnostic Payment Service for Firebase
I'd like to submit a feature request for a first-party payment service within the Firebase ecosystem — tentatively called Firebase Payments.
The Problem
Firebase does an excellent job abstracting away common backend concerns — authentication, real-time databases, cloud functions, push notifications, and hosting. However, one critical backend responsibility remains entirely unaddressed: payment processing and subscription management.
Today, developers who build on Firebase must wire together third-party providers (Stripe, Razorpay, Paddle, etc.) manually, manage webhooks, store transaction state in Firestore themselves, and handle currency normalization independently across regions. This introduces significant complexity, maintenance overhead, and security surface area — all of…
11 votes -
Autofill suggested indexes from query insights
With the legacy firestore any complex query required indexing to be able to get the documents, nowadays with firestore entreprise that is not require but still the optimization is required for large collections and aggregation queries. The new query insights help you keep track of the performance and can list each query, but unlike legacy firestore they require you to manually set the details of any new index even if the modal opens from a specific query (It seems like an incomplete ux). Being able to perform this tedious task with the click of a button will be amazing.
About…
11 votes -
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?
11 votes -
Android Studio Robo Script Recorder should support Jetpack Compose
With Android Jetpack Compose becomes more and more popular, it is pretty sad to see that Android Studio Robo Script recorder doesn't support Compose screen. Even though robo script support compose but it is very time consuming to generate robo script manually for every Jetpack Compose screen. What makes it even harder is that app crawler is no longer support testing generated robo script locally.
11 votes
- Don't see your idea?