embedded examples source code repository!
I’ve written before about my struggles getting into the habit of using the new Xcode bookmarks feature, but this article from Keith Harrison made me think about them differently. Not as something you’d set up while working on a single feature or bug fix, but as a more permanent guide to the interesting and commonly visited pieces of a codebase. It’s time to give them another try!
SwiftData is significantly easier to adopt and use than Core Data, but I’m still a fan of considering other options for small amounts of data storage before reaching for something that complex. Jordan Morgan goes through a greatest hits of all the methods that are worth considering before breaking out a database or ORM.
I love this post from Edvinas Byla on dropping back to AppKit to polish up an area of his app. You should read the whole piece, but make sure to read the conclusion as I’ve not seen a fairer examination of the SwiftUI vs AppKit/UIKit debate yet. He nailed it. 👍
If you used Apple’s sample code for StoreKit, you might also have the bug in your subscription code that Craig Hockenberry talks about in this post:
That code will work fine until you encounter a customer that has Family Sharing enabled, as most do. The issue is that the Product.SubscriptionInfo can contain multiple items, and the code above only checks the first one.
It might be worth checking!
The title of Natascha Fadeeva’s post says it all. She goes through three ways to avoid falling back to AnyView
in this post. 👍
What’s that? Is it a new Apple Developer YouTube channel a couple of months before this year’s conference with a load of WWDC 2023 videos already uploaded? I wonder if we’ll see quick uploads of this year’s session videos or even simultaneous distribution alongside the official site?
Senior iOS Engineer - Voloco @ Resonant Cavity – Voloco is the best mobile recording studio in the world! Small profitable company with an Engineering driven culture. We ship with minimal process and meetings. You’ll work closely with the founders, who still regularly commit code. – Remote (within US timezones) with some on-site work (United States in CA or MN)
Don’t forget to post any open positions you have available on iOS Dev Jobs!
… and beyond!