A modern programming language that makes developers happier.

kotlinlang

<https://jakewharton.com/a-jetpack-compose-by-any-other-name/>

*Anyone else here think there should be some sort of name change?*

:thumbsup:  or :thumbsdown:

Personally, I've talked to people about Jetpack Compose and they find "Jetpack" to be weird. I think I'm only "okay" with it because I've grown used to "jetpack" as a term that we use when talking about android dev. "Jetbrains Compose" for desktop could also be confusing. I think just having Compose (and saying that its available for Android and desktop) is easiest when talking about the UI, and the compiler and runtime could probably just be renamed. Seems like that would be the least amount of friction.

The runtime and compiler are two sides of the same coin. You cannot rename one without the other.

Compose UI is just a shit name. Compose UI is just one of infinite possible libraries built on Compose compiler/runtime. It should be named something else. The point of the post was to outline that it's probably too late for that, despite being the right thing to do.

You absolutely should not name _anything_ compose-&lt;platform&gt; such as compose-web or compose-desktop or compose-android because what toolkit are you targeting?

For web is it the HTML DOM or WebGL or SVG or something else? Hell, is it even targeting Kotlin/Js or Kotlin/Wasm?

For desktop is it the skia-based material implementation? Is it platform widgets? Is it Qt widgets? Something else?

For Android is the skia-based material implementation? Is it platform widgets? Is it the legacy view tree? Remote views? Something else?

Name it either with an arbitrary name if it ships its own toolkit or name it for the platform-specific toolkit that it targets.

Dang it. That makes a lot of sense.

should be say `compose-dom` for a lack of a better name, `compose-skia` `compose-webgl` `compose-svg` `compose-qt` e.t.c?

and the compiler/runtime get its own name. Yeah, makes perfect sense to me

And although it is late, better late than never.

one of the reason of putting in alpha is knowing things are likely to change no matter how late. If it is still in alpha, it can change

My vote is for `KotlinUI` because `SwiftUI` got here first, and there’s little reason to not be consistent across the entire mobile ecosystem

also swiftui wasn't first. the compose codebase dates back ~4 years at this point

Well React was first. SwiftUI is already super stable and on its second major release, so I don’t think looking at a repo creation date is the right yardstick. It’s first by just under a year and a half (and counting)

Is Jake’s point that SwiftUI is a dumb name?

No, KotlinUI is dumb name. Provided it can be used in different platform using different technologies i.e. DOM, QT, SVG, WebGL e.t.c

there's also many UI frameworks for Kotlin. It is no more KotlinUI than any other means of displaying UI. I'm fine with it being KotlinGoogleMaterialUI though, since that's what it is.

<@ULERY2F70> are you saying Jetpack Compose will target multiplatform like DOM / SVG etc and Kotlin won’t be involved at all? Or are you referencing Kotlin Multiplatform?