AFAIK "desktop" here means "JVM+SWING+SKIA on desktop"

First thought: something like compose-navigation wouldn't be available on desktop, right? That probably means we would have to build abstraction layers if want to build some cross-platform functionality. Is there a recommended way, through Ambients or something else?

Hey everybody! Technically, this channel is not yet open for general public. However welcome everybody, and stay tuned for just few days until official announce!

I am really stoked about this. Just played with it a bit - https://twitter.com/vinaygaba/status/1323741779133308930

I wonder if there are plans to make JbCompose truly native. i.e. Kotlin Native as opposed to JVM

Kinda off-topic, but what would be the recommended approach to store simple settings in a compose desktop project? Android dev here, I have a compose project using shared preferences, but have no idea how it should be handled in desktop, maybe just a simple file? 🤔

Anyone aware of ability to show map in Compose desktop app?

Only thing that makes me cringe is seeing the

androidx

imports in desktop code. i wish the package name, could be platform agnostic. Probably

compose

?🤷‍♂️ Is it just me who is disturbed by this? anyone else?

Do I need to use IntelliJ IDEA to work on Compose Desktop? Is it possible to work with android studio?

hi, just wanted to ask - I'm playing around with compose for desktop. how do I change the size of an element (like a button)?

Is it possible to use obfuscator to protect our package built with compose ? Can it be built into the toolchain ? So that we can safely distribute our product. 🤔

Is skia used by jbCompose written in c? If so, I'm curious how that's injected/managed from jvm?

I don't know much about GraalVM, I know that it generates a native executable of a Java/Kotlin project. There is any possibility of using the GraalVM AOT compiler with Compose-JB ?

It seems from announcements (and samples) that at least right now we should be able to have single project that supports Compose on Android and Desktop. What's plan for future in terms of sync'ing with respective releases cycles?

How about @Preview in Intellij

Successfully running my dark toggle button demo both on the Android and Desktop! 🤩 Code: https://github.com/lcdsmao/Dark-Toggle-Button-Sample-Jetpack-Compose

Kotlin Serialization was not working if it is in a module which uses compose directly. Is this problem in desktop too?

Is is possible to write Intellij IDEA plugins with Compose for Desktop?

Testing jetbrains compose by creating clone of intellij idea startup screen. Code here: https://github.com/blacpythoz/Compose-Desktop-PlayGround

Hello everybody, I’m trying to use jetpack compose, When I execute the code everything is okay, but the IDE shows somes errors I don’t known why

In desktop compose, do we have the ability to use any of the Material components from the Android library?

it will be posible to handle multiple windows?

Can we develop any UI inside of the common layer yet between android and desktop, or is the UI only available in the platform directories currently?

Is there any multiplatform image loading library for use with jetpack desktop?

When I want to change the corner raduis with a raduis big than 20dp, the button looks like this

Anybody experience this?

Script compilation error:

  Line 15:     implementation(compose.desktop.currentOs)
                                              ^ Unresolved reference: currentOs

👋 Are there any samples for writing tests for compose-desktop? I only found this in AOSP.

Wow waited so long for this release 😄. The imageviewer demo show how to handle images in Android and Desktop. But it completely doubles the UI code for Android and Desktop. Are there any plans to introduce some platform independent resource handling? So you could write the UI once and use it in Android and Desktop. Or maybe at least write components that are platform independent. Maybe a library which loads images from streams and outputs an ImageAsset that will be decoded to DesktopImageAsset or AndroidImageAsset. So you only need to handle ImageAsset which is Platform independent.