Currently, the packages name are in

androidx.compose.*

format? Will this change in future>?

I think Jake Wharton's article on naming comes to mind here as well and has a lot of community support. This seems highly related and probably worth discussing again in whatever format those discussions happen.

Who looks at imports? 😛

✋

Everytime the IDE doesn't import getValue and setValue for mutableStateOf 🧐

This is a discussion we (Google/Android Compose team) have had several times and we decided to keep those package names

I dont know you guys requirements, but compose.framework.* for the interfaces and other multiplatform code, then compose.android.* , compose.desktop.* , compose.web.* , compose.ios.* (ios maybe someday 🙂 ), for the implementations make a lot of sense to me

@romainguy Is it just that it's too inconvenient to change at this point? I'm pretty curious what the takeaways from the discussions were

I agree with @gbaldeck. If you guys wanted to have the same package name across all platforms, should have gone with something generic. like,

com.compose.*

compose.com is not related to jetpack compose %) just

compose

would be fine

@gildor i didnt mean exactly

com.compose.*

😄 was just giving some example for generic names..

So why not share the reasoning of keeping the naming tilted towards maximum confusion?

JetBrains CEO is sad about that decision you (Google/Android Compose team) made unilateraly (and is not the only one it seems). But… it's not too late to change to

compose.*

or something, it's still alpha!

Seriously please change it or at minimum pretend this is open source and convey critical decisions and their reasoning.

I think a lot of people agree on this. Taking the community's opinion into consideration is not a bad idea at all, and I think right now is the perfect time for such change, because Compose is only going to get bigger.

I understand that decision from Compose team (or Google in general), after all they invested vast majority of time/money/human resources. So it's their decision. Keep it in the same package as other JetPack libaries makes sense on some level But I don't think that changing package name to compose.android would somehow affect adoption on android (it will be the main UI framework, after all) , but it indeed makes it more frustrating and confusing to use on other platfroms and maybe not critically, but still may hard adoption on other platforms. Also in terms of usability, having

compose.${platform}

makes a lot easier to understand when some code is platform specific or not