546 results found
-
A SQL based database
Currently Firebase supports JSON & NoSQL Datastore which is a cool thing, but what is currently a pain point is that for building more complex apps with a lot of linked data is such an hassle with NoSQL Databases.
This is one reason people are pivoting from Firebase for anything long term, if there is a way to host relational data like a SQL instance (Postgres/MySQL) it will make firebase an Ideal solution for apps of any scale.
I would also happy to share some of the case studies of business which are looking forward to this specific thing.
36 votes -
Setting to disable returning auth error type
Currently errors such as "wrong password", "user with this email doesn't exists" etc are always returned to client. Would be nice to have the option to only return a generic error message to improve security.
3 votes -
Support deployment of Nuxt 3 projects to Hosting
Currently, support for Web Frameworks (Beta) only supports Next.js and Angular: https://firebase.google.com/docs/hosting/frameworks/frameworks-overview. Nuxt is labeled as 'Soon' at https://github.com/FirebaseExtended/firebase-framework-tools
I just wanted to cast my vote for Nuxt 3 support and try out the new portal :) Thanks!
5 votes -
Trusted headers for client IP address via Firebase Hosting
Context: from a backend running on Cloud Run/Cloud Functions, how to determine client IP address, when you need to TRUST it for IP-address based access restrictions.
You can normally find the real client IP as the first entry in the X-Forwarded-For header, but you cannot trust it.
If you are using Cloud Run (or Cloud Functions gen 2), then as far as I can tell the Cloud Run orchestrator always sits as a proxy in front of your container. This means you can trust the last entry in X-Forwarded-For as this is the client IP seen by Cloud Run itself.…
3 votes -
Separate/standalone Authentication admin library
Quite often I only need the firebase-admin/auth part of the NodeJS admin library. Especially when separating the application into single-purpose containers/microservices.
However because there is no separate NPM package for the auth part, I need to pull in the entire firebase-admin package, which pulls in a HUGE number of dependencies like @google-cloud/firestore @google-cloud/storage, google-gax, @grpc/grpc-js protobufjs and a multitude of others which are not needed for the auth part.
Much of the other components like Firestore, Storage etc can be used directly from the @google-cloud/... libraries without the entire firebase-admin package.
But there is no separate package for Authentication.
Authentication…
3 votes -
Analytics - Buggy engagement times when doing manual screenview tracking
Not really a feature request, but a pretty old bug which makes analyzing user engagement impossible.
When disabling automatic screen tracking via "googleanalyticsautomaticscreenreportingenabled" and doing it manually via SCREENVIEW events, engagement times are logged completely wrong.
Engagement time is wrong by a factor of 10 compared to our ios apps.Find more details in the following bug-report:
https://github.com/firebase/firebase-android-sdk/issues/32404 votes -
Custom App Preview Page for dynamic links
Use customized website for app preview page. This will also us to keeop our marketing brand and tone consistent
4 votes -
Allow URLs to be accessible fully, or by invitation, or by password protection, like Notion and Figma
Allow natively what we can do in Notion / Figma (sharing a prototype), by sharing a page with the followings options:
1/ allow a page to be fully accessible (that's already possible, so the default)
2/ allow a page to be viewed only if we provide another User a link.
3/ allow a page to be viewed if 2/ + password protected10 votes -
Firestore indexes in emulator
Currently, the Firestore emulator allows all queries without checking if the query requires an index. It would be great if the emulator checks the Firestore indexes file if the index exists.
103 votes -
MLKit support for Apple Silicon
It's been 2 years that we can't test our app on Apple Silicon (M1/M2 processor) with emulator (see: https://issuetracker.google.com/issues/178965151).
It force us to run our tests & deploy on old machine, witch is quite annoying.
3 votes -
Add an option to host cloud function free of cost
We all knoow cloud functions are not free now. But it would be great if you kindly allow upto 3 cloud functions without all the expensive apis like cloud vision etc.
4 votes -
Update Linked Documents
If you have split your data in several collections there should be an easy way to update a linked document - for example if the user changes his name, all articles with the authorId = userId should be updated automatically
7 votes -
Google Play User Data Delete Requirement
Google requires a web link that enables users to delete all their data, even after they have uninstalled the application. For a "serverless" app that only uses Firebase Auth, it would be ideal to have a plug-and-play solution for hosting a single webpage that complies with Google Play's policy.
8 votes -
Allow SMS customization & add Web OTP support
Web OTP support increased phone authorization conversion significantly.
Currently, We are not able to customize SMS messages to comply
https://developer.chrome.com/en/articles/web-otp/#format38 votes -
Better support for Cloud Tasks, e.g. queues
It is currently already possible to create google cloud tasks. However, this could be better integrated by creating an abstraction for queues, for example, which can also be monitored and controlled via the admin console and firebase emulator.
26 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.
11 votes -
Integrate googles BART AI as well into this project.
Googles BART could be used the same way “Bing Pages” for business are allowing people to say 54 phrases to ultimately be used to talk to potential customers or people looking at that businesses page.
5 votes -
A "--no-document-updates" flag for Firestore import
It has happened to me that I accidentally deleted some documents. While you can restore a collection from a backup, there is no option to not overwrite existing data.
This unfortunately makes it impossible to restore accidentally deleted documents, without also affecting other documents that have changed since you last made that backup. The restore would undo lots of changes that happened after the backup was made.
I think a very effective and simple solution could be to allow only injecting those documents from the backup that do not exist in de target collection. So no document is ever overwritten/updated…
3 votes -
18 votes
-
DocumentReference join query
Please add a join query to Cloud Firestore. It seems that using DocumentReference for the join would be appropriate.
24 votes
- Don't see your idea?