zlacker

>>emilsj+(OP)
For me, as an Android developer, this is a huge improvement.

Finally, I can easily select elements that were non-selectable-without-holding-cmd in the "design" mode. The thing that shows paddings and margins is a godsend, AND it stays put when you move your mouse somewhere else and switch to another window. The size tooltip also now shows the actual helpful size in pixels in addition to the unhelpful "hug/fill".

The choice of Jetpack Compose as the only Android code format is strange. Most people, even those who do embrace The Google Way™ of Android development and Kotlin itself, don't take it too seriously and don't consider it production-ready. It would be nice to have support for the good old XML layouts.

>>grishk+881
Interesting, I'm not an Android developer myself but at least our Android teams seem to really really like Compose. In fact yesterday I overheard one of the guys say, "Almost everyone in the industry is switching to Compose these days". (Not sure that's true but still.)

>>codeth+nm1
I'm personally on the opposite end of this spectrum. My projects don't use neither Kotlin nor even AppCompat. The AndroidX libraries that I need (because Google can't be assed to ship them as part of the system) like RecyclerView I use as my own fork that doesn't depend on anything else. I wholeheartedly despise what Google does to the Android development ecosystem. Google is not a good steward of Android.

Other developers I know approach Compose with caution and mostly use it for experiments, not in their real apps.