1209 results found

1. Job development

   Animated script for game development video prompts analytics workspace for project management

   1 vote

   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  ·  Agent Skills  ·  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

   Submit Rating

2. Increase Firebase Testing Agent Session Duration

   We are currently using the Firebase Testing Agent for automated testing of our React Native mobile application.

   One major limitation for us is the current 5-minute maximum test duration. Our real user flows include authentication, navigation, API loading, and media/content interactions, so even the login process alone can sometimes take around 3.5 minutes before the actual test scenario begins.

   Because of this, many realistic end-to-end test cases cannot be completed within the current limit.

   It would be extremely helpful if Firebase could:

   Increase the maximum test duration beyond 5 minutes, or
   Provide configurable/custom timeout options, or
   Offer optimization recommendations/features for reducing setup and login time in AI-driven test flows.

   Longer session support would make the Testing Agent much more practical for production-scale mobile applications and enterprise QA scenarios.

   We are currently using the Firebase Testing Agent for automated testing of our React Native mobile application.

   One major limitation for us is the current 5-minute maximum test duration. Our real user flows include authentication, navigation, API loading, and media/content interactions, so even the login process alone can sometimes take around 3.5 minutes before the actual test scenario begins.

   Because of this, many realistic end-to-end test cases cannot be completed within the current limit.

   It would be extremely helpful if Firebase could:

   Increase the maximum test duration beyond 5 minutes, or
   Provide configurable/custom timeout options, or
   Offer optimization recommendations/features for… more

   1 vote

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

   Submit Rating

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

   52 votes

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

   Submit Rating

4. make linking console to studio a button, right

   that should be a done deal

   4 votes

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

   Submit Rating

5. Request to make "flutter deploy" to allow Incremental Remote Config parameters update

   Take this case,

   An Enterprise Project with multiple Mobile Apps underneath. In our case, it is an ERP system with multiple subject-based mobile apps. Each mobile app needs to control its forced-update on the client side. Remote Config is thought to be the way forward.

   We need to have "flutter deploy" update a parameter for each app, to keep the latest version. The app will check this against its bulit-in version number. If a mismatch, then force an update. Very typical scenario.

   The issue with the current "flutter deploy" as a method to automatically update/maintain Remote Config parameter for the App, is that is erases all other parameters for all other apps in the same project !!

   A remote config file such as
   {
   "parameters": {
   "myapplatestversion": {
   "defaultValue": {
   "value": "A2001-AI0109"
   },
   "valueType": "STRING"
   }
   }
   }

   is missing a directive, to state if this is a New (Add) or Update, or Overwrite the entire project partameters.

   Currently, the firebase Console allows this sort of incremental maintenance of the project parameters. Therefore, it is only normal to expect the Deploy API to provide the same functionality of the portal.

   We are willing to help, if you need an extra hand to program the feature !

   Take this case,

   An Enterprise Project with multiple Mobile Apps underneath. In our case, it is an ERP system with multiple subject-based mobile apps. Each mobile app needs to control its forced-update on the client side. Remote Config is thought to be the way forward.

   We need to have "flutter deploy" update a parameter for each app, to keep the latest version. The app will check this against its bulit-in version number. If a mismatch, then force an update. Very typical scenario.

   The issue with the current "flutter deploy" as a method to automatically update/maintain Remote Config parameter for the… more

   2 votes

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

   Submit Rating

6. 1251 end

   VIP NUMBER

   1 vote

   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

   Submit Rating

7. Add official React Native / Expo SDK with Clerk-like DX: protected routes, RBAC components, and declarative auth UI

   The Firebase Auth SDK for React Native requires significant boilerplate
   to implement properly — auth state listeners, Firestore role fetching,
   route protection, and error handling all have to be wired up manually
   in every project.

   The developer experience gap compared to alternatives like Clerk is
   significant. Clerk provides:

   • <SignedIn> / <SignedOut> declarative components
   • <Protect role="admin"> role-based rendering
   • Automatic route guards for Expo Router
   • Pre-built auth screens

   I built an open-source package called react-native-fireguard that fills
   this gap for Firebase developers:

   npm install react-native-fireguard

   It wraps Firebase Auth with:
   • <FirebaseAuthProvider> — single setup, handles everything
   • <RouteGuard> — automatic redirect for unauthenticated users
   • <SignedIn>, <SignedOut>, <Protect> — declarative components
   • Role-based access control via Firestore
   • Security fixes: onIdTokenChanged instead of onAuthStateChanged
   (catches server-side revocations), raw User never in React state,
   email enumeration prevention

   364 downloads in the first 4 days suggests strong developer demand.

   npm: https://www.npmjs.com/package/react-native-fireguard
   GitHub: https://github.com/Inspire00/react-native-fireguard

   My suggestion to Firebase: consider building this officially into the
   Firebase JS SDK or partnering with the community. React Native developers
   need a first-class auth DX story, not 300 lines of boilerplate in every
   project.

   The Firebase Auth SDK for React Native requires significant boilerplate
   to implement properly — auth state listeners, Firestore role fetching,
   route protection, and error handling all have to be wired up manually
   in every project.

   The developer experience gap compared to alternatives like Clerk is
   significant. Clerk provides:

   • <SignedIn> / <SignedOut> declarative components
   • <Protect role="admin"> role-based rendering
   • Automatic route guards for Expo Router
   • Pre-built auth screens

   I built an open-source package called react-native-fireguard that fills
   this gap for Firebase developers:

   npm install react-native-fireguard

   It wraps Firebase Auth with:
   • <FirebaseAuthProvider> — single setup, handles everything
   •… more

   1 vote

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

   Submit Rating

8. Make App Hosting available in Doha and Dammam region (me-central)

   Deployment of apps in the firebase project has limited region options and middle east regions are not among them.

   Allowing the deployment of backend in these region will enable us to lower latency and use the cool firebase dashboards to manage the backend without having to go to GCP console often.

   3 votes

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

   Submit Rating

9. Store Firebase Console date filter settings in browser LocalStorage

   When I use Firebase Analytics on Firebase Console, it's quite annoying to set date filter settings every time when I visit that page.

   Firebase Console webapp should store user's date filter settings in a browser LocalStorage in order to get rid of this behavior.

   1 vote

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

   Submit Rating

10. Perform automatic rollouts only for changes to configured app directory

    I have a Next.js app within a monorepo for my Firebase project, which also includes an iOS and Android app, each in their own directories. My App Hosting backend is configured for the Next.js app directory, but it appears that the automatic rollouts feature does not take this setting into account when changes are pushed to the repo. I don't want to perform a rollout when making changes only the iOS app, for example.

    Automatic rollouts should only perform the rollout (or be able to be configured to) only when the specified app directory contains changes. Path matching is a common feature in CI/CD and I'm surprised to find that this isn't the default behavior. We should be able to specify which path(s) App Hosting monitors for changes, so that it doesn't needlessly roll out every time I make a change in the monorepo that doesn't affect the app.

    I have a Next.js app within a monorepo for my Firebase project, which also includes an iOS and Android app, each in their own directories. My App Hosting backend is configured for the Next.js app directory, but it appears that the automatic rollouts feature does not take this setting into account when changes are pushed to the repo. I don't want to perform a rollout when making changes only the iOS app, for example.

    Automatic rollouts should only perform the rollout (or be able to be configured to) only when the specified app directory contains changes. Path matching is a… more

    2 votes

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

    Submit Rating

11. Update iphone 16 and iphone 17 mapping for device information

    Now for iphone 16 and iphone 17, analytics only detect it as iphone, marketing name is null.
    It is hard to analyze user's device distribution.

    3 votes

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

    Submit Rating

12. Persistent Memory & "Do Not Modify" Toggles to Protect Existing Code

    As a project becomes more developed, I've noticed that the Gemini assistant in Firebase Studio sometimes starts modifying templates, forms, and functions that were already working perfectly.

    To prevent this, I currently have to prepend a strict warning to every single prompt: "Proceed with extreme caution. Do not change the visual design, menus, structure, or any logic unrelated to this specific query: [my actual prompt]". While this workaround is effective and usually results in better code, it is tedious to write every time.

    My Suggestion: It would be incredibly helpful to implement a "Context Memory" feature with a checklist or on/off toggles. This would allow developers to explicitly mark certain functions, files, or UI layouts as "Locked/Remember" (Gemini must preserve them) and others as "Modifiable". This way, we wouldn't have to constantly use defensive prompting to protect the code that is already finished and working.

    As a project becomes more developed, I've noticed that the Gemini assistant in Firebase Studio sometimes starts modifying templates, forms, and functions that were already working perfectly.

    To prevent this, I currently have to prepend a strict warning to every single prompt: "Proceed with extreme caution. Do not change the visual design, menus, structure, or any logic unrelated to this specific query: [my actual prompt]". While this workaround is effective and usually results in better code, it is tedious to write every time.

    My Suggestion: It would be incredibly helpful to implement a "Context Memory" feature with a checklist or… more

    2 votes

    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  ·  Agent Skills  ·  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

    Submit Rating

13. Kira
    1 vote

    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  ·  Remote Config  ·  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

    Submit Rating

14. Custom domain

    Custom Dom should instantly hook on the app hosting

    3 votes

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

    Submit Rating

15. Firebase main page.

    in the main Page of firebase , its feel empty nad only shows the projects name, i wish it every project looks like a box under each one shows data about it , Analytics , DAU , for all of them at once

    1 vote

    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

    Submit Rating

16. F
    1 vote

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

    Submit Rating

17. 200

    Fo Tamien

    1 vote

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

    Submit Rating

18. Create a tool to import and export json data as collections in and out of firestore
    2 votes

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

    Submit Rating

19. Realtime database console, usage tooltip scroll

    If you have many RTDB instances, it's practically impossible to use the Usage tab in the console and view the tooltips. I have to scroll out to 25% in my browser, to see our current full list, and we may have more in the future. You should add a way to scroll the tooltip. I'm thinking: click graph, so you know which tooltip to show, and then make the tooltip static and scrollable. But it could be implemented however makes sense to the developers, as long as I can scroll down the tooltip and not have to zoom way out (such that I can't really properly read it or see the icons).

    If you have many RTDB instances, it's practically impossible to use the Usage tab in the console and view the tooltips. I have to scroll out to 25% in my browser, to see our current full list, and we may have more in the future. You should add a way to scroll the tooltip. I'm thinking: click graph, so you know which tooltip to show, and then make the tooltip static and scrollable. But it could be implemented however makes sense to the developers, as long as I can scroll down the tooltip and not have to zoom way out… more

    5 votes

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

    Submit Rating

20. ربط تطبيق تكسيً بلي بتطبيق زين كاش لسحب أموالي

    ربط حسابي تطبيق تكسيً بلي بتطبيق زين كاش لسحبً أموالي

    1 vote

    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  ·  SQL Connect (Data Connect)  ·  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

    Submit Rating