2064 results found

1. Mobile support

   The browser should be mobile-friendly. I can barely zoom in and zoom out on mobile, it would be great if it was a bit optimized

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  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. Add a ferture to create virtual environment with specific version of python

   This feature will allow users to easily create isolated virtual environments on their system within project idx. Users can specify the desired Python version during environment creation. This ensures project dependencies are managed effectively and avoids conflicts with system-wide Python installations.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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

3. In all SDKs for node and web implement industry best practice error reporting and error codes

   I have been working on multiple projects that use Firebase, I use the Firebase JS SDK and the Firebase Admin SDK. And I am always pulling my hair out with the error reporting and the ability to handle in the SDKs returned errors. This is especially annoying when using TypeScript.

   There is also no master list of all error codes that an SDK can produce. That means I can get random error that I have to back trace to then add handling for it. Also I have to infer types all the time instead of using instanceof to check if it is an SDK error and get TS support.

   1. Please document all the error codes that each SDK could produce.

   2. Add a page to the documentation site about Error handling in the SDK (helps to explain how it works in this SDK if not very obvious)

   3. Please add a proper typescript Error object to the SDK. This would be a class that extends Error object and for the code property has all the possible codes it can produce. By doing this, the developers will be required to add to the list of error codes that the SDK has on the error if they add a new code when then trigger the error handling code. This means that users as they upgrade get more options in the SDK that they can use to see the new error types that have occurred.

   4. Contribution policy on the GitHub library that describes the error handling approach that has been placed and the expectations that are required for future code inclusion. This stops this from going backwards.

   99/100 I want the error code only and adding either or both would save 100s of hours of hair pulling (I don't want to look like Frank van Puffelen to soon).

   I acknowledge that this has been partially done, but an overhaul that finishes it would be much appreciated.

   I have been working on multiple projects that use Firebase, I use the Firebase JS SDK and the Firebase Admin SDK. And I am always pulling my hair out with the error reporting and the ability to handle in the SDKs returned errors. This is especially annoying when using TypeScript.

   There is also no master list of all error codes that an SDK can produce. That means I can get random error that I have to back trace to then add handling for it. Also I have to infer types all the time instead of using instanceof to check if… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  SDKs  ·  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 Angular Internationalization

   At this point the build fails because of the error:

   Output directory is not of expected structure

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

5. Convenient File Manager in Mobile

   The interface should be more practical to see on mobile.

   I propose that at least, taking into account the limitations of cell phones at the

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   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

6. Public IDX Template Submission

   Public IDX Template Submission

   Summary:

   Introduce a feature to allow the public to submit open-source contributions to the IDX platform through a simple and streamlined process using a GitHub link. This feature aims to encourage community contributions and enhance the platform's template repository.

   Details:

   1. Feature Name: Public IDX Template Submission

   2. Description:

      • Create a public interface where users can submit new templates to the IDX platform.
      • Allow users to submit their templates by providing a GitHub repository link.
      • Submitted templates should be reviewed and, if approved, added to the IDX platform’s template view.

   3. Goals:

      • Encourage community engagement and contributions.
      • Expand the variety and number of templates available on the IDX platform.
      • Simplify the process for submitting and reviewing new templates.

   4. Key Components:

      • Submission Form: A web form where users can enter their GitHub repository link and additional details about their template.
      • Review Workflow: A process for reviewing submitted templates to ensure quality and compatibility with the IDX platform.
      • Template Integration: Mechanism to integrate approved templates into the IDX template repository and make them available to users.

   5. User Flow:

      • User visits the Public IDX Template Submission page.
      • User fills out a form with the GitHub link to their template repository and other required information (e.g., template description, author details).
      • Submission is reviewed by the IDX team.
      • Approved templates are added to the template view and made publicly available.

   6. Technical Requirements:

      • Form Validation: Ensure the GitHub link and other inputs are valid.
      • Repository Access: Ability to clone and test the GitHub repository to verify the template.
      • Automated Tests: Run automated tests on submitted templates to ensure they meet quality standards.
      • Approval System: An interface for the IDX team to review and approve/reject submissions.
      • Notification System: Notify users about the status of their submission (e.g., received, approved, rejected).

   7. Mockup:

   Public IDX Template Submission Page:
   ```

   ---

   | Public IDX Template Submission |

   ---

   | Submit your open-source template to the IDX |
   | platform. Provide the GitHub link to your |
   | repository and fill out the required details.|

   ---

   | Form: |
   | [GitHub Repository Link] ___________________ |
   | [Template Description] ___________________ |
   | [Author Name] ___________________ |
   | [Submit Button] |

   ---

   
   8. **Potential Challenges**:
      - Ensuring the quality and security of submitted templates.
      - Managing the review process efficiently as submission volume increases.
   
   #### Additional Information:
   
   - **Link to GitHub Repository**: Users should submit the repository link in the following format: `https://github.com/user/repository`
   - **Submission Guidelines**: Provide clear guidelines on what makes a good template and the criteria for approval.
   - **Community Engagement**: Consider creating a forum or discussion board for users to discuss and share ideas about templates.
   

   Public IDX Template Submission

   Summary:

   Introduce a feature to allow the public to submit open-source contributions to the IDX platform through a simple and streamlined process using a GitHub link. This feature aims to encourage community contributions and enhance the platform's template repository.

   Details:

   1. Feature Name: Public IDX Template Submission

   2. Description:

      • Create a public interface where users can submit new templates to the IDX platform.
      • Allow users to submit their templates by providing a GitHub repository link.
      • Submitted templates should be reviewed and, if approved, added to the IDX platform’s template view.

   3. Goals:

      • Encourage community engagement and… more
   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

7. Remote Config should be protected from man in the middle attacks

   Currently Remote Config can be sniffered and there is no option to configure protection from "man in the middle attacks" in client side.
   The best solution is to add support of Certificate Transparency.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  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. Could you provide templates for NestJS?

   NestJS, celebrated for its modular architecture, has gained widespread acclaim in the TypeScript community. Many developers, myself included, opt for NestJS due to its robust features and development ease. Integrating NestJS templates into IDX projects would streamline development and attract a broader audience of TypeScript enthusiasts. I'm eager to see enhanced compatibility between NestJS and TypeScript-based templates.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  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. I need a way in Google Cloud to redirect the public URL of jpeg files of my bucket to a Google Function endpoint for checking headers

   https://storage.googleapis.com/bucket/folder/file.jpg

   This is an example of a jpeg file in my Firebase Storage. A lot of websites are using my images illegally. I need a way to add a background check and process behind each access to the images... In PHP it is easy to do because the script can deliver the image, but here ? I don't know. I need a check on the headers of the website hosting the image, if the header referer is not OK, I want to redirect to an image saying that the real image is not available, or a 403

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Cloud Storage for Firebase  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Wilcard Subdomain support documentation

    It seem to be already available (scr: https://www.youtube.com/watch?v=qyhdKb8liEA), can you update the documentation so we have DNS exemple for that.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

11. IDE like lego

    This like lego just pickup few templet and build project. but forget lego build only toy car not real car

    This not IDE. If better to use notepad++ instead to use this. First come out mentality of google. In search result, Android, YouTube and etc. In all of this user has few access its necessary because most of user don't know consequence of give him access so you take responsibly its ok but in dev you understand that not normal user.

    For example, window OS when you delete file ask permission and send to recycle bin also you don't delete system file. In Linux just single cmd entire disk erase.
    why they chose different approach because they know which they target
    if give normal user access cmd like rm In window what happen you understand

    I use google colab but what make no sense if not access to terminal in it
    First of all you clear your vision you make serious Dev tool or just rewrite history with another failure

    that IDE need to lot of improvement
    For case study use replit.com that far better than your IDE
    your IDE use vs code it make no sense to better it

    If you serious about it than create IDE and public resp ask dev to improve this IDE
    second not take charge for all thing. dev know what they do if you just provide resource for dev not provide workspace. they need they create they need template they create it
    you provide recourse and environment there build what they want to build you don't tell them what they build what they dont build

    This like lego just pickup few templet and build project. but forget lego build only toy car not real car

    This not IDE. If better to use notepad++ instead to use this. First come out mentality of google. In search result, Android, YouTube and etc. In all of this user has few access its necessary because most of user don't know consequence of give him access so you take responsibly its ok but in dev you understand that not normal user.

    For example, window OS when you delete file ask permission and send to recycle bin also you don't delete… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

12. SSR support in the sdk

    Support SSR from frameworks like Nextjs in the SDK. Currently, the web sdk can only be used in client side components, severely complicating the codebase vs something like supabase which has support already baked in

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  SDKs  ·  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. Secrets manager for API keys

    It would be nice if we can store API keys in dedicated area as the only current solution is putting them in code or env variable in dev.nix, which isn't prefered, as I would prefer put the dev.nix into git along with the code. This might also help if multiple user collaboration is ever implemented, each user can have their own API keys. Thanks!

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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

14. Sort screen rendering traces by impact

    Currently, the screen rendering trace tool displays a list of issues, but with many items, it becomes overwhelming to sift through and identify the most significant problems.

    Specific Challenges

    • Volume of Data: With many items in the trace list, manually identifying high-impact issues is impractical.
    • Lack of Prioritization: The current list does not prioritize issues based on their impact, making it difficult to focus on what matters most.
    • Efficiency: Developers need a way to quickly pinpoint and address the most significant rendering issues to improve application performance.

    Proposed Solution

    Introduce an "Impact Sort" option in the screen rendering trace tool. This sorting method will prioritize issues based on the formula: frozen frames * number of samples. By calculating the total frozen frames a given issue causes across the installed base, this option will provide a clear insight into which issues are most detrimental to performance.

    Currently, the screen rendering trace tool displays a list of issues, but with many items, it becomes overwhelming to sift through and identify the most significant problems.

    Specific Challenges

    • Volume of Data: With many items in the trace list, manually identifying high-impact issues is impractical.
    • Lack of Prioritization: The current list does not prioritize issues based on their impact, making it difficult to focus on what matters most.
    • Efficiency: Developers need a way to quickly pinpoint and address the most significant rendering issues to improve application performance.

    Proposed Solution

    Introduce an "Impact Sort" option in the screen rendering trace tool.… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

15. Static file apps support for App Hosting

    Allow Firebase App Hosting to host static files app, similar to Firebase Hosting.

    This would allow any web framework to work with App Hosting (without server-side rendering) without official support from App Hosting.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

16. White-label ssl for saas

    We host a whitelabel incident tracker and need the ability to use a customer domain. We currently use cloudflare ssl for saas with cloud run and load balancer

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

17. Add an argument that automatically chunks cloud function deployments according to the maximal possible quota

    When deploying multiple cloud functions at once via

    firebase deploy --only functions

    we frequently run into quota issues like:

    • functions: got "Quota Exceeded" error while trying to update projects/.... Waiting to retry...

    It never retries though.

    It would make it way easier if you could add an argument to the deployment command like:

    firebase deploy --only functions --chunked 50

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Cloud 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. CORS Error with GoogleIDX in Express.js Project

    'm encountering a CORS error when using GoogleIDX in my Express.js project. My application can't access https://workstations.cloud.google.com/devshell/gateway/oauth due to CORS restrictions.

    Enabling CORS on the server is preferred over a proxy server. I'm using express and cors with the following code (example provided if needed).

    I've also tried adding the Access-Control-Allow-Origin header but without success.

    Could you investigate and suggest solutions?

    Thanks,
    Kartik Kumar

    Additional Information (Optional):

    Error Message: GET https://workstations.cloud.google.com/devshell/gateway/oauth?... 403 (Forbidden)
    Using latest express and cors versions.
    This removes extra spaces while keeping the content concise.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  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. Positive Feedback with Question on GitHub Integration

    Dear Google IDX Team,

    I'm writing to express my enthusiasm for Google IDX! As a developer working on a low-end PC, IDX's cloud-based development environment is a game-changer. It's significantly improved my development speed and eliminated the need for a powerful local machine.

    However, I encountered a hurdle while trying to integrate Git and GitHub with IDX after creating a project. I searched extensively on Google, YouTube, and even attempted various solutions myself, but couldn't find a clear explanation.

    Here's my specific question:

    After creating a project in IDX and making code changes, how can I effectively utilize Git and GitHub for version control and pushing those changes to my GitHub repository?
    Any clarification or instructions on this aspect would be greatly appreciated.

    Overall, Google IDX is a fantastic tool with immense potential. Thank you for developing such an innovative solution!

    Sincerely,

    Kartik Kumar

    Dear Google IDX Team,

    I'm writing to express my enthusiasm for Google IDX! As a developer working on a low-end PC, IDX's cloud-based development environment is a game-changer. It's significantly improved my development speed and eliminated the need for a powerful local machine.

    However, I encountered a hurdle while trying to integrate Git and GitHub with IDX after creating a project. I searched extensively on Google, YouTube, and even attempted various solutions myself, but couldn't find a clear explanation.

    Here's my specific question:

    After creating a project in IDX and making code changes, how can I effectively utilize Git and… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  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. Manual reloading of firebase functions in emulator

    I'm suggesting this feature of nodemon:

    https://github.com/remy/nodemon?tab=readme-ov-file#manual-restarting

    Sometimes when inner dependencies changes, firebase emulator don't detect changes. So whenever I make a change in my large project, I have to always shutdown firebase emulator and restart it.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating