<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Swift on The Final Artefact</title><link>https://www.thefinalartefact.xyz/tags/swift/</link><description>Recent content in Swift on The Final Artefact</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Mon, 24 Nov 2025 16:01:56 +0000</lastBuildDate><atom:link href="https://www.thefinalartefact.xyz/tags/swift/index.xml" rel="self" type="application/rss+xml"/><item><title>Using Xcode Pre- and Post-actions to Observe Changes to Defaults</title><link>https://www.thefinalartefact.xyz/post/build-pre-post-actions-observe-default/</link><pubDate>Mon, 24 Nov 2025 16:01:56 +0000</pubDate><guid>https://www.thefinalartefact.xyz/post/build-pre-post-actions-observe-default/</guid><description>Because UserDefaults persistence is opportunistic, it’s often hard to tell when values truly flush and what changed between runs. In the article I set up an app group prefs watcher with fswatch, convert the binary plist to XML via plutil, and log a timestamped diff for every write—no breakpoints, no in-app logging. If you’ve ever wondered “what did my app really persist?”, this workflow makes it obvious.</description></item><item><title>Bring your Python ML Model to iOS App in under Three Minutes</title><link>https://www.thefinalartefact.xyz/post/python-models-app/</link><pubDate>Thu, 24 Jul 2025 00:00:00 +0000</pubDate><guid>https://www.thefinalartefact.xyz/post/python-models-app/</guid><description>&lt;p&gt;&lt;a href="https://www.thefinalartefact.xyz/post/python-models-app/images/phonedemo.gif" target="_blank" rel="noopener noreferrer"&gt;
&lt;img alt="Phone Model Demo" loading="lazy" src="https://www.thefinalartefact.xyz/post/python-models-app/images/phonedemo.gif"&gt;
&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Integrating Python-based machine learning models into iOS applications can be challenging, particularly when converting models into a Swift-compatible format. This example will demonstrate a simple image classification task using the Fashion-MNIST dataset and CoreML conversion tools. The goal is to illustrate the effort required to deploy small-to-medium complexity ML models within iOS applications. The demonstration is based on a Convolutional Neural Network (CNN) built with PyTorch, but the concepts apply broadly to other Python-based models as well.&lt;/p&gt;</description></item><item><title>Using Swift for Data Science Workflows</title><link>https://www.thefinalartefact.xyz/post/swift-data-science/</link><pubDate>Tue, 04 Mar 2025 00:00:00 +0000</pubDate><guid>https://www.thefinalartefact.xyz/post/swift-data-science/</guid><description>&lt;h2 id="why-swift"&gt;Why Swift?&lt;/h2&gt;
&lt;p&gt;Data science is dominated by Python and R, with some usage of Julia, Scala, Java, and C++. While Swift may not be the most popular choice, it offers several notable benefits—especially for developers already invested in the Apple ecosystem.&lt;/p&gt;
&lt;h2 id="key-advantages"&gt;Key Advantages&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Performance Considerations&lt;/strong&gt;&lt;br&gt;
As a compiled language, Swift often runs faster than languages like Python or R. This can be especially beneficial when handling large datasets or complex computations.&lt;/p&gt;</description></item></channel></rss>