<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Swift on App Coding</title>
    <link>https://appcoding.com/tags/swift/</link>
    <description>Recent content in Swift on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 05 Nov 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/swift/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SwiftUI After Five Years: What Works and What Doesn&#39;t</title>
      <link>https://appcoding.com/2025/11/05/swiftui-after-five-years-what-works-and-what-doesnt/</link>
      <pubDate>Wed, 05 Nov 2025 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/2025/11/05/swiftui-after-five-years-what-works-and-what-doesnt/</guid>
      <description>&lt;p&gt;SwiftUI launched in 2019 with a demonstration that made experienced iOS developers simultaneously excited and nervous. Excited because the declarative paradigm promised to eliminate the impedance mismatch between interface builder storyboards and code. Nervous because Apple&amp;rsquo;s track record with new frameworks included several that were replaced, deprecated, or quietly ignored within a few development cycles.&lt;/p&gt;&#xA;&lt;p&gt;Five years later, SwiftUI is neither the complete replacement for UIKit that Apple&amp;rsquo;s marketing implied nor the abandoned experiment that skeptics predicted. It is a mature but still-evolving framework that handles a large majority of common iOS UI requirements elegantly, struggles with a specific set of advanced requirements, and has permanently changed how iOS UI code is written even when developers reach for UIKit to solve problems SwiftUI cannot.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Swift vs Kotlin: The State of Native Mobile Development in 2026</title>
      <link>https://appcoding.com/2025/09/10/swift-vs-kotlin-the-state-of-native-mobile-development-in-2026/</link>
      <pubDate>Wed, 10 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/2025/09/10/swift-vs-kotlin-the-state-of-native-mobile-development-in-2026/</guid>
      <description>&lt;p&gt;The question of whether to build natively for iOS and Android or to abstract across both platforms with a cross-platform framework has occupied mobile development teams for more than a decade. The answer has not settled. What has settled is the character of native development itself — and in 2026, Swift and Kotlin have each reached a maturity that makes the native argument significantly stronger than it was five years ago.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
