1486 results found

1. List of all error codes in auth (Not the admin SDK)

   Currently there is only a list of error codes the Admin SDK can receive, not for the web sdk.

   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  ·  Documentation  ·  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. Phone number for testing in firebase emulator

   It would be great to be able to configure static MFA validation codes / phone numbers for testing in the emulator, like in the normal firebase auth product.

   This would make testing an application with automated tests a lot easier.

   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

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

   Submit Rating

3. Phone number for testing in firebase emulator

   It would be great to be able to configure static MFA validation codes / phone numbers for testing in the emulator, like in the normal firebase auth product.

   This would make testing an application with automated tests a lot easier.

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

4. The ability too see when an index was last accessed

   When a project grows to a certain size, you'll likely have many indexes with associated queries.

   However, queries change, or get removed, and currently there's no way to see if an index could be safely removed, after a query is; which would be a great feature.

   11 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

   Submit Rating

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

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

6. Crashalytics to support SDK

   I need crashlytics to track crashes of my SDK not the crashes of the app which is implementing my SDK

   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

   Submit Rating

7. Ability to select and copy fields and values in firestore document

   Ability to select and copy fields and values in firestore document, more like making everything selectable text.

   6 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

   Submit Rating

8. Hosting CDN cache stale-while-revalidate

   Time-to-first-byte from Firebase Functions is usually slow (more than 500ms) even without cold start, sometimes (with cold starts) TTFB becomes absolutely unacceptable for projects where performance is important. SSRed HTML is also not Brotli compressed as static files.
   This is a really big problem to deploy SSR web apps to Firebase IMO, and cache SWR at the CDN layer (edge) would solve it perfectly.

   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  ·  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. Lazy loading of items in firebase console for firestore

   Console has become laggy and returns a wait for page to load alert if a document has to many fields

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

10. Support "Continuing Uploads Across Process Restarts" on iOS

    I work for a company that enable people to record sports using video and the storage footprint are often very huge (10GB+). While building an app for iOS, I notice that Firebase don't support continuing uploads across process restarts on iOS which is a major deal-breaker for continuing using Cloud Storage for Firebase.
    I see support for this on Android and I will encourage you to add this to iOS in the future. Ref: https://firebase.google.com/docs/storage/android/upload-files#continuing_uploads_across_process_restarts

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

11. Support "Continuing Uploads Across Process Restarts" on iOS

    I work for a company that enable people to record sports using video and the storage footprint are often very huge (10GB+). While building an app for iOS, I notice that Firebase don't support continuing uploads across process restarts on iOS which is a major deal-breaker for continuing using Cloud Storage for Firebase.
    I see support for this on Android and I will encourage you to add this to iOS in the future. Ref: https://firebase.google.com/docs/storage/android/upload-files#continuing_uploads_across_process_restarts

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

12. Possibility to disable the automatic event "notification_receive" (Android) due to the high triggering of this event

    I would like to request the inclusion of the possibility of disabling the automatic event "notificationreceive" (Android) due to the high firing of this event, which can cause an inflation of costs for Google Analytics 360 customers who charge based on the number of events.
    And in some situations it is necessary to use push notifications, but the "notificationreceive" event may not be so useful, it being feasible to disable it to reduce tool 360 costs

    A suggestion would be to make it possible to disable it in the same way as we can disable the automatic event "screen_view" through a configuration in the AndroidManifest (reference https://firebase.google.com/docs/analytics/screenviews?hl=pt-br)

    I would like to request the inclusion of the possibility of disabling the automatic event "notificationreceive" (Android) due to the high firing of this event, which can cause an inflation of costs for Google Analytics 360 customers who charge based on the number of events.
    And in some situations it is necessary to use push notifications, but the "notificationreceive" event may not be so useful, it being feasible to disable it to reduce tool 360 costs

    A suggestion would be to make it possible to disable it in the same way as we can disable the automatic event… more

    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

    Submit Rating

13. Upload from local file store (or anywhere)

    Current file import options limited to github (and ssh). Ability to navigate local directories, net mount points, cloud storage blobs and URLs would be epic!

    A+ so far, cannot wait until Project IDX public launch ;)

    21 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  ·  Firebase Studio  ·  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. Add error stack trace to the testing emulator

    There is no error stack trace with the emulator for cloud functions. Which makes it very hard to deploy since you will encounter many errors. It's a real pain.

    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

    Submit Rating

15. Streaming

    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?

    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

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

16. Angular Template with Nx , Bazel ( monorepo in general )

    per config template with default option and ability to customize

    https://start.spring.io

    Spring Initializr is good example

    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

    1 comment  ·  Firebase Studio  ·  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. fix broken git project import

    I attempted to import a flutter codelab by using the git project import with url: https://github.com/material-components/material-components-flutter-codelabs.git

    It fails, with no useful error message. However, this is the stack from the js console:
    Error: Internal error encountered.
    at iM.f (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:720:10)
    at new iM (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:845:332)
    at .MN.<anonymous> (https://www.gstatic.com//mss/boq-monospace//js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTSg/m=base:892:163)
    at IM (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:855:206)
    at l.dispatchEvent (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:853:343)
    at QN (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:886:284)
    at SN (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:888:326)
    at .MN.Zl (https://www.gstatic.com//mss/boq-monospace//js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTSg/m=base:887:430)
    at .MN.Tb (https://www.gstatic.com//mss/boq-monospace//js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTSg/m=base:887:394)
    at XMLHttpRequest.Hd (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:727:416)
    at t.Ti (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:715:49)
    at Object.bj (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:342:111)
    at t.Ti (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:715:9)
    at p.eq (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:708:19)
    at u.Ti as Wb

    I attempted to import a flutter codelab by using the git project import with url: https://github.com/material-components/material-components-flutter-codelabs.git

    It fails, with no useful error message. However, this is the stack from the js console:
    Error: Internal error encountered.
    at iM.f (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:720:10)
    at new iM (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:845:332)
    at .MN.<anonymous> (https://www.gstatic.com//mss/boq-monospace//js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTSg/m=base:892:163)
    at IM (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:855:206)
    at l.dispatchEvent (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:853:343)
    at QN (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:886:284)
    at SN (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:888:326)
    at .MN.Zl (https://www.gstatic.com//mss/boq-monospace//js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTSg/m=base:887:430)
    at .MN.Tb (https://www.gstatic.com//mss/boq-monospace//js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTSg/m=base:887:394)
    at XMLHttpRequest.Hd (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:727:416)
    at t.Ti (https://www.gstatic.com/_/mss/boq-monospace/_/js/k=boq-monospace.MonospaceNgUI.en.taNhyicQfx4.es5.O/d=1/excm=base/ed=1/dg=0/wt=2/ujg=1/rs=AP-1MC6DV8OE0pFyUXjT0KOqbeh54rTS_g/m=base:715:49)
    at Object.bj… more

    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 Studio  ·  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. Blank template needs to be a lot more... blank

    I was really surprised how much content is included in the blank template. I can get behind having the html file, JS, and CSS, but they should actually be empty, or mostly empty. The HTML file can have a base skeleton (html, head, body, that's it), but the JS and CSS files should be empty. I'm having to remove a lot to get to a 'proper' blank.

    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  ·  Firebase Studio  ·  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. Easy way to start a new project

    Once you get into a project, there's no clear way to start a new one from scratch.

    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  ·  Firebase Studio  ·  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. Project Templates

    The ability for users to initialize projects using set templates for their desires tech stacks. For example, allowing me to select a new Next.js project from the initialization page.

    6 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  ·  Firebase Studio  ·  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