Join 31,000+ Swift & iOS developers — free, every Tuesday, in 5 minutes.
Almost there — check your inbox to confirm your subscription.
No spam. One email every Tuesday. Unsubscribe in one click.
While actors work great in Swift Concurrency, they're not always the best choice. You might not want to introduce the overhead of async/await in some cases, in which a Mutex with Sendable support can be a way out.
Read the articleUnlock over 40 hours of expert training, mentorship, and community support to secure your place among the best devs. Click now for early access to this limited offer and a FREE crash course!
Learn moreStart with this post on interactive snippets and follow up with this week’s one. If your app has app intents, you want to build this in. If your app doesn’t have intents, you might want to consider intent-driven development.
With AI tools at hand, it’s easier than ever just to get started coding. However, taking a step back to think things through is often wiser. And yes, you can use AI in that process, too!
The new @Animatable protocol in SwiftUI aims to make animations even more approachable.
After open-sourcing Launch Booster not long ago, we got another open-sourced framework. Even if you’re not looking to delete dead code, it’s going to be fun to look through the internals and see how this works!
I’ve migrated quite a few of my projects to Swift Testing already and found this article providing an excellent overview of things I found out the hard way. A must-read!
You might not all want to adopt the Model Context Protocol (MCP), but the way this project is set up is already worth a read. I love how they combine documentation and macros to integrate into existing projects more easily.
Last week's Swift proposal state changes. Review-stage proposals are your chance to influence Swift's future.
On a day-to-day basis I'm mostly working on my developer tool RocketSim. It's a project that started in 2019, so the code base starts to have places with outdated code.
I've been mostly working solely on this project, but invited two engineers to the team recently. This suddenly surfaced problems like outdated local packages and no CI integration for running all tests.
The latter is also a downside when you want to work with AI agents. They're great at opening PRs these days, but you want to validate the outcome by running your suite of tests.
In other words, I have to prepare my codebase for the future. I started a dedicated xcode-26 branch and dropped macOS 14 so I can fully adopt latest APIs. This included refactoring old CGWindow APIs to ScreenCaptureKit and migrating XCTest to Swift Testing.
These weeks are less fruitful feeling wise since I'm not doing many releases. Not having something tengible can feel demotivating—the opposite is actually releasing an app update with added value which always feels great. Yet, I do know what I'm working towards. Soon, I'll be able to easier invite other engineers or AI agents to the project and accelerate development due to having a modern codebase.
Sometimes, you have to take one step back to take two steps forward!
Join 31,000+ Swift & iOS developers and get the next one in your inbox — free, every Tuesday, in 5 minutes.
Almost there — check your inbox to confirm your subscription.
No spam. One email every Tuesday. Unsubscribe in one click.