<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dart on App Coding</title>
    <link>https://appcoding.com/tags/dart/</link>
    <description>Recent content in Dart on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 08 Oct 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/dart/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Flutter&#39;s Bet on a Single Codebase Has Mostly Paid Off</title>
      <link>https://appcoding.com/2025/10/08/flutters-bet-on-a-single-codebase-has-mostly-paid-off/</link>
      <pubDate>Wed, 08 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/2025/10/08/flutters-bet-on-a-single-codebase-has-mostly-paid-off/</guid>
      <description>&lt;p&gt;Google&amp;rsquo;s decision to build Flutter on top of Dart — a language that had minimal developer mindshare and an uncertain future when Flutter launched — was a risk that the broader developer community viewed with skepticism. Dart was not JavaScript. It was not Kotlin. It was not a language that developers had strong feelings about because most developers had never used it. Building a cross-platform UI framework on an obscure language was, on its face, an unusual strategic choice.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
