1236 results found

1. food

   "Create a responsive, single-page food delivery application like Zomato or Swiggy using only HTML, CSS, and JavaScript (no frameworks). The app should simulate user interaction and have dynamic UI updates using JavaScript. Include the following features divided into key modules:

   ---

   🧑‍🍳 1. Home Page & Restaurant Listing

   A header navbar with logo, search bar, login button

   A location selector (dropdown or modal)

   A carousel/banner section for promotions

   Display a list of restaurants with:

   Restaurant Name

   Ratings & Reviews

   Cuisine Tags (e.g., Indian, Chinese, Pizza)

   Estimated Delivery Time

   Restaurant Image

   Use JavaScript to load restaurant data from a local mock JSON or JS array.

   ---

   📜 2. Restaurant Details & Menu View

   When a user clicks on a restaurant card:

   Open a new section/modal with:

   Restaurant name, image, ratings

   Dynamic food menu list categorized by type (e.g., Starters, Main Course, Desserts)

   Each item should show:

   Item name

   Price

   Short description

   “Add to Cart” button

   Data should be loaded dynamically using JavaScript.

   ---

   🛒 3. Cart System (Client-side using JS)

   Add/remove food items from cart using buttons

   Display total price, quantity, and list of added items

   Add “Place Order” button (which simulates order placed)

   Cart should be a popup or side panel

   Use localStorage to persist cart data on page reload

   ---

   👤 4. User Authentication Simulation

   Simple modal for login/signup with email & password

   Use localStorage to simulate user login session

   After login, show user icon and name instead of login button

   ---

   🛍 5. Order History (Optional Advanced)

   Store placed orders in localStorage

   Display past orders on a separate section with date, items, and total amount

   ---

   ⚙ 6. Admin Simulation (Basic)

   A hidden admin page that can:

   Add/edit restaurant info

   Add/edit menu items

   View order stats (from stored data)

   Use basic form inputs and localStorage to simulate updates.

   ---

   🎨 UI & Styling

   Use clean and modern CSS

   Make it fully responsive for mobile and desktop

   Use CSS grid/flexbox for layout

   Include hover effects, transitions, and popups

   ---

   💡 Technical Constraints

   No external JS frameworks like React/Vue

   Only vanilla JavaScript, HTML, and CSS

   Use localStorage for storing:

   Cart

   User session

   Order history

   Mock restaurant data

   Use modular JavaScript (functions for each action)

   ---

   📦 Output Files:

   Structure your files like this:

   /food-app/
   │
   ├── index.html
   ├── style.css
   ├── script.js
   ├── /assets/
   │ ├── images/
   │ └── icons/
   └── /data/
   └── mockRestaurants.js

   ---

   ✅ Bonus Feature Ideas (Optional):

   Rating/feedback system

   Search filter (by rating, cuisine, time)

   Pagination or infinite scroll

   Order tracking steps (like “Preparing”, “Out for Delivery”, “Delivered”)

   Delivery partner mock profile

   ---

   ✅ Example Usage:

   👉 You can feed this prompt directly to ChatGPT or Copilot:

   "Generate a single-page food delivery web app using HTML, CSS, and JavaScript with restaurant listing, dynamic menu, cart system with localStorage, and order placement simulation."

   "Create a responsive, single-page food delivery application like Zomato or Swiggy using only HTML, CSS, and JavaScript (no frameworks). The app should simulate user interaction and have dynamic UI updates using JavaScript. Include the following features divided into key modules:

   ---

   🧑‍🍳 1. Home Page & Restaurant Listing

   A header navbar with logo, search bar, login button

   A location selector (dropdown or modal)

   A carousel/banner section for promotions

   Display a list of restaurants with:

   Restaurant Name

   Ratings & Reviews

   Cuisine Tags (e.g., Indian, Chinese, Pizza)

   Estimated Delivery Time

   Restaurant Image

   Use JavaScript to load restaurant data from a local mock JSON… 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  ·  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

2. easy hosting

   Hi, I completely understand that Firebase Studio is fantastic for "vibe-coding" – even for experienced developers! However, after quickly building a front-end, I've found myself stuck on the next steps.

   I've been trying for weeks to deploy a fully functional app but struggle with the backend aspects. I've explored Firebase Hosting, Firestore, Realtime Database, and Authentication, but for a non-coder who was excited by the "vibe-coding" concept, these backend tasks are incredibly challenging. It would be amazing if there were easier ways to handle this, perhaps as simple as filling out a form or using natural language requests. While I know this might not be easy to implement, making the backend truly accessible is where "vibe-coding" could become a real game-changer.

   Hi, I completely understand that Firebase Studio is fantastic for "vibe-coding" – even for experienced developers! However, after quickly building a front-end, I've found myself stuck on the next steps.

   I've been trying for weeks to deploy a fully functional app but struggle with the backend aspects. I've explored Firebase Hosting, Firestore, Realtime Database, and Authentication, but for a non-coder who was excited by the "vibe-coding" concept, these backend tasks are incredibly challenging. It would be amazing if there were easier ways to handle this, perhaps as simple as filling out a form or using natural language requests. While I… 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  ·  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

3. Run code with optimal precision I'm trying to run code using firebase

   Running code with multiple intervals may lead to fast response times when coding

   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

4. Support Direct VPC

   A static IP is a must-have feature when dealing with certain services.
   In the past, we could use Serverless VPC Access connectors, but this required renting a virtual machine (VM), which contradicts the principles of serverless architecture and significantly increases costs.
   Recently, a new method called Direct VPC has emerged, which eliminates the need for connectors. This means it is truly serverless, even when using a static IP.
   Currently, Direct VPC can be configured by revision in the Google Cloud Console. However, I would like to enable Direct VPC in Firebase Functions as an option, like so:
   
vpcConnector: 'test-connector',
vpcConnectorEgressSettings: 'PRIVATE_RANGES_ONLY'


   See more about the compression from the doc below:
   https://cloud.google.com/run/docs/configuring/connecting-vpc

   A static IP is a must-have feature when dealing with certain services.
   In the past, we could use Serverless VPC Access connectors, but this required renting a virtual machine (VM), which contradicts the principles of serverless architecture and significantly increases costs.
   Recently, a new method called Direct VPC has emerged, which eliminates the need for connectors. This means it is truly serverless, even when using a static IP.
   Currently, Direct VPC can be configured by revision in the Google Cloud Console. However, I would like to enable Direct VPC in Firebase Functions as an option, like so:
   
vpcConnector: 'test-connector',
vpcConnectorEgressSettings:… 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

   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

5. Consistent and documented behavior for on*WithAuthContext

   When Functions use e.g. onDocumentCreatedWithAuthContext to handle Firestore event triggers, the meaning of event.authType and event.authId are not documented and are inconsistent between the production and emulator environments.

   The documentation [https://firebase.google.com/docs/functions/firestore-events?gen=2nd#auth-context](here) says "For information about the data available in the authentication context, see..." and links to a page that is not specific to Firebase. That page lists some possible values, but it's not clear what values would be used. The most sensible guess is that authType would be "appuser" or "user" if the document was created from the client-side web SDK, and "serviceaccount" if created from a Cloud Function. But those are not the values used.

   In production, if the document is created from the client-side web SDK, authType is "api_key" and authId is the ID of the logged in user. If it's created from a Cloud Function, authType is "unknown" and authId is the ID of the default service account. Thus it is possible to tell the difference, although since the behavior is undocumented, we can't assume that the behavior won't change.

   In the emulator environment, authType is always "unknown" and authId is always "fake-auth-id@gmail.com". This is inconsistent with the production environment and makes it impossible to tell how the document was created.

   The behavior should be consistent and sensible and well documented.

   When Functions use e.g. onDocumentCreatedWithAuthContext to handle Firestore event triggers, the meaning of event.authType and event.authId are not documented and are inconsistent between the production and emulator environments.

   The documentation [https://firebase.google.com/docs/functions/firestore-events?gen=2nd#auth-context](here) says "For information about the data available in the authentication context, see..." and links to a page that is not specific to Firebase. That page lists some possible values, but it's not clear what values would be used. The most sensible guess is that authType would be "appuser" or "user" if the document was created from the client-side web SDK, and "serviceaccount" if created from a… 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  ·  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

6. Improve Billing Verification and Support for New Firebase Users

   Many new Firebase users face serious issues when trying to activate the Blaze plan due to strict and non-transparent billing verification processes.

   In my case:
   • I attempted to verify my billing using a Revolut card (registered under my name);
   • All payment confirmations were approved through the Revolut mobile app (4–5 times), yet the verification still failed;
   • No clear error explanation was provided, and I had no way to resolve the issue;
   • I tried adding a backup Korean card, but the verification message never arrived in the Korean mobile banking app (SMS also didn’t arrive because my Korean phone number is inactive);
   • After these attempts, my billing account was suspended and my project was blocked.

   Suggested improvements:
   1. Allow users to upload supporting documents to verify card ownership;
   2. Provide clear error messages when billing verification fails;
   3. Prevent automatic suspension after just a few failed attempts — especially when the card is verified by the bank;
   4. Offer a direct way to contact Firebase Billing Support for real-time help;
   5. Add an option to manually request a billing review instead of locking out users.

   This problem affects many developers who are just starting to use Firebase. Without proper verification and support tools, it’s nearly impossible to access key features like Cloud Functions and Hosting. Please consider improving this part of the onboarding process.

   If others have experienced similar issues — please vote for this idea. Let’s make Firebase more accessible for everyone.

   Many new Firebase users face serious issues when trying to activate the Blaze plan due to strict and non-transparent billing verification processes.

   In my case:
   • I attempted to verify my billing using a Revolut card (registered under my name);
   • All payment confirmations were approved through the Revolut mobile app (4–5 times), yet the verification still failed;
   • No clear error explanation was provided, and I had no way to resolve the issue;
   • I tried adding a backup Korean card, but the verification message never arrived in the Korean mobile banking app (SMS also didn’t arrive because my… 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  ·  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

7. Simultaneously adding multiple configurations to a/b-experiment

   I would like to be able to add multiple configurations to experiment a/b at once that have been previously selected or marked. Or create an experiment based on multiple selected configurations.
   Right now, if you add configurations manually, you have to do it one at a time.

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

8. Connect

   Play store

   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

   2 comments  ·  Performance Monitoring  ·  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. Sending arrays as parameters, to allow scaling.

   When building simple select queries in GraphQL (really simple ones), the underlying query is being transformed, sending the values through as parameters.

   As you can use arrays as parameters, that would allow the DBs to scale as it makes this more robust. Without scaling, it will limit production applications form fully investing.

   As an example you run into instances where the select for 50 columns in the schema (a standard employment record, nothing special) is transformed and we end up getting the dreaded 100 parameters error. This is a Postgres issue, but can be avoided.

   The Error for the fun of it:
   @firebase/data-connect: DataConnect (11.4.0): Error while performing request: {"error":{"code":400,"message":"cannot prepare SQL statement ... SQL Error: pq: cannot pass more than 100 arguments to a function","status":"FAILED_PRECONDITION"}}

   When building simple select queries in GraphQL (really simple ones), the underlying query is being transformed, sending the values through as parameters.

   As you can use arrays as parameters, that would allow the DBs to scale as it makes this more robust. Without scaling, it will limit production applications form fully investing.

   As an example you run into instances where the select for 50 columns in the schema (a standard employment record, nothing special) is transformed and we end up getting the dreaded 100 parameters error. This is a Postgres issue, but can be avoided.

   The Error for the fun… 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  ·  SQL Connect (Data Connect)  ·  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. Clickable results in firebase query mode

    When using Firebase UI query mode, the results are not really human readable. I'd like the document ID field to be clickable, taking me to the panel view of that document, so I can see the document in a readable way.

    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

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

11. Hosting should preserve the client's IP address when proxying to Cloud Run

    When using hosting with rewrites to Cloud Run (e.g., routing all requests to /api/** to a Cloud Run container), the clientIp always reflects the IP address of a Google server rather than the actual client’s IP address. As a result, filtering incoming requests by IP address in the logs viewer becomes impossible.
    It would be great if the x-forwarded-for header could be used to populate this field instead.

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

12. Fix GitHub integration

    Issues:

    1. In the app hosting wizard: Connecting a GitHub account that is not the owner of the GitHub repository and then removing it breaks the GitHub integration process and the App Hosting set up process.
    2. Being just a collaborator to a GitHub repo doesn't make it visible in the App Hosting Set Up wizard, you have to connect with the GitHub account of the owner of the repo.

    Error messages:

    1. Connection verification failed: unable to verify the authorization token: GET https://api.github.com/user: 401 Bad credentials []: failed precondition.
    2. Error: Request to https://developerconnect.googleapis.com/v1/projects/PROJECT-ID/locations/europe-west4/connections/firebase-app-hosting-github-oauth:fetchGitHubInstallations had HTTP Error: 400, Failed to list GitHub installations

    I described the issue in detail in this r/Firebase reddit post:
    .

    https://www.reddit.com/r/Firebase/comments/1i1k4ln/firebase_app_hosting_and_github_issue/

    .

    Improvement suggestions:

    1. Don't make the GitHub integration step mandatory as I only wanted to manually deploy at that stage.

    2. Let the user know he needs to be the owner and can't change the "bot-account" later.

    3. Add the ability to remove the account and change to another.

    4. Make it work not only with repos where you are the owner but also to repos where you are collaborator

    5. Add the ability to "Factory reset" a firebase project.

    6. Add the ability to reuse a project ID if it's been deleted already.

    Issues:

    1. In the app hosting wizard: Connecting a GitHub account that is not the owner of the GitHub repository and then removing it breaks the GitHub integration process and the App Hosting set up process.
    2. Being just a collaborator to a GitHub repo doesn't make it visible in the App Hosting Set Up wizard, you have to connect with the GitHub account of the owner of the repo.

    Error messages:

    1. Connection verification failed: unable to verify the authorization token: GET https://api.github.com/user: 401 Bad credentials []: failed precondition.
    2. Error: Request to https://developerconnect.googleapis.com/v1/projects/PROJECT-ID/locations/europe-west4/connections/firebase-app-hosting-github-oauth:fetchGitHubInstallations had HTTP Error: 400, Failed to list GitHub installations

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

13. Request for Biweekly and Monthly Backup Options in Firestore

    Currently, Firestore only supports daily and weekly scheduled backups. We would like to request the addition of both biweekly and monthly backup options. These features would provide greater flexibility for projects where weekly backups are too frequent, but biweekly or monthly backups would better suit our needs.

    Thank you for considering this enhancement to support diverse backup schedules for Firestore users.

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

    Submit Rating

14. Offer no bill in case of small website spam which could cause a houndred dollar bill for no reason.

    When I chose to use Firebase. It was because it was a free database for small webpages with 10 SMS/day. Now, it seems that you changed the terms when I already put a lot of effort into using firebase. Now I need to use a Blaze plan for 10 SMS/day. This means the following: "Now I might get spammed by any hacker using a VNP + a bot". It doesnt matter how much time I spend on setting up anti-spam defense. I could still get spammed and have to pay thousands of dollars right? I have 2 solutions:

    1. You could offer me the previous terms: 10 SMS/day without a pay-as-you go plan.
    2. I use the pay-as-you go plan. But You need to sign a contract or a guarantee that if I suddenly get a 1000 dollar paycheck even though I only have about 1 user/day, I shouldnt have to pay that bill.

    Is this possible? This would make sense for all your small-business customers since firebase WAS a good options for small website startups before.

    regards Melker

    When I chose to use Firebase. It was because it was a free database for small webpages with 10 SMS/day. Now, it seems that you changed the terms when I already put a lot of effort into using firebase. Now I need to use a Blaze plan for 10 SMS/day. This means the following: "Now I might get spammed by any hacker using a VNP + a bot". It doesnt matter how much time I spend on setting up anti-spam defense. I could still get spammed and have to pay thousands of dollars right? I have 2 solutions:

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

    1 comment  ·  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. Use readable date format for email sign-in

    According to
    https://firebase.google.com/docs/auth/web/email-link-auth#default-email
    and
    https://github.com/firebase/firebase-js-sdk/issues/2574
    The email sign in template contains a timestamp in the email title and body, so email are not collapsed into a sigle thread.

    I believe the current date time format, such as 2024 November 11 13:33 UTC is not user friendly, and should be replaced with a more readable format, such as Nov. 11, 2024, 11:33.

    The mail language is already based on the language set in the Firebase Authentication -> Template language section, so the formatting can be done based on the same setting, or a new option can be added in the Firebase Console to select a format.

    According to
    https://firebase.google.com/docs/auth/web/email-link-auth#default-email
    and
    https://github.com/firebase/firebase-js-sdk/issues/2574
    The email sign in template contains a timestamp in the email title and body, so email are not collapsed into a sigle thread.

    I believe the current date time format, such as 2024 November 11 13:33 UTC is not user friendly, and should be replaced with a more readable format, such as Nov. 11, 2024, 11:33.

    The mail language is already based on the language set in the Firebase Authentication -> Template language section, so the formatting can be done based on the same setting, or a new option can be added in the Firebase… 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  ·  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

    Submit Rating

16. Pull Firebase Crashlytics Custom Key values into the slack integration

    It would be very helpful if custom key information could be pulled out of Crashlytics into e.g., the Slack integration.

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

    Submit Rating

17. Make Phone Auth support MFA

    Food delivery services usually need to know the phone number of their customers, to guarantee that the deliveries will be smooth.

    So, a food delivery app would probably prefer authenticating users by phone number rather than by email address.

    Phone auth on its own isn’t particularly secure, though, so it would be nice to allow users to optionally add email authentication as a second factor.

    As of right now, phone auth doesn’t support MFA, though, which means that a food delivery app might want to force users to use email and phone 2FA right away, which might seem intrusive to users, even if you implement anonymous auth and explain why you’re asking for both email and phone.

    Food delivery services usually need to know the phone number of their customers, to guarantee that the deliveries will be smooth.

    So, a food delivery app would probably prefer authenticating users by phone number rather than by email address.

    Phone auth on its own isn’t particularly secure, though, so it would be nice to allow users to optionally add email authentication as a second factor.

    As of right now, phone auth doesn’t support MFA, though, which means that a food delivery app might want to force users to use email and phone 2FA right away, which might seem intrusive to… 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  ·  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

    Submit Rating

18. Allow configuring standard Firebase Authentication via Terraform

    The google Terraform providers allow creating and configuring Firebase projects via Terraform.

    This includes Firebase Authentication via the googleidentityplatform_config Terraform resource, but also forces an upgrade to Firebase Authentication with Identity Platform.

    Identity Platform has a much higher cost.

    We'd like to be able to configure standard Firebase Authentication via Terraform

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

    Submit Rating

19. WearOS support for App Distribution

    WearOS App Distribution feature is recommended, so Firebase can be used for deploying WearOS apps and updates for test users, and even for production/enterprise apps

    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

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

    Submit Rating

20. ai measure

    This is about the Chatbot Gemini Extension

    I'd like to implement a gen-AI feature in my app for general use by the entire organization, but I need a way to monitor and limit how much they use or the cloud cost could spiral out of control. could we have a token count (both prompt and response) in the status map in the transaction document? this way i can keep track of each user's token consumption. with this, it would then be possible to put a reasonable cap on token usage to prevent abuse.

    superb extension by the way. thanks!

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