2379 results found

1. Github auto feed to firebase conle backend

   After deployment in firebase studio, app hosting require backend to rollout. However GitHub has to feed firebase console the code in repo. That request is now done manually and can miss critical steps that lead to frustration

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

2. Une fonction pour directement télécharger
   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  ·  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

3. Voice over

   I can give my voice over to control

   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

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

4. Save files to local as zip file

   Please add a feature where we can download the files into a zip files from firebase studio

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

5. Feature Request: One-Click "Export to APK" in Firebase Studio for Educational Projects

   Hello Firebase Team,
   I am an 11-year-old developer building a child safety ecosystem. I use Firebase Studio (Cloud Workstations) because it’s powerful, but it has one big barrier for young students: The Terminal.
   To see my project on a real Android device, I have to use CLI commands, manage hosting, and use third-party wrappers. This is very difficult for 5th-grade students and beginners.
   My Proposal:
   Please add a simple button in the Firebase Studio interface (perhaps under the "Project" menu or a "Build" tab) called "Export as Android APK".
   How it should work:
   User clicks "Export as APK".
   Enters App Name and Package ID.
   Firebase builds the project in the cloud and provides a direct download link or a QR code for the phone.
   This would make Firebase the #1 tool for STEM education and help kids like me build tools for internet safety (like my project for blocking gambling and toxic content) much faster.
   Let's make mobile development accessible to everyone, regardless of their terminal skills!

   Hello Firebase Team,
   I am an 11-year-old developer building a child safety ecosystem. I use Firebase Studio (Cloud Workstations) because it’s powerful, but it has one big barrier for young students: The Terminal.
   To see my project on a real Android device, I have to use CLI commands, manage hosting, and use third-party wrappers. This is very difficult for 5th-grade students and beginners.
   My Proposal:
   Please add a simple button in the Firebase Studio interface (perhaps under the "Project" menu or a "Build" tab) called "Export as Android APK".
   How it should work:
   User clicks "Export as APK".
   Enters App… 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  ·  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. Missing Primitives: Transaction Awareness and Trusted Server Metadata in Security Rules

   Firestore Security Rules currently lack two capabilities that force developers to choose between security, performance, and maintainability.

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

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

   1. No "Middle Ground" for Server-Side Operations Currently, a server must either use the Admin SDK (which results in a full administrative bypass of all rules) or Identity Platform to impersonate a user. There is no way for a server to provide "partial validation" for a request that must still remain failable if it violates standard Rule constraints.

   The Fallout: Current limitations incentivize the use of "shared secrets"—checking for specific plain text properties or "magic strings" within the document data to signal that a server has "blessed" the write. This pattern may be adopted because it is more efficient than the alternatives, but it is brittle and mimics security without the actual structural protection of the Rules engine.

   Use Case Examples
   Relational Integrity (The "Escrow" Logic): A Purchase document must be created if and only if the Product status is simultaneously updated to sold in the same atomic transaction.

   External Validation (The "Verified Invite"): A server validates a one-time invite code against a 3rd-party API and "stamps" the request as valid. The Rules then check this stamp alongside request.auth to ensure the user isn't on a blacklist. The server validates the code; the Rules validate the user.

   State Synchronization (The "Booking Lock"): A user booking a hotel room must create a Booking doc and update the Room availability timestamp in one batch. Without is_transaction, rules cannot prevent "orphaned" bookings.

   Requested Features
   request.is_transaction: A boolean allowing rules to reject non-atomic "partial" updates to sensitive multi-document states.

   request.auth.token.server_assertions: A way for the Admin SDK to attach non-forgeable, temporary metadata to a user-authed request. This allows the server to act as a co-validator without needing a full administrative bypass.

   Appendix: Proposed Rule Syntax Examples
   A. Multi-Document Invariants

   JavaScript
   // Ensure a product status isn't flipped without a corresponding purchase record
   match /products/{productId} {
   allow update: if request.resource.data.status == 'sold'
   && request.istransaction == true
   && existsAfter(/databases/$(database)/documents/purchases/$(request.auth.uid)$(productId));
   }
   B. Co-Validation (Failable Requests)

   JavaScript
   // Server verifies the invite, Rules verify the user identity and blacklist status
   match /workspaces/{workspaceId}/members/{memberId} {
   allow create: if request.auth.uid == memberId
   && request.auth.token.serverassertions.inviteverified == true
   && !get(/databases/$(database)/documents/blacklist/$(memberId)).exists();
   }
   Summary: Firestore needs a way to combine user auth with trusted server assertions and transaction visibility. Without these, secure patterns are significantly harder to implement than unsafe ones.

   Firestore Security Rules currently lack two capabilities that force developers to choose between security, performance, and maintainability.

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

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

   1. … 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  ·  Firestore  ·  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. Gemini in firebase

   I think it would be a great idea to be able to create more one context chat with gemini , with ability to link them together , or merging them.

   Especially while gemini right now in Firebase , is very It is very distracted and does not adhere to instructions and commands and performs actions repeatedly and repeatedly outside the user's control, also it should be made more committed to the instructions and it has not been clearly indicated previously not to do so, for example if you ask to change the color of a button on the site, you will be surprised that it has made several other changes such as changing the size of the button or deleting the text above it.

   I think it would be a great idea to be able to create more one context chat with gemini , with ability to link them together , or merging them.

   Especially while gemini right now in Firebase , is very It is very distracted and does not adhere to instructions and commands and performs actions repeatedly and repeatedly outside the user's control, also it should be made more committed to the instructions and it has not been clearly indicated previously not to do so, for example if you ask to change the color of a button on the site, you… 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  ·  Gemini in Firebase  ·  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. Firebase studio auto generate commit messages

   In code editor view, version control, should have option to auto generate commit messages with gemini

   10 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 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. About entertainment
   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  ·  Cloud Functions for Firebase  ·  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. Instruct the agent to be in the git head of the repository in the appropriate branch

    Instruct the agent to be in the git head of the repository in the appropriate branch, then to read the files it assumes it will edit, I ensure it's using the latest version of everything. This prevents many errors caused by hallucinations like outdated functions in a use case, which leads to wasted time fixing the same problem repeatedly.

    It's also important to tell it to validate that the files exist and are in the correct path. This way, the chain of thought process iterates automatically until it finds the correct files.

    I've been using this method since the update, and my experience has changed dramatically. I use Firebae Studio for about a month, roughly 14 hours a day, so I've really been able to experience the improvement. I hope this helps others.

    Instruct the agent to be in the git head of the repository in the appropriate branch, then to read the files it assumes it will edit, I ensure it's using the latest version of everything. This prevents many errors caused by hallucinations like outdated functions in a use case, which leads to wasted time fixing the same problem repeatedly.

    It's also important to tell it to validate that the files exist and are in the correct path. This way, the chain of thought process iterates automatically until it finds the correct files.

    I've been using this method since the update,… more

    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  ·  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. Make personalizing accsess

    Opprette kontoer for hver enkel bruker

    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  ·  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. Merging projects

    It would be nice to be able to merge projects. If you have multiple apps that may need to communicated to one another and read from the same data base, but you dont want to build a monolith, you should be able to merge the projects in a way that you can build the functionality between the apps so they can all talk to one another

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

13. to many to list but they were added into the app as i was building it and then bam the app stops,3 month later

    I have so many, but then there's the one, when the app stops after the word perfect, one step back button/ from the issue, or remove the 30-day callapse

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

14. Allow users to easily leave or disconnect from Firebase projects they no longer belong to

    When developers change companies or stop collaborating on a project, they often remain listed as members of Firebase projects that they no longer use or have access to.

    Currently, the only way to be removed from a project is for a project owner or administrator to manually remove the user from the project permissions. This becomes problematic when:

    The developer no longer has contact with the project owner

    The company forgets to remove former collaborators

    The user wants to clean up their Firebase project list

    I suggest adding a “Leave Project” or “Disconnect from Project” option directly in the Firebase console for members.

    This feature could:

    Allow users to remove themselves from projects they no longer work on

    Improve security by reducing unnecessary access to company resources

    Help developers keep their Firebase console organized

    Reduce administrative overhead for project owners

    For example, developers who change jobs often still see old company projects in their Firebase dashboard, even though they no longer use them.

    A simple self-removal option would solve this problem in a secure and user-friendly way.

    When developers change companies or stop collaborating on a project, they often remain listed as members of Firebase projects that they no longer use or have access to.

    Currently, the only way to be removed from a project is for a project owner or administrator to manually remove the user from the project permissions. This becomes problematic when:

    The developer no longer has contact with the project owner

    The company forgets to remove former collaborators

    The user wants to clean up their Firebase project list

    I suggest adding a “Leave Project” or “Disconnect from Project” option directly in the Firebase… 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  ·  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

15. Hi Firebase , I need urgent help with Case 10386349. My Firebase project was incorrectly flagged, and my entire Realtime Database is inacces

    Please check

    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

    2 comments  ·  Firestore  ·  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. preview env links support

    currently its needed to deploy the app to firebase hosting AND firebase app hosting to get preview links working, thats making things more complex than needed...

    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 Hosting  ·  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. سهل الربط بالتسلسل بين خدمات غوغل كلاود وطرق الدفع واستقبال الدفعات تحت شاشة مراقبة ضمن صفحة المؤسسة لدى العميل على غوغل وورك سباس

    سهل الربط بالتسلسل بين خدمات غوغل كلاود وطرق الدفع واستقبال الدفعات تحت شاشة مراقبة ضمن صفحة المؤسسة لدى العميل على غوغل وورك سباس

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

18. I would like to import the source code of an existing GitHub repository from Firebase Studio Prototyper Gemini so that I can modify it. This

    I would like to import the source code of an existing GitHub repository from Firebase Studio Prototyper Gemini so that I can modify it. This feature is very useful, so please consider it.

    As a specific example, I would like to import the source code of the following GitHub repository so that I can modify it from Firebase Studio Prototyper Gemini.
    https://github.com/okamoto53515606/homepage

    PS)
    Until the above feature is available, I plan to proceed as follows:
    1. Instruct Firebase Studio Prototyper to create a dummy app (with minimal functionality).
    2. Press the "Publish" button to create app hosting for the dummy app (with minimal functionality).
    3. Open a terminal in Firebase Studio.
    4. In the Firebase Studio terminal, download and unzip the tar.gz file from GitHub.
    5. Run npm install again in the Firebase Studio terminal.
    6. Run "Restart" from Firebase Studio to rebuild your Firebase Studio development environment.
    7. Have prototyper gemini review the contents of the new docs folder and understand the structure of your app.
    8. Ask prototyper gemini to make any corrections.

    I would like to import the source code of an existing GitHub repository from Firebase Studio Prototyper Gemini so that I can modify it. This feature is very useful, so please consider it.

    As a specific example, I would like to import the source code of the following GitHub repository so that I can modify it from Firebase Studio Prototyper Gemini.
    https://github.com/okamoto53515606/homepage

    PS)
    Until the above feature is available, I plan to proceed as follows:
    1. Instruct Firebase Studio Prototyper to create a dummy app (with minimal functionality).
    2. Press the "Publish" button to create app hosting for the dummy… 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  ·  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. Please communicate the following information to Gemini, the prototyper, in advance. Please also provide Gemini with a development preview UR

    Please communicate the following information to the prototyper, Gemini, in advance. Please also provide the development preview URL to the prototyper, Gemini, in advance.

    Firebase Studio Development Environment Workflow and Knowledge

    This document summarizes the knowledge required for AI development partners (App Prototypers) to understand the characteristics of this development environment and work smoothly with users.

    1. Terminal and Command Execution

    Available Command Line Tools

    The following main commands are available in the terminal of this environment.

    • git: Version control
    • gcloud: Google Cloud resource operations
    • firebase: Firebase project operations

    How to Execute Commands

    In dialogue with the user, the AI ​​presents commands to be executed.

    • `bash Markdown: When commands are presented in this format, an execute button (▶) appears in the user interface. The user can execute the command simply by pressing this button.
    • AI Cannot Execute Directly: The AI ​​itself does not have the permission to execute commands directly. The basic workflow is a collaborative one: the user executes a command, communicates the results to the AI, and then proceeds to the next step.

    2. Deployment and URL

    Deployment Flow

    • Pushing to Production: By pressing the "Publish" button in the upper right corner of the UI, the developed application is deployed to Firebase App Hosting and pushed to the production environment.

    Environment URL

    • AI Doesn't Know URLs: By default, the AI ​​does not know the development preview URL or the production URL.
    • User-Provided Information: The user can run a command such as firebase apphosting:backends:list and provide the AI ​​with the URL identified from the command. The AI ​​can then remember that information as context and use it for future development (such as CORS configuration).
    • Example of URL confirmed:
    • Preview URL: https://9000-firebase-studio-*.cloudworkstations.dev/
    • Production URL: URL confirmed using the firebase apphosting:backends:list command

    3. Infrastructure Configuration Workflow Example

    In addition to code, Firebase and Google Cloud infrastructure configuration can also be performed in conjunction with AI.

    1. User specifies the goal: (Example: "I want to securely set the service account's private key as an environment variable.")
    2. AI plans and suggests commands:
    3. Check the account with gcloud iam service-accounts list.
    4. Use gcloud iam service-accounts keys create - ... to output the key to standard output without saving it to a file.
    5. User executes command: Executes the suggested command and optionally provides feedback to the AI ​​with the results.
    6. Continuous Operation Through Collaboration: The AI ​​suggests the next step based on feedback.

    This workflow allows users unfamiliar with commands to safely and accurately configure infrastructure with the assistance of the AI.

    4. Version Control (Git) Workflow Example

    How Auto-Commit Works

    The AI ​​suggests file changes, and once they're applied, the changes are automatically committed to Git. The commit message contains the AI's instructions (user prompts).

    Reverting to a Specific Commit

    You can also revert a project to a specific past state through interaction with the AI.

    1. AI suggests a history check command: The AI ​​suggests a command such as git log --oneline.
    2. User executes a command and shares the results: The user executes a command and shares the displayed commit history with the AI.
    3. User specifies the commit to revert to: The user identifies the commit in the history to which they want to revert.
    4. AI suggests a rollback command: The AI ​​suggests a command to return to a specified state, such as git reset --hard <commit ID>.
    5. User executes a command: The user executes the command, reverting the project's files to a previous version.

    I would like to see the prototyper gemini be able to execute terminal commands directly.
    I would appreciate your consideration.

    Please communicate the following information to the prototyper, Gemini, in advance. Please also provide the development preview URL to the prototyper, Gemini, in advance.

    Firebase Studio Development Environment Workflow and Knowledge

    This document summarizes the knowledge required for AI development partners (App Prototypers) to understand the characteristics of this development environment and work smoothly with users.

    1. Terminal and Command Execution

    Available Command Line Tools

    The following main commands are available in the terminal of this environment.

    • git: Version control
    • gcloud: Google Cloud resource operations
    • firebase: Firebase project operations

    How to Execute Commands

    In dialogue with 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  ·  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. Figure out a way to make menus/options User Friendly - I tried setting up Email Trigger in an APP - maybe I will get it figured out a year f

    Fix the menu process flow for set-up - think like a user instead of a Nerd Progrmmer or enable Gemini to do some work for users

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