2019 results found

1. Allows Roslyn to create YoungEnterprises@yahoo.com

   There's always Theft of my Intellectual Properties, and I'm tired of it. I want to be paid for my creations.

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

2. Feedback on "Prototype with AI": Performance Issues, Bug Loops, and File Save Failures on Larger Projects

   Hello Firebase Team,

   --

   Here are a few suggestions to improve the Prototype with AI feature:

   ---

   Problem: On larger projects, the AI becomes slow and often gets stuck on the same bug. It also frequently fails to save code changes, sometimes just adding a blank line to the file.

   ---

   Suggestion 1: Add a "Clear Chat" Button. Please add an option to clear the current chat and its memory. This would allow us to quickly reset the AI when it gets stuck in a repetitive loop, which is a common issue.

   ---

   Suggestion 2: Support for GitHub Projects. Please enable the "Prototype with AI" feature for existing projects imported from GitHub. This would be a huge benefit for developers working on established Firebase applications.

   ---

   These changes would make the tool more robust and useful for ongoing development.

   ---

   Thank you!

   Hello Firebase Team,

   --

   Here are a few suggestions to improve the Prototype with AI feature:

   ---

   Problem: On larger projects, the AI becomes slow and often gets stuck on the same bug. It also frequently fails to save code changes, sometimes just adding a blank line to the file.

   ---

   Suggestion 1: Add a "Clear Chat" Button. Please add an option to clear the current chat and its memory. This would allow us to quickly reset the AI when it gets stuck in a repetitive loop, which is a common issue.

   ---

   Suggestion 2: Support for GitHub Projects. Please enable the "Prototype… 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  ·  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. Feedback, inefficient user experience

   I selected app by react+expo I think (I tried many different things and all have similar issues) one of projects as example was expense tracker

   the prompt was 👇

   Build a mobile-friendly financial management app called Expense Tracker with the following features and technical specifications:

   ---

   Core Features:

   1. Net Worth Management

   Allow users to manually set exact values for three asset categories: cash, bank, and card.

   Support incremental updates (add/subtract) to individual asset categories.

   Automatically calculate and display total net worth in real time.

   Visualize asset breakdown by category using a card or chart.

   1. Expense Tracking

   Let users add expenses by entering:

   Amount

   Description

   Category (e.g., food, transport)

   Source (cash, bank, or card)

   Show a filterable transaction history of all recorded expenses.

   Automatically subtract expense amounts from the selected asset source and update net worth accordingly.

   1. Debtor Management

   Allow users to record loans given to others by entering:

   Amount

   Debtor name

   Description

   Source used for lending (cash, bank, or card)

   Track the status of each debt: paid or unpaid.

   When marking a debt as paid, return the money to the original asset source.

   Allow filtering of debt records based on payment status.

   ---

   Technical Implementation:

   Components Required:

   UpdateNetWorthForm: Dual-mode form for exact values or add/subtract updates per asset category.

   ExpenseForm: Inputs for amount, description, category, and asset source.

   DebtorForm: Inputs for loan details and repayment action.

   NetWorthCard: Displays total net worth and asset breakdown visually.

   TransactionHistory: Filterable list of all expenses.

   DebtorsSection: Display, filter, and manage all debtor records.

   Data Models:

   NetWorth: Holds values for cash, bank, and card, plus total calculation.

   Expense: Stores expense records with source and metadata.

   Debtor: Stores loans, repayment status, and source tracking.

   App Flow Summary:

   1. User sets initial asset values.

   2. When expenses are recorded, assets update based on the selected source.

   3. Loans reduce assets and are logged with details.

   4. When debts are marked repaid, the amount returns to the correct asset source.

   5. Dashboard continuously displays real-time data on assets, expenses, and debts.

   ---

   Additional Notes:

   Ensure forms are validated and handle user input errors gracefully.

   Preserve individual asset values when updating only one category.

   Ensure debtor repayments correctly credit the original asset category.
   ,,,

   That's it. None of my projects on idx made an app honestly all of them get bugs that ruin it .. and Gemini tells many times that she can't do some prompts. Like fixing the Android emulator. Which isn't working at all as shown in ss. I hope you fix it and make it better. And I hope you're aware that almost all users are upset because of bad performance wasn't expected.

   I selected app by react+expo I think (I tried many different things and all have similar issues) one of projects as example was expense tracker

   the prompt was 👇

   Build a mobile-friendly financial management app called Expense Tracker with the following features and technical specifications:

   ---

   Core Features:

   1. Net Worth Management

   Allow users to manually set exact values for three asset categories: cash, bank, and card.

   Support incremental updates (add/subtract) to individual asset categories.

   Automatically calculate and display total net worth in real time.

   Visualize asset breakdown by category using a card or chart.

   1. Expense Tracking

   Let users add expenses by… more

   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

   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

4. AI Fixes One Thing But Breaks Another – Please Improve

   When I ask the AI to fix or adjust something in my Firebase app, it works—but then it changes other things I didn’t ask for. For example, I might want to fix spacing, but it also removes gradients, transparency, or changes the layout.

   Suggestions:

   Let me limit the AI to only the part I want changed.

   Show me what will change before applying it.

   Add an easy undo button.

   Make the AI focus only on what I ask—nothing more.

   This would help a lot and save time. Thank you!

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

5. Program have own stong in phone of creat and have all database to run

   On database and program

   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

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

6. Future

   To grow fast

   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  ·  App Check  ·  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. 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

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

8. add team workspace for enterprise.
   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

9. Create workspace from existing FlutterFlow project

   or import FlutterFlow project into Firebase Studio

   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

10. It must try with other stacks while building it must take the desired language

    It is only generating in typescript it will be better and best to generate in the user desired stack and language

    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

11. Change apphosting region while publishing in Studio

    Change apphosting region while publishing in Studio. Currently if we publish project from Studio, automatically in Firebase App Hosting is created a backend in region us-central1. There is no option later on to change it, or to create a new backend in Firebase AppHosting (with other region) and relate it with publishing from Studio.

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

12. Work

    I'm love work

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

13. Pre-built User Authentication & Common App Features

    We propose adding a suite of pre-built, configurable modules for user authentication and other common application features directly into Firebase Studio. This would allow developers to quickly set up essential functionality without writing repetitive boilerplate code.

    Why this is important: Many developers spend significant time implementing standard features like user registration, login, and profile management. By providing these components out-of-the-box, Firebase Studio would enable developers to skip these steps and focus immediately on building their app's unique and core functionality. This would dramatically accelerate development speed and improve time-to-market.

    Core Features to Include: User Authentication Module: A ready-to-use system for user registration, sign-in, password reset, and social login (e.g., Google, Apple).

    User Profile Management: A common UI for users to view and edit their profile details.

    Role-Based Access Control (RBAC): A simple way to define and manage user roles and permissions.

    This feature would significantly enhance the value of Firebase Studio by transforming it from a data management tool into a comprehensive, rapid application development platform.

    We propose adding a suite of pre-built, configurable modules for user authentication and other common application features directly into Firebase Studio. This would allow developers to quickly set up essential functionality without writing repetitive boilerplate code.

    Why this is important: Many developers spend significant time implementing standard features like user registration, login, and profile management. By providing these components out-of-the-box, Firebase Studio would enable developers to skip these steps and focus immediately on building their app's unique and core functionality. This would dramatically accelerate development speed and improve time-to-market.

    Core Features to Include: User Authentication Module: A ready-to-use system for… 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  ·  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

14. The annimations can be better

    Please Use Codepen.io

    Thanks!

    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

15. Retain Gemini conversation in code mode when switching to and from prototyper

    Right now when I go from code mode to prototyper and back to code mode, any previous conversation in code mode with Gemini is lost and I have to start again. This is really frustrating. Would be better to keep the conversation whenever switching to and from code mode

    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

16. Feedback for Google Firebase Studio

    Hello Firebase Team,

    First of all, thank you for building Firebase Studio – the tool’s integration with Firebase services and backend setup is working well. However, I would like to share some honest feedback based on my experience using it to build web apps.

    🔧 What’s Working Well:
    Firebase services integration is smooth.

    Backend connectivity and authentication flow are reliable.

    Easy to link with Firestore, Auth, and other core services.

    ❌ What Needs Improvement:
    Idea Implementation Feels Basic:

    The concept generation is too plain. When I enter an idea or app concept, I expect the tool to intelligently add related features or modules, but currently, it just scaffolds a basic setup with little depth.

    Tools like Replit AI, Lovable AI, or FlutterFlow give smart suggestions and auto-build useful, customizable components.

    e-Signature Functionality is Weak:

    The eSign part is not intuitive or visually modern.

    Needs better UI for signature capture, downloadable PDFs, and mobile responsiveness.

    Design System & UI Customization is Very Limited:

    It’s hard to make apps look modern or production-ready using default styles.

    Lack of ready-made UI templates, design themes (like material, glassmorphism, or neomorphic).

    No drag-and-drop interface or component styling options.

    No Visual Builder or Live Preview:

    Would be helpful to have a side-by-side live preview that updates in real time as we edit code.

    A drag-and-drop component builder like in FlutterFlow would really boost productivity.

    Lack of AI Assistance or Recommendations:

    A simple idea prompt like “Build a chat app” should suggest login, chat UI, backend structure, etc.

    AI could help with structure setup, security rules, or visual improvements.

    ✅ Suggested Improvements:
    Add smart AI idea-to-feature mapping.

    Improve eSign module with better UX and export options.

    Include modern UI templates and design systems.

    Build visual UI editor and live preview.

    Suggest features & integrations based on app type.

    🧠 Why It Matters:
    Tools like Replit, FlutterFlow, and Lovable AI are helping creators build professional web apps just from an idea prompt. Firebase Studio has a solid backend, but without intelligent frontend and visual tools, it's hard to rely on it fully as a product builder.

    I truly believe with a few upgrades, Firebase Studio can become the go-to builder for both developers and makers.

    Thanks for listening!
    Looking forward to seeing what’s next. 🚀

    Hello Firebase Team,

    First of all, thank you for building Firebase Studio – the tool’s integration with Firebase services and backend setup is working well. However, I would like to share some honest feedback based on my experience using it to build web apps.

    🔧 What’s Working Well:
    Firebase services integration is smooth.

    Backend connectivity and authentication flow are reliable.

    Easy to link with Firestore, Auth, and other core services.

    ❌ What Needs Improvement:
    Idea Implementation Feels Basic:

    The concept generation is too plain. When I enter an idea or app concept, I expect the tool to intelligently add related… more

    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

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

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

18. Error Fixing

    The app is really bad at fixing errors when they occur. Errors that other web development Apps can fix, this app has a hard time fixing or cant fix at all

    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. Plantillas de la comunidad del proyecto IDX <div align="center">Una biblioteca de plantillas para que puedas comenzar más rápido y explorar

    Plantillas de la comunidad del proyecto IDX
    <div align="center">Una biblioteca de plantillas para que puedas comenzar más rápido y explorar herramientas, marcos y tiempos de ejecución.</div>

    

    Nota: Este repositorio es para plantillas no oficiales y no compatibles para espacios de trabajo IDX.

    <a href="https://idx.google.com/import?url=https://github.com/project-idx/community-templates">
    <img height="32" alt="Abrir en IDX" src="https://cdn.idx.dev/btn/open_dark_32.svg">
    </a>

    Agregue su plantilla IDX personalizada

    Project IDX permite a cualquier persona crear espacios de trabajo personalizados mediante plantillas personalizadas (https://developers.google.com/idx/guides/custom-templates). Requiere algunos archivos específicos que indican a Project IDX qué hacer al crear un espacio de trabajo.

    Clona y crea tu propia carpeta

    Primero clona el repositorio y crea tu propia carpeta para tu plantilla.

    clon de git https://github.com/project-idx/community-templates
    mkdir <ruta-de-su-plantilla> && cd $_
    

    Crea los archivos necesarios para la plantilla: idx-template.json y idx-template.nix.

    Pruebas

    Pruebe sus cambios con la CLI de la plantilla o mediante una URL de plantilla como https://idx.google.com/new?template=<github-url>.

    Agregar un botón Abrir en IDX

    Consulta la herramienta "Generador de botones Abrir en IDX" en nuestra documentación.

    Crear una PR

    Una vez que tenga una plantilla probada con un botón Abrir en IDX, cree una PR y solicite revisión.

    Plantillas de la comunidad del proyecto IDX
    <div align="center">Una biblioteca de plantillas para que puedas comenzar más rápido y explorar herramientas, marcos y tiempos de ejecución.</div>

    

    Nota: Este repositorio es para plantillas no oficiales y no compatibles para espacios de trabajo IDX.

    <a href="https://idx.google.com/import?url=https://github.com/project-idx/community-templates">
    <img height="32" alt="Abrir en IDX" src="https://cdn.idx.dev/btn/open_dark_32.svg">
    </a>

    Agregue su plantilla IDX personalizada

    Project IDX permite a cualquier persona crear espacios de trabajo personalizados mediante plantillas personalizadas (https://developers.google.com/idx/guides/custom-templates). Requiere algunos archivos específicos que indican a Project IDX qué hacer al crear un espacio de trabajo.

    Clona y crea

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

20. Boom Boom Dating App
    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  ·  App Check  ·  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