2369 results found

1. make firebase studio as fullstack developer which can create powerful apps with ai

   In firebase studio ai everybody can create fullstack apps with this ai

   7 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

2. Improve Firebase Auth integration with Server side rendering (Next.js)

   Hey, hi, I’m a Next.js developer, and the only problem I’m having with Firebase is with the Firebase Auth integration. I’d like to see improvements to the documentation for Next.js and its integration with server-side rendering. The problem I’ve encountered is that we need to save the token generated on the frontend to pass it to the backend. And the Next.js documentation recommends creating the token on the backend as “HttpOnly” for better security, but Firebase Auth doesn’t follow this pattern, and there isn’t much documentation about it or how Firebase handles cookie security.

   I hope Firebase will consider my feedback.

   Hey, hi, I’m a Next.js developer, and the only problem I’m having with Firebase is with the Firebase Auth integration. I’d like to see improvements to the documentation for Next.js and its integration with server-side rendering. The problem I’ve encountered is that we need to save the token generated on the frontend to pass it to the backend. And the Next.js documentation recommends creating the token on the backend as “HttpOnly” for better security, but Firebase Auth doesn’t follow this pattern, and there isn’t much documentation about it or how Firebase handles cookie security.

   I hope Firebase will consider my… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Authentication  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Firebase studio built in mod assistant extension

   You guys are a since you guys are sunset firebase studio so please release the extension the Gemini AI assistant code that can work I can send photo and it is understanding and built-in mode there can I can code unlimited so other student I can learn and do my easily just normal your model not powerful one and

   0 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  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. A Key Adjustment to Avoid Errors and Code Loss (Refactoring) in a Firebase Studio Project

   I've been developing a large-scale project using Firebase, still in the experimentation, testing, and evaluation phase of Firebase Studio's functionalities. However, I've observed that small changes made to specific parts of the project end up significantly impacting other areas that shouldn't be affected.

   This behavior creates insecurity in the development process, as minor adjustments end up compromising stable functionalities, even when there's no direct correlation between the modules.

   It's quite frustrating to see that, because of a minimal code flaw, the project can stop working completely—compromising months of work in a matter of seconds. As a safety measure, I've been making several duplications of the project to preserve functional versions. However, this quickly consumes all the contracted space and is not a sustainable solution.

   It would be extremely important to have a mechanism similar to a "restore point" or "rollback," allowing the project to revert to a previous stable state if a critical error occurs. This would guarantee greater security, control, and continuity in development, preventing isolated corrections from compromising the entire system.

   Therefore, I request an evaluation of the possibility of implementing a native internal restoration or versioning feature that protects projects against unexpected failures and minimizes impacts on the development environment.

   For example: when requesting AI to make a correction or adjustment to the code, a copy of the code would be created, the adjustment or implementation would be made, then the changes would be presented to the developer, and once the developer confirms, the functionality would be assigned to the original code, deleting the copy. If something goes wrong, the code would simply be deleted without altering the original structure, so as not to have to create copies of the project occupying server space.

   I've been developing a large-scale project using Firebase, still in the experimentation, testing, and evaluation phase of Firebase Studio's functionalities. However, I've observed that small changes made to specific parts of the project end up significantly impacting other areas that shouldn't be affected.

   This behavior creates insecurity in the development process, as minor adjustments end up compromising stable functionalities, even when there's no direct correlation between the modules.

   It's quite frustrating to see that, because of a minimal code flaw, the project can stop working completely—compromising months of work in a matter of seconds. As a safety measure, I've been… 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

5. Narottam
   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Distribution  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Realtime database, change default tab order

   Reorder the tabs in Realtime DB to prioritize displaying the rules or a landing page before the data.

   New users and analytics management find that loading the Realtime Database section from the web console impacts bandwidth usage for reads. This behavior is not ideal and could be separated from the Realtime Database landing page, especially when editing or inspecting the rules, as it requires loading larger chunks of the database before the user switches tabs.

   13 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

   5 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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