Hello, I am wondering if reducing dependence on Gradle will be one of the future goals of Amper?

Will Amper enter the alpha or beta stage this year? I'm curious about how long it will take until there is a version that can be integrated into IntelliJ IDEA and used in a production environment. Gradle is so frustrating.

Hello, I was pondering about what it takes to support Maven Central library publishing in Amper… What are the notable challenges? Is it adapting to Maven Central specific, like zips, GPG signing requirements, etc? Is it allowing to inject publishing secrets? Is it defining a way for lib authors to configure POMs? Is it Gradle metadata support for KMP libs? Is it Android specific things? Other things?

Is there any eta for wasm (and compose-web) support yet?

Hello, does anyone have a trick to import an iOS dependency on standalone? Cocoapods is not supported yet and was wondering if you had an example of how to do it manually for now.

Hi! First of all, thanks for building Amper and providing a way out of the pit of despair that is Gradle 🎉 I find the simplicitly of defining modules, a more sane project folder structure etc to be just lovely so far. Question: Is there (currently) a way to publish locally and use said packages in another, separate Amper project?

Followup: Should we expect a more fleshed out ui for the IntelliJ plugin further down the line? Hoping for something similar to the Gradle pane (sync, build, clean, publish, other tasks, run for specific module etc. ) I understand we are in very early stage so this isn’t impatience, I just think this will be very important for team adoption.

Hi, I'm getting this error while trying to add compose-sonner library in amper module.yaml file

Dependency io.github.dokar3:sonner:0.3.8 depends on io.github.dokar3:sonner-android:0.3.8 which has the following problem:

Module io.github.dokar3:sonner:0.3.8 depends on androidx.compose.ui:ui-tooling-preview, but its version could not be resolved. Attribute version is not defined

Once Amper supports extensibility, will there be a way to mark some sources as generated, and a programmatic way to know if a source set or file is generated? Tools like Detekt will be better with it (it's not supported in Gradle, BTW)

Does amper not support plugins yet? Only some blessed ones like Spring, Ktor, Lombok, etc?

Hey 👋, another question about the KMP IntelliJ Plugin and Amper 😅 About compose previews in compose multiplatform shared modules, is this something planned? Based on this we have >

@Preview

working in common code (you need an Android target for that) Which works fine for compose multiplatform gradle projects. But I think with the current Amper structure this might not be possible:

Platforms [iosArm64] are not supported by the library org.jetbrains.compose.ui:ui-tooling-preview:1.8.0

Supported platforms: [android, jvm]

If I add that dependency only to android/jvm, it's gonna be available only in their respective source folders (as expected). Or am I setting up something wrong?

Hi. I'm trying to use allDrawableResources as part of KMP, but that seems to only work with Gradle build, not Amper build. See https://youtrack.jetbrains.com/issue/CMP-4880 and https://www.jetbrains.com/help/kotlin-multiplatform-dev/compose-multiplatform-resources-usage.html#compose-multiplatform-resources-as-android-assets. Any pointer here? Is that a missing feature, should I add a ticket in Youtrack?

How does Amper integrate with Intellij Autocomplete and other features? Does it use BSP?

Hey, I am playing with Amper. The DevXP is pretty nice. Looking forward to see the upcoming plugin mechanism to get a better idea of what it will look like. Not sure if it has been already discussed, and I am not a native english speaker, but my first surprise/friction is this

product

term. Looks a bit weird to me, could somebody explain the reasoning behind the choice of that word ? I am also a bit confused by the mix of camel case and

-

separators. Do you plan to continue mixing both, and if yes with which rules? Do you plan to provide Yaml schemas that could be used easily by other IDEs to provide basic autocomplete and documentation?

Will be there a way to declare build configuration variables? Something similar to the BuildKonfig plugin in Gradle? Ideally, the variables should be accessible from common code, or scoped to a specific target if needed. It should also support multiple flavors/environments—like dev, prod, test, etc.

Some Feature Suggestions: 1. Posibility to define IDEA

packagePrefix

pattern (similar to gradle idea plugin: https://github.com/JetBrains/gradle-idea-ext-plugin/wiki#package-prefix ) 2. Similarly, to define module name pattern. Example below - We have multiple modules, and each module is split into

contract

(interfaces) and

service

(implementations), e.g.

manager/sales/contract        # package manager.sales.contract
manager/sales/service
engine/pricing/contract
engine pricing/service        # package engine.pricing.service
resource/orders/contract 
resource/orders/service

Currently with Amper i get collisions in my experiment project (multiple projects named

contract

) and had to modify the folder structure in order to build the project as a whole. I guess these both are more candidates for plugins / extensions since potentially this is more programmatic than plain yaml if you want to let the user define this project-wide. Another approach could be having the user define things like packagePrefix, module name, artifact name in each project explicitly

Hi. is it possible to use jvm lib in shared if I target only jvm and android?

HI. I triedto create new project in Intellij, have not changed anything but ios app does not run

when using bom the IDE should not warn me about schema validation, right?

is it possible to see Compose previews in shared module?

Hello, definitely the wrong channel, but not sure about the right one… anyway, I can't vote for Kotlin YouTrack issues anymore. I really wonder what happened, and it's driving me a bit crazy.

Hi, not sure if I should ask here, but for some reason I can not use collectAsStateWithLifecycle in JVM app. It works in Android target.

Is it possible to add Crashlytics to app?

how to build APK? in docs it says that it can be done via build command, but this builds every target and then fails on iOS (not important for me now)

mkay, I'm a bit lost here. newest IntelliJ, JVM 21/Temurin, MacOS: 1. create new project, kotlin/amper/jvm console (product: jvm/app), let's name it "autocloseable" or whatever 2. check amper wrappers that it is 0.7.0 3. replace content of main.kt with

import java.net.http.HttpClient

fun main() {
    val client: HttpClient = HttpClient.newHttpClient()
    client.close()
}

Nothing suspicious here, usual code, right? 4. Run main.kt (from IntelliJ, or via

./amper run

00:01.810 INFO  :autocloseable:compileJvm Compiling module 'autocloseable' for platform 'jvm'...
00:02.974 ERROR :autocloseable:compileJvm e: file:///Users/jakub.g/personal/jakub-gwozdz/autocloseable/src/main.kt:5:12 Unresolved reference 'close'.

ERROR: Task ':autocloseable:compileJvm' failed: Kotlin compilation failed:

e: file:///Users/jakub.g/personal/jakub-gwozdz/autocloseable/src/main.kt:5:12 Unresolved reference 'close'.
16:08:04: Execution finished 'run -m autocloseable --main-class MainKt'.

How. How is it possible that

<http://java.net|java.net>.http.HttpClient

, which obviously is

AutoCloseable

, yields this error for me? Someone please confirm or deny this 🙂

Hi. can you guys add this panel for Amper as well?

You guys asked for some feedback in a presentation on YouTube yesterday, so here we go: I really, really want to adopt Amper, but I am entirely blocked by a lack of support for two things: - Kotlin JS / Web targets (https://youtrack.jetbrains.com/issue/AMPER-221) - As an aside, can you guys please upgrade from WebPack to Vite and fix the double-build problem? The Vite plugin found at https://opensavvy.dev/libraries/gradle/vite.html is frankly much better than using the default Gradle tooling at the moment. - Library targets - Ideally include publishing to a private repository (S3), but if I have to manually script uploading some files I'll be fine. I have custom tasks I need to run, and some things I extend Gradle to do, but I can always separately script and run those. The extendability of Amper in that sense is actually less important to me. In addition, if automatically rebuilding at least for web isn't there, then for convenience's sake I might stay away from Amper. That feature is too nice to leave behind.

Hi. I should see an option to generate actual declarations here, right?

Im not able to reference expected class.

Sometime ago I published a library with Amper and used.

settings:
  kotlin:
    languageVersion: 2.2

now when I try to consume it from a Gradle project, the build fails