546 results found

1. Firestore: Use C++ implementation directly from Swift

   Swift has recently gained direct interoperability with C++.
   
   This would allow the current bridging layer written in Objective-C++ to be removed, which would in turn make it possible to use Firestore from Swift cross platform.

   The Browser Company have created patches for firebase-cpp-sdk to allow this:

   https://github.com/thebrowsercompany/swift-firebase

   It could also decrease the maintenance burden by removing the bridging layer code.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firestore  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Automatic SMS OTP read with English templates

   For automatic SMS retrieval to work, SMS length has to be under 64 bytes. This means currently that for English SMS template, the app name has to be 11-14 characters. Play Console allows max 30 characters. Firebase doesn't allow customers to modify the SMS template contents themselves. Now I'm working around by utilizing some other languages, that will fit below 64 bytes with current app name.

   Two options I suggest to achieve this:
   1) Modify the English SMS template: remove unnecessary filler words and make it shorter, so that it will fit to 64bytes with max 30 char app names.

   or

   2) Add support to Firebase SMS Templates for English variants, so those could be used solely for sending out OTP SMS with shorter app names set in the Store listing.

   For automatic SMS retrieval to work, SMS length has to be under 64 bytes. This means currently that for English SMS template, the app name has to be 11-14 characters. Play Console allows max 30 characters. Firebase doesn't allow customers to modify the SMS template contents themselves. Now I'm working around by utilizing some other languages, that will fit below 64 bytes with current app name.

   Two options I suggest to achieve this:
   1) Modify the English SMS template: remove unnecessary filler words and make it shorter, so that it will fit to 64bytes with max 30 char app names.

   … more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Authentication  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Fee/Pricing

   Functions is behind paywall, (it is still free for some limit in Blaze plan), but IF i upgrade to Blaze, then Cloud Storage, Hosting etc starts to charge right away, even in free plan they have free limits but once switched to Blaze it starts to charge. So to get free Functions, i have to pay cloud storage and hosting and more.

   For any playground project that is not gonna hit market or earn money, how i am supposed to try/learn functions? This forces me to move away from platform

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Cloud Functions for Firebase  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Customize password creation requirements
   43 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Authentication  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Custom build command

   It can be necessary to run a script before the build command.

   Example:

   • With angular: A script to create the environment.ts files need to be run before the ng build.
   • With Prisma: A script to generate the prisma files should be run before the build the build itself.

   Suggestion:

   As for render.com, get in the settings Build Command options and Start Command

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Security Rules: unique() operator

   I am submitting a feature request to introduce a 'unique()' operator in Firestore's security rules, offering a streamlined method to enforce data uniqueness within collections. This operator would not only simplify validation and potentially reduce reads by leveraging Firestore's hidden index table, but also eliminate the need for a separate cloud function, similar to the 'get()' and 'exists()' operations.

   Background:

   At present, ensuring data uniqueness in Firestore often requires workarounds that are less than optimal and can impact scalability.

   Feature Proposal:

   The proposed 'unique()' operator would operate much like the 'exists()' operation, but with a focus on reading Firestore's concealed index table. This efficient approach would verify the uniqueness of specified fields within collections.

   Comparison to Existing Operations:

   Similar to the 'get()' and 'exists()' operations, the 'unique()' operator would provide developers a straightforward means to validate crucial data points such as usernames, email addresses, and more, all without the need for complex cloud functions.

   Example Usage:

   For instance, to ascertain unique usernames:

   Firestore Security Rules:

   function isUniqueUsername(username) {
     return unique(/databases/$(database)/documents/users, ['username', '==', username]);
   }
   

   Benefits:

   Introducing the 'unique()' operator not only simplifies the validation process and leverages the hidden index table but also eliminates the requirement for an additional cloud function. This comprehensive approach enhances Firestore's performance while maintaining developer-friendly functionalities.

   Conclusion:

   By implementing the 'unique()' operator, Firestore could effectively address the challenge of maintaining data uniqueness while offering a holistic solution that eliminates the need for cloud functions.

   Thank you for considering this feature request. I'm optimistic about the significant value it could add to Firestore and our development workflows.

   I am submitting a feature request to introduce a 'unique()' operator in Firestore's security rules, offering a streamlined method to enforce data uniqueness within collections. This operator would not only simplify validation and potentially reduce reads by leveraging Firestore's hidden index table, but also eliminate the need for a separate cloud function, similar to the 'get()' and 'exists()' operations.

   Background:

   At present, ensuring data uniqueness in Firestore often requires workarounds that are less than optimal and can impact scalability.

   Feature Proposal:

   The proposed 'unique()' operator would operate much like the 'exists()' operation, but with a focus on reading Firestore's concealed… more

   18 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Firestore  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Django support for firebase app hosting

   Django is a very popular framework. It is likely the easiest one to get up and running with, also allowing reusing the code much better than other solutions. No need to say how big Python is and Django (and even Flask) will only become bigger and bigger. Firebase app hosting must support Django. Not tomorrow, now!

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Hosting  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Add an argument that automatically chunks cloud function deployments according to the maximal possible quota

   When deploying multiple cloud functions at once via

   firebase deploy --only functions

   we frequently run into quota issues like:

   • functions: got "Quota Exceeded" error while trying to update projects/.... Waiting to retry...

   It never retries though.

   It would make it way easier if you could add an argument to the deployment command like:

   firebase deploy --only functions --chunked 50

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Cloud Functions for Firebase  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. remove recaptcha firebase phone auth flutter

   remove recaptcha firebase phone auth flutter

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Authentication  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    5 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Improve firestore explorer UI - it is too small

    The UX when reading large objects in the firestore explorer UI requires too much scrolling in small windows to find the information you are after. I'd propose to:

    Note: "window" here refers to where the container where the data of a document can be found or alternatively where all the collection can be found. So the firestore explorer contains usually, a collection window, a document window, (a sub collections window, a document window,...).

    • collapse maps by default, or collapse maps if the object is larger than the current window. When dealing with large objects it's currently annoying to find the information by scrolling.
    • make the explorer bigger or add a button to have the explorer as full screen. Currently takes only half the space available on a 15 inch screen.
      • when you have a subcollection and you are watching a document in this sub collection, the collections and documents are aligned vertically. It would be nice to have a handle to be able to resize which of the sub collection or document take more vertical space.

    The UX when reading large objects in the firestore explorer UI requires too much scrolling in small windows to find the information you are after. I'd propose to:

    Note: "window" here refers to where the container where the data of a document can be found or alternatively where all the collection can be found. So the firestore explorer contains usually, a collection window, a document window, (a sub collections window, a document window,...).

    • collapse maps by default, or collapse maps if the object is larger than the current window. When dealing with large objects it's currently annoying to find the… more
    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Create a context.auth (1st Gen) equivalent for 2nd Gen cloud function

    1st gen cloud functions can access auth info via context.auth as described here: https://firebase.google.com/docs/database/extend-with-functions?gen=1st#accessing_user_authentication_information

    But 2nd gen cloud functions is yet to have the same function.

    23 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Cloud Functions for Firebase  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Getting started Tutorials needs critical refinement and acurate articulation of label, navigation steps

    https://firebase.google.com/codelabs/firebase-nextjs#4
    Labels and directions in the tutorial are not matching the Firebase console. Configuration steps are vague and not descriptive enough. Example " Add your Firebase configuration to your web app code" section Step 2 makes sense if no app was build, but at this point of the tutorial the app has been created "My Nexst.js app", so these instruction are not right. Step 3 i believe is wrong or inaccurately written. Are we to transpose the contents to the npm tab from the "SDK setup and configuration pane" to the proper variable state or if we are to replace all the contents of the apphosting.yaml file with a variable and the objects from the npm or config. What does "In the file, replace the existing properties with those that you copied." mean....? Be specific, clear and detailed... This is waisting
    my time trying to figure out what you meant to write...

    https://firebase.google.com/codelabs/firebase-nextjs#4
    Labels and directions in the tutorial are not matching the Firebase console. Configuration steps are vague and not descriptive enough. Example " Add your Firebase configuration to your web app code" section Step 2 makes sense if no app was build, but at this point of the tutorial the app has been created "My Nexst.js app", so these instruction are not right. Step 3 i believe is wrong or inaccurately written. Are we to transpose the contents to the npm tab from the "SDK setup and configuration pane" to the proper variable state or if we are to replace… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Remote Config Emulator

    Provide a native emulator for Remote Config with A/B tests will be great, but is not critical.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Remote Config  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. The ability disable default domains
    41 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Allow customization of email template message
    42 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Authentication  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Filter on reference fields in the Firestore panel

    There is currently no way to filter on reference fields in the Firestore panel of the Firebase console.

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    4 comments  ·  Firestore  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Change FCM Reports console timezone

    As I know FCM reports console uses Pacific Standard Time (PST), please make a feature that I can change FCM Reports console to another timezone.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Cloud Messaging  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. useEmulator should return False if emulator is not running

    I am currently using firebase/firestore from react native. Currently

    import { firebase } from "@react-native-firebase/firestore";

    const rc = firebase.firestore().useEmulator("192.168.1.130", 8080);

    Ideally I would like rc=False if the emulator is not up.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Emulators  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. 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/#format

    38 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Authentication  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close