{"id":422035,"date":"2023-12-21T12:42:47","date_gmt":"2023-12-21T11:42:47","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=amper&p=422035"},"modified":"2024-08-30T15:23:05","modified_gmt":"2024-08-30T14:23:05","slug":"amper-update-december-2023","status":"publish","type":"amper","link":"https:\/\/blog.jetbrains.com\/de\/amper\/2023\/12\/amper-update-december-2023","title":{"rendered":"Amper Update \u2013 December 2023"},"content":{"rendered":"\n

Last month JetBrains introduced Amper<\/a>, a tool to improve the project configuration user experience. It offers concise, declarative configuration with sensible defaults for common use cases and carefully considered extension points.<\/p>\n\n\n\n

Since then, we\u2019ve received a lot of feedback from the community and have continued our development work as well. In this post, we\u2019ll recap some of the highlights of what we\u2019ve heard from you and talk a little about where we\u2019re headed next.<\/p>\n\n\n\n

Your feedback<\/h3>\n\n\n\n

At this early stage of the project, receiving feedback is of utmost importance, as it helps us build Amper in a way that meets real needs and solves real problems. We\u2019re grateful to everyone who has already shared their thoughts with us, and we hope to hear more from you. Your comments have reaffirmed that the simplicity offered by Amper is indeed something you want.<\/p>\n\n\n\n

We\u2019ve also received a lot of feedback about our choice of YAML as the language of Amper\u2019s module definition files. Rest assured that we\u2019ve taken this feedback to heart. As stated in our initial announcement, this language choice is not final. We\u2019re still evaluating the available options, and we look forward to sharing more on this topic soon.<\/p>\n\n\n\n

New releases<\/h3>\n\n\n\n

Since the initial announcement, we\u2019ve released a few updates, adding support for configuring Kover<\/a> (a community contribution<\/a> from Landry Norris, which we\u2019re grateful for) and delivering bug fixes (AMPER-222<\/a>, AMPER-256<\/a>).<\/p>\n\n\n\n

We\u2019ve also published the source code for the current prototype implementation, which you can now browse in the GitHub repository<\/a> of the project.<\/p>\n\n\n\n

Amper is being actively developed, and we also have other exciting additions coming soon. These include one of the most commonly requested features: support for version catalogs. We\u2019re also working on improved IDE capabilities, such as better typing assistance and code completion in your Amper manifest files.<\/p>\n\n\n\n

How to try Amper<\/h3>\n\n\n\n

If you haven\u2019t tried Amper yet, we encourage you to give it a go and share your thoughts on it with us. <\/p>\n\n\n\n

To get started, open your project in the latest version of IntelliJ IDEA or Fleet, and follow the setup instructions<\/a>. You can also take a look at the tutorial<\/a>, sample projects<\/a>, and documentation to learn more.<\/p>\n\n\n\n

Explore the docs<\/a><\/p>\n\n\n\n

A good approach for trying Amper in your own project is to create a separate branch where you replace your existing configuration with Amper modules. You can see this in action in our KMP app template repositories with shared Compose Multiplatform UI<\/a> and with native UI implementations<\/a>, which now have separate branches configured with Amper.<\/p>\n\n\n\n

For example, here\u2019s how the shared module of the template with native UI was converted from the original build file to its new module manifest that uses Amper.<\/p>\n\n\n\n

\"\"
Before \/ after converting a shared KMP module in the template project<\/figcaption><\/figure>\n\n\n\n

Because Amper offers interoperability with Gradle<\/a>, you can still use Gradle plugins and write custom Gradle tasks if necessary. For example, the module above uses this interop to include the Gradle plugin for SKIE<\/a> in the project. You also have the option to keep the file layout<\/a> that Gradle projects use to simplify migration.<\/p>\n\n\n\n

To provide feedback about your experience, join the discussion in the #amper channel<\/a> on the Kotlin Slack, or share your suggestions and ideas in an issue on YouTrack<\/a>. Your input will really help shape Amper\u2019s future, and we look forward to hearing from you.<\/p>\n\n\n\n

Join the Slack channel<\/a><\/p>\n\n\n\n

More resources<\/h3>\n\n\n\n