518 results found

1. support kotlin, xml & jetpack compose

   Please add support for Kotlin and Android XML as well as Jetpack Compose because now Jetpack Compose supports multiplatform

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

2. gemini help on main page

   on main page I want to learn how to use idx. to give an example, how can I work on a project which has frontend+backend(api).

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

3. Basic Python support

   For Python (i) Seamless installation of pip (ii) smooth Integration of python libraries without nix (iii)Alternative to nix package manager (iv) better "ms python extension support" , right now now using this extension generates so many errors

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

4. mejorar la capacidad de colaboración en línea

   Poder ver en qué parte del código está editando un colaborador, poder dejar comentarios al estilo de Google Docs. Y poder ver el perfil del usuario que colabora. Sería interesante además agregar en el panel de chat la posibilidad de chatear con los colaboradores. Una integración con Google Chat sería perfecta para enviar notificaciones de DevOps.

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

5. Google colab

   Google Colab is an awesome way to get access to workflows that require a GPU but a Jupyter notebook is not as powerful as working from an IDE.

   This idea would be to allow IDX to open within or attach to a Google Colab VM for a more fully featured development experience for AI applications.

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

6. Be able to run the firebase emulator in IDX

   I love that i can connect to a production firebase environment, but can you make it so i can run my emulators from within IDX? i managed with the firebase-tools to setup everything but i just get an error when doing
   firebase emulators:start

   i  emulators: Starting emulators: auth, functions, firestore
   ⚠  firestore: Error when trying to check port 8080 on ::1: Error: listen EADDRNOTAVAIL: address not available ::1:8080
   ⚠  firestore: Port 8080 is not open on localhost (127.0.0.1,::1), could not start Firestore Emulator.
   ⚠  firestore: To select a different host/port, specify that host/port in a firebase.json config file:
         {
           // ...
           "emulators": {
             "firestore": {
               "host": "HOST",
               "port": "PORT"
             }
           }
         }
   ⚠  hub: Error when trying to check port 4400 on ::1: Error: listen EADDRNOTAVAIL: address not available ::1:4400
   ⚠  hub: Port 4400 is available on 127.0.0.1 but not ::1. This may cause issues with some clients.
   ⚠  hub: If you encounter connectivity issues, consider switching to a different port or explicitly specifying "host": "<ip address>" instead of hostname in firebase.json
   ⚠  ui: Error when trying to check port 4000 on ::1: Error: listen EADDRNOTAVAIL: address not available ::1:4000
   ⚠  ui: Port 4000 is available on 127.0.0.1 but not ::1. This may cause issues with some clients.
   ⚠  ui: If you encounter connectivity issues, consider switching to a different port or explicitly specifying "host": "<ip address>" instead of hostname in firebase.json
   ⚠  logging: Error when trying to check port 4500 on ::1: Error: listen EADDRNOTAVAIL: address not available ::1:4500
   ⚠  logging: Port 4500 is available on 127.0.0.1 but not ::1. This may cause issues with some clients.
   ⚠  logging: If you encounter connectivity issues, consider switching to a different port or explicitly specifying "host": "<ip address>" instead of hostname in firebase.json
   ⚠  auth: Error when trying to check port 9099 on ::1: Error: listen EADDRNOTAVAIL: address not available ::1:9099
   ⚠  auth: Port 9099 is available on 127.0.0.1 but not ::1. This may cause issues with some clients.
   ⚠  auth: If you encounter connectivity issues, consider switching to a different port or explicitly specifying "host": "<ip address>" instead of hostname in firebase.json
   ⚠  firestore.websocket: Error when trying to check port 9150 on ::1: Error: listen EADDRNOTAVAIL: address not available ::1:9150
   ⚠  firestore: Port 9150 is available on 127.0.0.1 but not ::1. This may cause issues with some clients.
   ⚠  firestore: If you encounter connectivity issues, consider switching to a different port or explicitly specifying "host": "<ip address>" instead of hostname in firebase.json
   i  emulators: Shutting down emulators.
   

   I love that i can connect to a production firebase environment, but can you make it so i can run my emulators from within IDX? i managed with the firebase-tools to setup everything but i just get an error when doing
   firebase emulators:start

   i  emulators: Starting emulators: auth, functions, firestore
   ⚠  firestore: Error when trying to check port 8080 on ::1: Error: listen EADDRNOTAVAIL: address not available ::1:8080
   ⚠  firestore: Port 8080 is not open on localhost (127.0.0.1,::1), could not start Firestore Emulator.
   ⚠  firestore: To select a different host/port, specify that host/port in a firebase.json config file:
         {
           //

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

   2 comments  ·  Extensibility  ·  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

7. Manual recovery

   As Project IDX is still in beta, there's a few issue that might result in workspace being stuck in state where it cannot be recovered. For example, I was impacted by
   https://issuetracker.google.com/issues/341319148
   It would be nice if the "Launch Recovery" button will be available, even if the system did not detect any error. Issue like this can be easily be fixed if we can changed the dev.nix file with a manual recovery.

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

8. Allow access to mapped URLs from another workspace, so that a frontend project can talk to a backend (API) project.

   Allow access to mapped URL from another workspace, so that a frontend project can talk to a backend (API) project.

   For instance, https://3000-idx-sermons-nextjs-1723133529534.cluster-hf4yr35cmnbd4vhbxvfvc6cp5q.cloudworkstations.dev/ making requests to https://3001-idx-sermons-backend-1723134362471.cluster-joak5ukfbnbyqspg4tewa33d24.cloudworkstations.dev/api/some-endpoint

   This is presumably possible when it's a client-side request since you'll be logged in to Project IDX, but it's not currently possible for server-side requests - the request gets redirected to the OAuth flow.

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

9. Make Capacitor template

   Make IDX support the capacitor project. Capacitor / ionic is the one of most popular frameworks It would be nice if IDX support

   7 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

   under review  ·  1 comment  ·  Project Templates  ·  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

10. Allow to upload files to idx

    allow the user to upload files like pdf's, csv files which will be helpful for machine learning projects.

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

11. Add Support for common ML and Data analysis workloads

    Development around Machine Learning and/or tools for performing ML should also be considered well, specifically around building tools for ML which do not directly involve training (such as experiment tracking, data analysis, etc.)

    36 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

    2 comments  ·  Project Templates  ·  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
    under review  ·  AdminKirupa (Product Manager, Google, LLC - Project IDX) responded

    This is a great suggestion! We are going to investigate what support here can look like and follow-up with you further for more details.

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

    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  ·  UI / UX  ·  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

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

14. Serverpod

    Certainly! Below is a template you can use to request adding Serverpod to the Google Cloud Index (IDX) platform. Customize it with specific details or additional information as needed:

    ---

    Subject: Request to Add Serverpod to Google Cloud Index (IDX) Platform

    I am writing to request the addition of Serverpod to the Google Cloud Index (IDX) platform. Serverpod is a robust backend framework designed specifically for Dart, leveraging the power of Flutter for its user interface. Given its features and compatibility with modern development practices, I believe it would be a valuable addition to the Google Cloud ecosystem.

    Key Features of Serverpod:

    1. Dart-Based Framework: Serverpod is built using Dart, providing seamless integration with Flutter for creating high-performance, scalable applications.
    2. PostgreSQL Database: It uses PostgreSQL as its primary database, ensuring reliable and efficient data management.
    3. Docker Support: Serverpod can be easily containerized using Docker, facilitating consistent development, testing, and deployment processes.
    4. Cloud Deployment: It supports deployment on various cloud platforms, including AWS and Google Cloud, enabling flexible and scalable infrastructure management.

    Benefits of Adding Serverpod to Google Cloud IDX:

    • Enhanced Developer Experience: Dart and Flutter developers will have a complete, integrated solution for building both frontend and backend components within the Google Cloud environment.
    • Scalability and Flexibility: Serverpod's compatibility with Docker and PostgreSQL ensures that applications can scale efficiently and leverage the full potential of cloud-native services.
    • Comprehensive Cloud Integration: By supporting Serverpod, Google Cloud can attract more developers who are looking for a unified development stack that leverages Google’s robust cloud infrastructure.

    I am confident that adding Serverpod to the Google Cloud IDX platform will significantly benefit the developer community and further enhance the capabilities of Google Cloud services.

    Thank you for considering my request. I am looking forward to seeing Serverpod as part of the Google Cloud IDX platform. Please let me know if you need any additional information or have any questions.

    Certainly! Below is a template you can use to request adding Serverpod to the Google Cloud Index (IDX) platform. Customize it with specific details or additional information as needed:

    ---

    Subject: Request to Add Serverpod to Google Cloud Index (IDX) Platform

    I am writing to request the addition of Serverpod to the Google Cloud Index (IDX) platform. Serverpod is a robust backend framework designed specifically for Dart, leveraging the power of Flutter for its user interface. Given its features and compatibility with modern development practices, I believe it would be a valuable addition to the Google Cloud ecosystem.

    Key Features of… 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  ·  Project Templates  ·  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

15. detection of stress in it employees by using machine learning
    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  ·  Previews  ·  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

16. Monorepo support

    Hello, Just discovering IDX, very exciting product!
    I just set up a repo that is a monorepo, with /backend with a Nest.js server, and a /frontend with an Angular app.

    Is it possible to:
    - Have both running, port 3000 and 8080, and allow each to communicate with each other?
    - Set up monospace.json and specify working_directory for each project listed?

    For the moment, should the monospace.json file live in the root of the repo, or nested at the root of each project?

    29 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

    2 comments  ·  UI / UX  ·  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

17. Should have a way to view the emulator

    Needs a way to re-open the android emulator when it is accidentally closed without having to re-build the app

    32 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

    planned  ·  2 comments  ·  UI / UX  ·  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

18. Laggy and Less Touch Responsive Online Android Emulator

    The current online Android emulator is experiencing significant lag and lacks touch responsiveness, impacting the user experience negatively. This hinders developers' ability to efficiently test and debug their Android applications in a simulated environment.

    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  ·  UI / UX  ·  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

19. NestJs Support

    NestJS, with its modular and scalable architecture, has become increasingly popular in the TypeScript community. Many developers, myself included, have adopted NestJS for its robust features and ease of development. Having the ability to seamlessly integrate NestJS templates into IDX projects would not only streamline the development process but also open up IDX to a larger audience of TypeScript enthusiasts.
    I'd like to see enhanced compatibility with NestJS and TypeScript-based templates.

    12 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

    under review  ·  1 comment  ·  Project Templates  ·  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

20. Native code syntax highlighting with Flutter

    If you're working on a Flutter plugin, which. includes native code (eg Kotlin, Swift) then those files are accurately labeled in the navigator on the left, but syntax highlighting for those languages appears not to work

    29 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

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