Feature Request: Support Standard Gradle Projects and Build Configuration

[ShafiqulIslamShamim]

Currently, CodeAssist uses its own build system instead of reading the standard Gradle project configuration. Because of this, projects are not fully compatible with Android Studio.

For example:

• Importing an existing Android Studio project into CodeAssist may fail or require manual changes.
• A project created in CodeAssist may not work correctly when opened in Android Studio.

This makes it difficult to move projects between the two environments.

Feature Suggestion

Please consider adding support for reading standard Gradle build files, such as:

• "settings.gradle" or "settings.gradle.kts"
• "build.gradle" or "build.gradle.kts"
• "libs.versions.toml"
• Gradle wrapper configuration

CodeAssist could read these files and use the existing project configuration instead of relying on a separate build system.

Benefits

• Full compatibility with Android Studio projects.
• Projects can be opened in CodeAssist without modification.
• Projects created or edited in CodeAssist can be opened directly in Android Studio.
• Developers can switch between desktop and mobile development without migration issues.
• Better compatibility with existing Android libraries, plugins, and Gradle features.

I believe this feature would greatly improve the developer experience and make CodeAssist a much more powerful Android development environment.

Thank you for your amazing work on this project.

[vayamsrijanambykrishna]

It has these, in past versions, now it is a new initiative.

[ShafiqulIslamShamim]

Thanks for the reply.

Just to clarify, I'm not asking CodeAssist to use Gradle as its build system.

What I mean is that when an Android Studio project is imported, CodeAssist could parse the Gradle configuration files (dependencies, plugins, SDK versions, and other build settings) and convert them into its own internal build configuration.

The actual build can still use CodeAssist's own build system. The Gradle files would only be used as a source of project configuration.

Also, when exporting a project, it would be great to have an option to generate/write the corresponding Gradle files from CodeAssist's internal project configuration. This would allow the exported project to open directly in Android Studio or be built using standard Gradle-based tools, including GitHub Actions workflows.

This would provide seamless interoperability between CodeAssist and the standard Android ecosystem while allowing CodeAssist to keep its own build system.