Liking the approach and api of compose. But wonder...
# compose-desktop
p
Liking the approach and api of compose. But wondering, is compose-desktop primary goal to run multi-platform applications also on the desktop, or also to create complex graphical apps that wouldn't make much sense on mobile. So will it be in its final form also a contender for swing and javafx?
o
As with many libraries/frameworks, only practical success stories will show the most appropriate niche. We aim at being modern and fast UI framework, and it’s up to users to build either MPP or desktop-only apps. And in case of Swing/JFX, we interop with them, and so people could build UI solutions using best of either one.
👍 2
c
For running a mobile-type app on a desktop environment, I’d usually say that a website would be a better choice (and the JB team is currently looking into Compose for web, too). So IMO that leaves native desktop as more useful for complex apps that need more screen real estate than a mobile app and the ability to do more local data processing than you can with a website or that would be prohibitively expensive to run in the cloud (file IO, batch processing, image transformations, etc.)
p
Thanks, will further explore some use cases I have for it and see how it integrates with fx when certain type of components are not (yet) available.