685 results found

1. Support Go in Cloud Functions

   Go is much more efficient than Python or Js and should be the obvious choice for backend where performance is crucial

   31 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  ·  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

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

3. Firebase Setup infrastructure

   I'm creating an Open Source Cloud Native Platform based on Firebase. Every installation requires manual steps, to enable specific APIs.
   Please provide a configuration file where I can configure all required Google Cloud services (like Google Translate, Storage, Artifact Registry, etc ...).
   It will facilitate the automatic installation of Firebase applications.

   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

   0 comments  ·  Other  ·  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

4. Add support to programmatically configure social providers for tenants

   Add the ability to configure social authentication methods like Google, Facebook, etc. like how OIDC and SAML can be done.

   Also, the ability to use the parent configuration for Google Authentication so it is just an enable like in the Web Console UI. This reduces the overhead code that we need to provide if all we are doing is splitting into different tenants for management reasons.

   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  ·  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. In all SDKs for node and web implement industry best practice error reporting and error codes

   I have been working on multiple projects that use Firebase, I use the Firebase JS SDK and the Firebase Admin SDK. And I am always pulling my hair out with the error reporting and the ability to handle in the SDKs returned errors. This is especially annoying when using TypeScript.

   There is also no master list of all error codes that an SDK can produce. That means I can get random error that I have to back trace to then add handling for it. Also I have to infer types all the time instead of using instanceof to check if it is an SDK error and get TS support.

   1. Please document all the error codes that each SDK could produce.

   2. Add a page to the documentation site about Error handling in the SDK (helps to explain how it works in this SDK if not very obvious)

   3. Please add a proper typescript Error object to the SDK. This would be a class that extends Error object and for the code property has all the possible codes it can produce. By doing this, the developers will be required to add to the list of error codes that the SDK has on the error if they add a new code when then trigger the error handling code. This means that users as they upgrade get more options in the SDK that they can use to see the new error types that have occurred.

   4. Contribution policy on the GitHub library that describes the error handling approach that has been placed and the expectations that are required for future code inclusion. This stops this from going backwards.

   99/100 I want the error code only and adding either or both would save 100s of hours of hair pulling (I don't want to look like Frank van Puffelen to soon).

   I acknowledge that this has been partially done, but an overhaul that finishes it would be much appreciated.

   I have been working on multiple projects that use Firebase, I use the Firebase JS SDK and the Firebase Admin SDK. And I am always pulling my hair out with the error reporting and the ability to handle in the SDKs returned errors. This is especially annoying when using TypeScript.

   There is also no master list of all error codes that an SDK can produce. That means I can get random error that I have to back trace to then add handling for it. Also I have to infer types all the time instead of using instanceof to check if… 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  ·  SDKs  ·  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. 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.

   37 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

7. Allow setting a maximum amount per billing cycle
   87 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

   14 comments  ·  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. Slack webhook for app distribution

   When we share a build to Firebase App Distribution it would be great to share that build details and link into slack. There's no easy way of doing this at the moment.

   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  ·  App Distribution  ·  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. Jendo

   Menarik

   0 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  ·  App Hosting  ·  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. Support reCAPTCHA Enterprice Multi-factor authentication

    AppCheck fail of low score reCaptcha

    user can't access based on AppCheck fail of low score reCaptcha

    reCAPTCHA Enterprice support Multi-factor authentication (Conditionally enforce email multi-factor authentication for users who score below a threshold.) but AppCheck does not.

    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

    0 comments  ·  App Check  ·  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

11. Should add basic REDIS/ Memcache Like Capability

    Why I Want This?

    Firebase splits functions to individual Docker Container. This works great for scaling, but with that it is not easy to share global values, for example, user's access key to external services and session specific values.

    While we can use REDIS and such hosted on GCP, it would be more "batteries included" platform if this feature is offered as a built-in functionality for the functions without resorting to Firestore or RTDB.

    What I look for is to globally share key values and also auto-expire them.

    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

    0 comments  ·  Cloud Functions for Firebase  ·  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

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

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

14. Support for web apps in Crashlytics
    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

    1 comment  ·  Crashlytics  ·  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. Food and beverages

    We need more supplies for our upcoming events

    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

    0 comments  ·  Firebase console  ·  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

16. Sub Collection View

    I feel the window to view sub collection on the firebase firestore console could be expandable.

    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

    0 comments  ·  Cloud Functions for Firebase  ·  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

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

18. Support adaptive app icons

    Android 8.0 (API level 26) introduced adaptive app icons, which are made out of background and foreground layer. Apps that have minSDK = 26 don't have to specify "flat" PNG icons. However, App Distribution doesn't support adaptive app icons, and as a result weird icon with cropped app name is displayed in the App Tester app. App Distribution should support adaptive app icons by parsing icon XML, obtaining foreground and background assets, and based on this render the icon.

    5 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 Distribution  ·  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. Crashlytics support for react JS based application.

    Crashlytics support for react JS based application.

    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

    0 comments  ·  Crashlytics  ·  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

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