1236 results found
-
Add npm workspace support for monorepos
App Hosting already supports nx based monorepos, but it would be great to have basic npm workspace support. I tried to take the plunge and convert my repo to nx tooling but I failed spectacularly 🙂 npm workspaces are super simple to get started with and other than not being able to deploy to App Hosting, they haven't come up short for me in a way that would convince me to try nx again.
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
-
12 votes
-
12 votes
-
12 votes
-
Email OTP Verification Code
We should open a Firebase community discussion about Email OTP authentication.
Firebase currently does not support native email-based OTP login (only email link or password auth).
I want to build a passwordless system where:
- Users sign in with email only
- A one-time code (OTP) is sent to email
- No passwords are stored
- Same OTP flow is used for login, signup, and account actions
This would provide a simpler and more secure authentication method without requiring phone numbers or passwords.
11 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-nov2511 votes -
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…
11 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.
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 -
Firestore insights dashboard
Same dashboard in GCP as Firestore in datastore mode. Collection storage space usage, index size, data size, etc.
Also, for multi tenancy apps in both modes (using subcollections or multiple databases or also schemas in native mode would be nice to have) an API that can tell how much resources - space, reads, writes, etc. did each customer use, to be able to offer some kind of pay-as-you-go type of subscription.
11 votes -
Support "Continuing Uploads Across Process Restarts" on iOS
I work for a company that enable people to record sports using video and the storage footprint are often very huge (10GB+). While building an app for iOS, I notice that Firebase don't support continuing uploads across process restarts on iOS which is a major deal-breaker for continuing using Cloud Storage for Firebase.
I see support for this on Android and I will encourage you to add this to iOS in the future. Ref: https://firebase.google.com/docs/storage/android/upload-files#continuing_uploads_across_process_restarts11 votes -
Allow field selections in client sdk's
Let's say I have an orders collection where each document represents a customer order.
I would like to be able to fetch and listen to only the names and dates of all orders and not get the whole document.
This would speed up a lot queries where not all fields are required and save bandwidth for users.
Since selection is already present in some server side SDK's I wonder if this could be enabled with a somewhat manageable effort.
11 votes -
Allow Android/iOS apps to select dynamically which Firebase project should be used on startup
Some scenarios require dynamically switching from one Firebase project to another, including Analytics and Crashlytics, For example, switching from a Firebase project set up for a staging environment (which requires to collect Analytics and crashes) to another set up for a production environment.
There could be many solutions to this problem, such as having multiple plist/json files and switching them dynamically, or no longer requiring these files and simply using object instances that store the configuration (e.g., using the FirebaseOptions builder). The best solution should satisfy the scenario described above.
This idea comes from this issue https://github.com/firebase/firebase-android-sdk/issues/66
11 votes -
Get rid of the egress data transfer fee for Firebase Storage
Rework Firebase Storage pricing to compete with Cloudflare R2. Even if Firebase Storage has some unique features like Firebase security rules, this does not justify the egress cost.
11 votes
- Don't see your idea?