1485 results found
-
264 votes
Hi folks, this is being actively worked on, and is expected to preview sometime in H1 2024. Thank you for using UserVoice to help us prioritize!
-
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
10 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
21 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
3 votes -
Edge Runtime for functions
Bring in Edge Runtime for functions to perform high performance tasks in the edge cloud for faster responses.
19 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 -
Add API to make it easy to build rate limiting in HTTPS functions
It would be awesome with some kind of helper built on memcache to allow rate limiting on user defined parameters.
E.g. if I build a webservice that can access an 'account' concept that I have modelled with some kind of access token I have modelled, then it would be nice to add rate limiting rules for either the specific access token or the entire account.
13 votes -
Persisted indexes in the Realtime Database
The indexes in the Realtime Database are created in-memory and on-the-fly - and they are 'garbage collected' when memory is needed for something else.
This makes it expensive (meaning high CPU usage, not costly) to query large collections of data in the Realtime Database.
Collections can also become so large that they are not queryable through the SDKs, but only using the firebase cli tool. One hope would be that with an actual persisted index, it would always be possible to iterate through a collection of nodes, no matter the number of nodes in the collection.
3 votes -
Support array-contains-prefix operator in Firestore
You can build a search index in a Firestore collection by storing an array of search words.
If you query this property using 'array_contains' you get exact matches for your search string.
If you wish to build a prefix search, then you potentially need to store all prefixes of the words you need to index.Assuming that the array-contains is performing some kind of index scan, it would appear that it was possible to create an array-contains-prefix such that:
where('index', 'array-contains-prefix', 'fire')
would match the following documents[
{ index: ["firestore", "database"],
...
},
{ index: ["firebase", "dog"],
...
}…
6 votes -
Add event ids for browser viewing into Crashlytics BigQuery tables
I had trouble with finding a specific crash event in the group of crashes. BigQuery gave me an event_id, but I was not able to use this id in the URL query param to open a specific crash in browser. Browser event ids and bigquery event ids are different. Not sure if I’ll need it in the future again, but it was a bit annoying to get all the threads and stacktraces from bigquery
2 votes -
62 votes
-
Support for Jetpack Compose in Analytics and PerfMon
Right now, there is no support for Jetpack Compose. If you have a single Activity and use composables to navigate through your app, without custom events, nothing is really tracked. So the request add navigate support for screen views based on composables like we have for Activities and Fragments.
9 votes -
Support Swift in Cloud Functions
Swift is a much beloved and popular language for writing apps on the Apple platforms, but increasingly, it is also being used server side and even for writing cross platform business logic on Android and on Windows.
Being able to share models and business logic between your clients and server would be an amazing productivity boost. And being able to develop in a language that focuses on safety would eliminate categories of issues that can exist if you develop in say Javascript or Typescript.
322 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
8 votes -
Firebase SDK for compose-multiplatform that can support Android, iOS, Web and Desktop
As compose-multiplatform now supports iOS app development hence compose may see a very good in-take by the developers in the near future. The way Firebase Flutter SDK got introduced in a similar way if SDK for compose-multiplatform can be introduced for the developers then it will be super beneficial for them.
6 votes
- Don't see your idea?