Skip to content

General

General

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

30 results found

  1. 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…

    625 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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.

    165 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. It is currently already possible to create google cloud tasks. However, this could be better integrated by creating an abstraction for queues, for example, which can also be monitored and controlled via the admin console and firebase emulator.

    24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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.

    19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Go is much more efficient than Python or Js and should be the obvious choice for backend where performance is crucial

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Bring in Edge Runtime for functions to perform high performance tasks in the edge cloud for faster responses.

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. It's a pain to have to configure a process to watch and transpile TypeScript files to use in the emulator. Firebase CLI should have built-in support for it both in the emulator (with automatic watching, or on-the-fly transpilation as I showed here https://github.com/firebase/firebase-tools/issues/5633#issuecomment-1622585432) and when deploying.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Jvm languages are not supported in Cloud Functions today, so developers need to use more than one language in their code base.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. An article and youtube video explains how to optimize cold boots by updating dependencies to 'commonly used versions' as this will increase the chance that the dependencies can already be found in the 'dependencies cache'.

    https://medium.com/@duhroach/improving-cloud-function-cold-start-time-2eb6f5700f6

    This is quite vague and a bit hard to reason about. Would it be possible to see a list of package names and version info for all packages in the dependencies cache?

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. To implement userfriendly generative AI applications it is import to stream data produced by LLMs back to the users browser. Firebase currently buffers all content and only returns when data is complete. Is the firebase team planning to implement this?

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. With Firebase, you can have real time listeners on Firestore documents, which allow to have your UI in sync with your data.

    But when you ship logic in an app, you lose control over it.

    If you want to be able to update that logic after shipping, you place it in the backend (Cloud Functions), but then you lose real time updates.
    It would be amazing to have functions that can fire real-time events based on Firestore updates.

    So the flow would be:
    - There is an update in a Firestore document (or potentially other triggers like pub/sub, analitycs, etc.)…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. We all knoow cloud functions are not free now. But it would be great if you kindly allow upto 3 cloud functions without all the expensive apis like cloud vision etc.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. In the same way, we have onCreate and onDelete, it will be very helpful to have an onUpdate option. For example, so we can react to an email address change.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Currently using 2nd gen cloud functions requires having the default Compute Engine Service Account and there is no way to use custom service account.

    Not all projects have the service account or have any means to re-create the default SA if it has been deleted at some point and using default service accounts is anyway something that is not recommended by Google. So currently not all can move to using 2nd gen cloud functions unless support for using custom SA is added.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. In this code await admin.auth().createUser({
    email: email,
    displayName: name,
    uid: uid,
    emailVerified: false,
    password: password,
    disabled: false,
    });, if email and password are created, please create the user via that login method and if only phone is provided and no email, then let the user be created via phone auth. So that later on, when they try to sign in via phone auth, the system doesn't create a whole new user with a new uid but just lets the user sign into that account

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. By default HTTP Firebase Functions are made public. In Google Console they are marked as "Allow unauthenticated" because they will allow all callers, without checking authentication.

    I would like an option to deploy them privately.

    Example:

    const privateFunction = onRequest(
    {
    allowUnauthenticated: false,
    },
    (req, res) => {
    res.status(200).send(req.body);
    },
    );

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1
  • Don't see your idea?