<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gui-Toolkits on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/gui-toolkits/</link>
    <description>Recent content in Gui-Toolkits on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 16 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/gui-toolkits/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>LVGL vs Slint vs Nuklear in 2026: Which Embedded GUI Toolkit Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-10-16-embedded-gui-toolkits-lvgl-slint-nuklear-guilite/</link>
      <pubDate>Fri, 16 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-16-embedded-gui-toolkits-lvgl-slint-nuklear-guilite/</guid>
      <description>&lt;p&gt;Your device ships with a 320x240 display, 256 KB of RAM, and a project manager who wants the UI done yesterday. On the proprietary side, TouchGFX, emWin and Crank Storyboard all want per-seat licenses and NDA paperwork before you can read the docs. On the open side, three toolkits dominate every forum thread: &lt;strong&gt;LVGL&lt;/strong&gt;, &lt;strong&gt;Slint&lt;/strong&gt; and &lt;strong&gt;Nuklear&lt;/strong&gt;. Picking wrong costs you months — a widget set that cannot fit your memory budget, or a project that stopped receiving commits in 2020.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
