Hey, thinking of playing with Amper today - so am gonna post all my queries in this thread :thread: ...

# amper

[theapache64]

Hey, thinking of playing with Amper today - so am gonna post all my queries in this thread 🧵 (i don’t want to flood this nice channel with my stupid queries).. so here we go!!

[theapache64]

I see there are two ways of using Amper
1. Using gradle way
2. Using native way
Which one is more preferred, given that I am targetting to work with Compose Multiplatform project as well as library ?

[theapache64]

---
Second question, I am planning to build a Compose Multiplatform library and I assume the publishing part (to things like mavenCentral, jitpack) works without any extra tricks 😬 - (or let me knw if am going to face some challenge 😬 )

[theapache64]

---
Third question, I see both Fleet and IntelliJ have support for Amper. Which one is more compatible and friendly with Amper?or the support is almost equal ? Do i compromise on any feature if I choose intellij for amper? (asking out of FOMO of missing out some awesome feature 😛 )

[theapache64]

---
Fourth : If i go with native Amper, can I use still use Gradle version catalogs or is there a better way to manage version catalogs in native amper?

[joffrey]

Which one is more preferred, given that I am targetting to work with Compose Multiplatform project

The Gradle-based Amper plugin was meant for us to quickly gather feedback about Amper, but we're mostly focused on the standalone Amper now. This is definitely preferred. So please use standalone Amper unless you're lacking some critical feature (and if you do, please open an issue and let us know in this channel 🙏🏻)

Second question, I am planning to build a Compose Multiplatform library and I assume the publishing part (to things like mavenCentral, jitpack) works without any extra tricks

Amper standalone cannot publish KMP libraries yet, only single-platform JVM libraries. With Gradle-based Amper, you should be able to publish KMP libraries, but it doesn't have all the maven central publication built-in, though. So you still have to configure maven central stuff in your Gradle build files like you would in "pure" Gradle.
We definitely aim at providing a much better out-of-the-box experience for publishing libraries in standalone Amper, but we didn't have the resources to focus on that just yet. We are now going to work on this, please stay tuned! 😉

[joffrey]

@theapache64 I believe you have pretty decoupled questions, and it wouldn't be spam at all if you asked them in the channel so we could start new threads 😉

[theapache64]

Yeah - just realised that’d be better 😄 lemme open threads for 3 and 4

[theapache64]

threads are open - closing this thread

[theapache64]

----

[joffrey]

Nice, thanks!