Issue Checklist
Additional terms
Feature description
Currently, the "New project" screen provides a fixed set of predefined templates (such as Empty Activity, Basic Activity, etc.).
I am requesting a feature that allows users to create, import, and manage fully customizable project templates. The default templates often include outdated Gradle distribution versions, legacy Android Gradle Plugin (AGP) versions, or older AndroidX libraries that do not align with the developer's current preferences.
Adding support for custom templates would allow developers to define their own starter kits, complete with adjustable library dependencies, pre-configured resources, and bundled common Java utilities.
Use Case
When starting a new project, developers usually have a preferred project structure, specific library versions they rely on, and a set of boilerplate utility classes they reuse frequently.
Instead of generating a project from the default templates and spending unnecessary time manually updating Gradle build files, modifying AGP versions, and copying over standard utilities, a developer could simply select their own custom template. For example, a user could create a "Personal Starter Kit" template that already includes the latest AndroidX libraries, their preferred Gradle configuration, and a predefined folder structure, allowing them to start coding their core logic immediately.
Benefits
- Increased Productivity: Eliminates the repetitive and time-consuming process of manually updating Gradle/AGP versions and restructuring basic project setups every time a new project is created.
- Developer Flexibility: Empowers users to tailor their starter projects to their specific workflows, such as including custom Java utilities or tailored UI resources right out of the box.
- Future-Proofing: Users are no longer restricted to the specific library versions shipped with the app's default templates. They can independently maintain their own templates with the latest dependencies.
Issue Checklist
Additional terms
Feature description
Currently, the "New project" screen provides a fixed set of predefined templates (such as Empty Activity, Basic Activity, etc.).
I am requesting a feature that allows users to create, import, and manage fully customizable project templates. The default templates often include outdated Gradle distribution versions, legacy Android Gradle Plugin (AGP) versions, or older AndroidX libraries that do not align with the developer's current preferences.
Adding support for custom templates would allow developers to define their own starter kits, complete with adjustable library dependencies, pre-configured resources, and bundled common Java utilities.
Use Case
When starting a new project, developers usually have a preferred project structure, specific library versions they rely on, and a set of boilerplate utility classes they reuse frequently.
Instead of generating a project from the default templates and spending unnecessary time manually updating Gradle build files, modifying AGP versions, and copying over standard utilities, a developer could simply select their own custom template. For example, a user could create a "Personal Starter Kit" template that already includes the latest AndroidX libraries, their preferred Gradle configuration, and a predefined folder structure, allowing them to start coding their core logic immediately.
Benefits