<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Compose-Multiplatform on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/compose-multiplatform/</link>
    <description>Recent content in Compose-Multiplatform on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 30 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/compose-multiplatform/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>JavaFX vs Swing vs Compose Multiplatform in 2026: Which Java GUI Framework Should You Use?</title>
      <link>https://www.pistack.xyz/posts/2026-08-30-java-gui-frameworks-javafx-swing-compose-multiplatform-comparison/</link>
      <pubDate>Sun, 30 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-30-java-gui-frameworks-javafx-swing-compose-multiplatform-comparison/</guid>
      <description>&lt;p&gt;Java desktop development is not dead — it just got more confusing. In 2026 you have three credible paths to a native desktop app: Swing, the 1997-era toolkit that still ships inside every JDK; JavaFX, the modern retained-mode framework that Oracle handed to the OpenJFX community; and Compose Multiplatform, JetBrains&amp;rsquo; declarative UI that compiles the same Kotlin code to Windows, macOS, Linux, Android, and iOS. Pick wrong and you either fight a 25-year-old API or sign up for a learning curve that dwarfs your actual project. This guide compares all three with real code, current GitHub stats, and licensing facts so you can decide in ten minutes instead of three weekends.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
