741 results found
-
Realtime Query Updates
Subscribe to realtime updates for a limited subset of queries, for example retrieving updates to specific rows or getting new items for a simple timeline.
269 votes -
Add GraphQL enum support
Add support for the GraphQL enum type in @table types.
46 votes -
Event Triggers
Trigger a Cloud Function when data in a table type is created (via insert or upsert), updated (via update or upsert), or deleted.
170 votes -
Firebase-UI Support
The firebase-ui https://github.com/firebase/firebaseui-web seems to no longer be supported. It currently doesn't support the latest firebase versions: https://github.com/firebase/firebaseui-web/issues/1107
35 votes -
Cloud Firestore Datasource
Support Cloud Firestore as a datasource for Data Connect in addition to Cloud SQL. Support data model mapping (e.g.
@collection) and querying via GraphQL126 votes -
Offline Support
Allow data to be cached and accessible offline. Offline data may have limited query and write capabilities compared to online data
110 votes -
SQL Full-Text Search
Index and query your data with full-text search leveraging PostgreSQL's built-in capabilities including stemming, ignoring stop words, and weighted relevance scoring.
113 votes -
Add devices running iOS 17 and 18 in Test Lab
The newest iPhone model and iOS version available to run in Test Lab is an iPhone 14 Pro running iOS 16.6. With iOS 18 recently released, it would be great to have support for newer devices (iPhone 15 and 16 models) running the newest iOS versions (17.x and 18.x).
37 votes -
Automatic Deployment of Changed Firebase Functions
Firebase should offer a built-in feature to automatically detect changes to Cloud Functions and deploy only those functions, grouped into manageable batches to avoid rate limits. This feature would streamline deployments by:
- Scanning the project directory to identify functions with modified code since the last deployment.
- Automatically batching the deployment of changed functions based on rate limit thresholds (e.g., 8-10 functions per batch).
- Handling the deployment process transparently within the Firebase CLI or CI/CD integrations, reducing manual intervention.
This functionality would save time, minimize deployment errors, and improve developer workflows, particularly in large projects with numerous functions.
22 votes -
App Distribution should have at least basic management of email notifications
There is no option to set email preferences for tester groups in Firebase App Distribution. It is unnecessary to pester everyone with emails when they can find the last app version in App Tester.
10 votes -
Support Public distribution group to allow user to install app on their device without authentication
However, Firebase lacks the feature to share debug builds with a public distribution group, like Microsoft AppCenter offers, without adding testers. Sharing public link users should be able to install on their devices without authentication.
16 votes -
Support Dart in Cloud Functions
Dart is not currently supported in Cloud Functions, so developers need to use more than one language in their code base. Here are some pain points they shared with the Firebase product team about this gap:
- They need to learn another language, and many of them do not have the same expertise in JavaScript as they do in Dart.
- The lack of features and tools, such as Hot Reload and Hot Restart, impacts development speed.
- Developers cannot share business logic and data models across the entire stack.
- Developers cannot use frequently used Dart packages on the…805 votes -
Firebase Authentication Setup API
I'm running the Web/APP builder platform using user's own Firebase. However, when user is creating platform through my service, Authentication setup API is limited to Blaze plans users.
Please provide the Authentication Setup API also for Spark Plan user.
Spark Plan user is highly possible to be the Blaze plan user in the future if Firebase provide a contentable user's experience.35 votes -
Firebase Storage Setup API Issue
I'm running the Web/APP builder platform using user's own Firebase. However, when user is creating platform through my service, Storage setup API is limited to existing users who have previously set up Cloud Storage. I have discovered that the existed Storage Setup API is available for both Spark and Blaze plans but not for new Firebase user who has never setup the Storage.
Please provide the Storage Setup API also for new firebase user35 votes -
Support Kotlin Multiplatform (KMP) in the SDKs
KMP is now stable and more libraries are being added to KMP ecosystem. There is a big opportunity for Firebase to be in Multiplatform and support developers adopting this tech.
664 votes -
Support fetching/returning data from mutations
Currently mutations return only the primary key of the created record, but it would be nice to be able to fetch the full record (including e.g. defaulted values) as part of a mutation.
34 votes -
SQL Aggregation Queries in GraphQL
Support aggregations (COUNT, SUM, AVG, MIN, MAX) with grouping as part of the built-in GraphQL query builder.
58 votes -
Realtime database, change default tab order
Reorder the tabs in Realtime DB to prioritize displaying the rules or a landing page before the data.
New users and analytics management find that loading the Realtime Database section from the web console impacts bandwidth usage for reads. This behavior is not ideal and could be separated from the Realtime Database landing page, especially when editing or inspecting the rules, as it requires loading larger chunks of the database before the user switches tabs.
4 votes -
Allow String to Timestamp conversion in Firestore rules
In Firestore rule, it could be very powerful to convert String containing date to Timestamp. For example, the RevenueCat extension store date as ISO 8601 string and we can't use them in firestore rule because date are not Timestamp.
In my Firestore rule, I would like to do something like :
timestamp.parse(collection.data.expires_date) > request.time
21 votes -
Allow connecting the web client to HTTPS-hosted emulators (for Web Push testing & more)
Allow connecting the web client to HTTPS-hosted emulators (for Web Push testing & more)
Browsers nowadays require HTTPS-hosted sites to use some privileged features, like Web Push. HTTPS-hosted sites also typically can not request HTTP content from APIs ("protocol downgrade" errors).
Most Firebase Emulators are not built to work with HTTPS, which puts up a big obstacle to test HTTPS-enabled features on external devices (e.g. test locally-hosted Web Push server code on an external Android phone).
Server-side: Firebase emulators don't offer ways to be served over HTTPS, but tools like ngrok or a local HTTPS proxy offer simple workarounds for…
36 votes
- Don't see your idea?