2134 results found
-
Support for WebAssembly in Cloud Functions
Many languages requested in other posts—Swift, Rust, Kotlin, etc.—can be implemented all at once by adding WebAssembly (WASM) and WebAssembly System Interface (WASI) to the list of Cloud Functions’s supported runtimes (and—importantly—supplying high-quality documentation).
4 votes -
3 votes
-
App Check for Java Admin SDK
Verifying requests with Java Admin SDK would be very helpful for many servers using this language.
5 votes -
Allow updating multiple documents through a query
Many other databases have support for update queries, such as:
- Apply "x" update data to all docs matching "y" query
- Delete all docs matching "x" query
Maybe these queries would only count as 1 write per doc, as opposed to 1 read + 1 write. At the very least they would have better performance.
18 votes -
FieldValue.min() and FieldValue.max()
Currently the Firestore API supports FieldValue.increment() to atomically increment or decrement a numeric value. I propose to add:
FieldValue.max(value): if the provided value is greater than the existing value on the server, then the field on the server takes this value. If it is less than the existing value, then the existing value remains.
FieldValue.min(value): (the opposite) if the provided value is less than the existing value on the server, then the field on the server takes this value. If it is greater than the existing value, then the existing value remains.
These operators should work on numeric fields AND…
21 votes -
Wildcard index exemptions
Firestore automatically indexes all fields in all collections adding to storage size and slowing write performance.
We can add single-field exemptions but we need to list all fields separately and there is a database-wide limit of 200 field exemptions.
In a highly optimised use case we would want to index only specific fields that we know we query on, and just exclude all others.
It's almost like the current behaviour is a database for novices, but we can't optimise for serious production.
We need either a wildcard exclusion, or effectively just a switch/setting that says "only fields with explicit index…
6 votes -
Firebase SDK support for Cloudflare workers
Make a Firebase SDK compatible with [Cloudflare Workers][cw] so that it is possible to use Firebase Authentication and Firestore with ease.
12 votes -
Custom Claims Editor
Show Custom Claims and allow them to be managed in the Firebase Authentication Console (like in the Emulator). Usefull for manually creating the first super user, for example.
38 votes -
Allow input of analytics label on in-app messages like push notifications
Push notifications allow for an analytics label which makes sense for marketers who are running multi channel campaigns and want to aggregate results.
There is currently no way to add these to in app messages. Goal would be they are treated the same way as push notifications with simple reporting and pull through on the analytics for custom report building. Thanks
5 votes -
303 votes
-
A/B testing and Conditional Rollout on event params
Currently, Firebase allows A/B testing to be created on the remote config parameter with the optimization metric on any event being fired on the Firebase Analytics. Unfortunately, it does not allow the metric to be one of the event_params sent on that event. This limits us in running refined experiments on certain attributes.
Secondly, A/B testing and conditional rollout do not allow the creation of refined conditions on the basis of event parameters. This limits further in creating rolling out a feature in controlled manner
4 votes -
View custom domain setup DNS configurations
After a Custom Domain is set up on a site, there's no way to view what the correct DNS records should be.
4 votes -
2 votes
-
4 votes
-
X-User-Country header when proxying to Google Cloud Run
App Engine and Cloud Functions send X-AppEngine-Country to app servers, which is useful for serving regional content to users.
Google Cloud Run doesn't receive the same headers. GCR can receive this header through load balancer custom headers (https://cloud.google.com/load-balancing/docs/https/custom-headers), but it'd be great if it were supported through Firebase Hosting directly without any extra configurations.
5 votes -
Restrict Unauthenticated PURGE requests
At the moment Hosting is using Varnish cache which developers do not have access so they can't configure it, this leaves a small window for people to continuously Purge the page and increase the developer's usage
15 votes -
Support monorepo
Firebase functions does not support monorepo structures (NPM monorepo, NX, Turborepo) during deployment.
Firebase uses custom archive logic for functions packaging (https://github.com/firebase/firebase-tools/blob/127ca3fbf7549d6c0cdf12e89e4465de9dd2b7c9/src/deploy/functions/prepareFunctionsUpload.ts), which does not support internal packages deployment out of the box.
Github discussion: https://github.com/firebase/firebase-tools/issues/653
28 votes -
CI & CD for deployments
Git based CI & CD auto deployments would really be a game changer, it can be integrated to things like cloud run and enable this. Half the time I use tools like vercel and netlify because of lack of auto deployments in firebase
4 votes -
Edge Runtime for functions
Bring in Edge Runtime for functions to perform high performance tasks in the edge cloud for faster responses.
20 votes -
Biométrics reader
You install your program application and once you install it you turn your biometrics reader and so it performs your eyes scans. Once done so it will detect your presence, will know you by your eyes and of course a fingerprint scans will be done as well. So you turn it on then all you do is read a book for example and the program will be sensorineural and so whatever you read on your screen it will detects what your eyes are seeing actually and so the system will detect your readings and read them out loud to you.
2 votes
- Don't see your idea?