Skip to content

General

General

Categories

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

1236 results found

  1. Assets

    1 vote

    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. The hosting product support punycode domain but App Hosting doesn't which is kind of odd. Please bring App Hosting to the same domain support parity with the Hosting product. Thank you!

    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

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

    We're glad you're here

    Please sign in to leave feedback

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

    1 comment  ·  Agent Skills  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Problem
    Firebase Hosting currently serves content simultaneously across three URLs: a custom domain (e.g., site.example.org) and two system domains (project.web.app and project.firebaseapp.com). This creates duplicate content issues for SEO and fragmenting analytics.

    Proposed Solution
    Allow users to designate a Primary Domain within the Firebase Console. Once set, all requests to the default system domains should automatically trigger a 301 redirect to the primary custom domain.

    Key Requirements
    * Automatic Redirection: System domains (web.app / firebaseapp.com) should mirror the "Redirect" functionality already available for custom domains.
    * SEO Optimization: Consolidate page rank by ensuring only one…

    1 vote

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Larger customers often use Google Cloud Essential Contacts for ensuring critical notifications get to the right people. Currently Firebase product and developer communications seem to go out via email to named user accounts where the customer has no control who this goes to and it may miss its intended audience.

    It would be great if FIrebase notifications could be integrated with Google Cloud Essential Contacts to give customers more control over where critical notifications go to and to make this consistent with other Google Cloud services.

    https://docs.cloud.google.com/resource-manager/docs/managing-notification-contacts

    Thank you!

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Errors in native sql statements like in _execute always result in the same "Invalid SQL statement" error without any further information, which makes it really difficult to debug. More data - for example the part of the SQL statement that is invalid - would be really helpful! Especially as this error also seems to be thrown when the SQL is perfectly fine but a wrong _execute syntax is used, which should not throw an "Invalid SQL statement" error, as it is not about SQL!

    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)
  7. Firebase TLDR:

    UI?
    Trash
    Pricing?
    Trash... Cloudfare can do it for free.
    User experience?
    One of the worst system interface I have ever used in my entire life. I tested a few apps and got charged for testing a Alpha game for 2 days with a few friends, what I would've paid for a VPS for a whole month with unlimited amount of bandwidth.

    This plataform does NOT feel like a Google service. And I am NEVER going to use this **** ever again. Feels that I just got scammed for real.

    Firebase = Trash company. I hope Google finds…

    1 vote

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Iwant to used Google Ads.by YouTube channel and YouTube creations Apps and music studio channel us all in one YouTube page channel... I hope you're understand what I'm trying to say... that's all thank you for your.. understanding..

    1 vote

    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

    0 comments  ·  App Distribution  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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)
  10. When I press the login button on https://firebase.google.cn/docs/crashlytics/android/get-started-ndk?authuser=9&hl=en
    It displays the QR code to login with Wechat. But I'm not in China and I don't have wechat account.

    1 vote

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Just tell me: “build it” or “make it a business plan” 🚀

    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)
  12. Mujhe ek YouTube se Milta julta Ek app banana hai uski link Maine Upar Dal Di Haiuski link Maine Upar Dal Di Hai

    0 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

    0 comments  ·  App Check  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Firebase Auth Expose Email Verification Status and Attempts

    We have a user that is having problems verifying. However there is no logging or debugging for this feature on firebase.

    1. Add an interface under auth to see which users have requested verification
    2. Add information about if the email was recieved, spammed, blocked, expired
    3. Visually show which accounts are not validated, pending validation, and validated.
    4. Be able to reset validation, or manually validate
    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)
  14. Current Firebase App Check is using the classic play integrity API, which results in rate limit easily. As a result, the token decode will fail easily as the QPS limit by play integrity api. Why not migrate to the Standard Play Integrity API which suggested by Google Play?

    9 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

    1 comment  ·  App Check  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Native RBAC (Role-Based Access Control) management
    Currently, to manage roles (admin, editor, client), you have to use Custom Claims via the Admin SDK (Node.js) or store the roles in Firestore. This is cumbersome for a beginner.

    The improvement: Being able to define roles directly from the Firebase console and have them automatically appear in the request.auth object of Security Rules without additional code.

    1 vote

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. provide an option for the developer enforce a schema in the firebase console. At least on the firestore enterprise edition. Mongo Atlas had this offering. rightnow, we are having to manage schema at the app level and then again at the cloudfunctions level. Making it hard to manage.

    1 vote

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Hey, hi, I’m a Next.js developer, and the only problem I’m having with Firebase is with the Firebase Auth integration. I’d like to see improvements to the documentation for Next.js and its integration with server-side rendering. The problem I’ve encountered is that we need to save the token generated on the frontend to pass it to the backend. And the Next.js documentation recommends creating the token on the backend as “HttpOnly” for better security, but Firebase Auth doesn’t follow this pattern, and there isn’t much documentation about it or how Firebase handles cookie security.

    I hope Firebase will consider my…

    1 vote

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 1 vote

    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

    0 comments  ·  App Distribution  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Doing TLD SPOFING FOR WEB2:WEB3 TUNNEL MANAGEMENT

    TO ADD EXPLICIT RESTRICTIONS FOR “{TRAP HANDLER}” Inference Modeling

    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)
  20. Firestore Security Rules currently lack two capabilities that force developers to choose between security, performance, and maintainability.

    1. Lack of Transaction/Batch Awareness Rules cannot verify if a write is part of an atomic batch or transaction. This makes it impossible to enforce multi-document integrity constraints natively.

    The Fallout: Developers must either trust the client to perform all parts of an operation (unsafe) or move logic to Cloud Functions. This introduces latency and cold-starts, but more importantly, it fragments security logic. Concise, native rules bolster security because they are easier to audit and are implemented correctly more often than fragmented, multi-layered workarounds.

    1 vote

    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

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

    We're glad you're here

    Please sign in to leave feedback

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