<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mobile on code.kiwi.com</title><link>https://code.kiwi.com/tag/mobile/</link><description>Recent content in Mobile on code.kiwi.com</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 15 May 2024 12:17:03 +0000</lastBuildDate><atom:link href="https://code.kiwi.com/tag/mobile/index.xml" rel="self" type="application/rss+xml"/><item><title>Swift 5.10 Concurrency Survival Guide</title><link>https://code.kiwi.com/articles/swift-5-10-concurrency-survival-guide/</link><pubDate>Wed, 27 Mar 2024 12:54:34 +0000</pubDate><guid>https://code.kiwi.com/articles/swift-5-10-concurrency-survival-guide/</guid><description>&lt;p&gt;This pattern was broken a few years ago when new versions of Swift started coming out in point updates. Xcode 15.3 includes Swift 5.10. Reading through the &lt;a href="https://developer.apple.com/documentation/xcode-release-notes/xcode-15_3-release-notes"&gt;release notes&lt;/a&gt;, one can find a few mentions of concurrency, such as:&lt;/p&gt;</description></item><item><title>ObservableObject initialisation using Environment</title><link>https://code.kiwi.com/articles/observableobject-initialisation-using-environment/</link><pubDate>Wed, 23 Aug 2023 13:22:30 +0000</pubDate><guid>https://code.kiwi.com/articles/observableobject-initialisation-using-environment/</guid><description>&lt;p&gt;For the purpose of this article, our &lt;strong&gt;ObservableObjects&lt;/strong&gt; represent optional testable and mockable view models that drive the domain logic for some of the more complicated screens in our app.&lt;/p&gt;
&lt;p&gt;A side note on the SwiftUI environment for following code examples: As our app is driven by feature-based modular architecture, we are using &lt;strong&gt;Environment&lt;/strong&gt; instead of &lt;strong&gt;EnvironmentObjects&lt;/strong&gt; for our modular dependencies. This approach has some disadvantages (for example not being able to fully use &lt;strong&gt;@Published&lt;/strong&gt; properties), but in our case, the modularity aspect overweights these limitations.&lt;/p&gt;</description></item><item><title>Feature flag and A/B test management in the iOS app</title><link>https://code.kiwi.com/articles/feature-flag-and-a-b-test-management-in-the-ios-app/</link><pubDate>Wed, 31 Aug 2022 20:10:00 +0000</pubDate><guid>https://code.kiwi.com/articles/feature-flag-and-a-b-test-management-in-the-ios-app/</guid><description>&lt;p&gt;In bigger apps, there is often a need for using &lt;a href="https://en.wikipedia.org/wiki/Feature_toggle"&gt;feature flags&lt;/a&gt;. As responsible developers, we don't want to depend directly on a third party for this, so we create abstractions on top of the remote data provider. The one we were using wasn't up to the task, so we set out to create a better one.&lt;/p&gt;</description></item></channel></rss>