<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Flutter on Nalar</title>
    <link>https://nalar.dev/tags/flutter/</link>
    <description>Recent content in Flutter on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/flutter/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Compose Multiplatform vs Flutter: Rendering, Performance, and Bundle Size</title>
      <link>https://nalar.dev/compose-multiplatform-vs-flutter-rendering-performance-and-bundle-size/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/compose-multiplatform-vs-flutter-rendering-performance-and-bundle-size/</guid>
      <description>&lt;h1 id=&#34;compose-multiplatform-vs-flutter-rendering-performance-and-bundle-size&#34;&gt;Compose Multiplatform vs Flutter: Rendering, Performance, and Bundle Size&lt;/h1&gt;&#xA;&lt;p&gt;Compose Multiplatform and Flutter can produce similarly smooth mobile interfaces, but they do not reach the screen through the same stack. That difference matters more than the usual &amp;ldquo;Kotlin versus Dart&amp;rdquo; comparison.&lt;/p&gt;&#xA;&lt;p&gt;Compose Multiplatform extends the Compose programming model across platforms. Flutter ships a more self-contained UI stack with its own engine and Dart runtime. Both approaches add machinery around application code, but the cost appears in different places: rendering work, startup, memory, binary size, and platform integration.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
