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.
Switching to Swift Concurrency if you've worked for years with GCD might make you struggle getting rid of the 'threading-mindset'. Tasks still result in work being done on different threads, but we don't directly manage them anymore. This article is an essential piece of learning and an example lesson of my full course. Enjoy!
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 moreI’ve mentioned the improvements in Swift 6.2 several times already, but I haven’t yet told you that it’s also available as Approachable Concurrency. This article by Keith Harrison tells you how to enable it for existing projects.
Do you know how Xcode 26’s conversation with ChatGPT works behind the scenes?
With many AI tools rapidly advancing in capabilities, any article that offers tips is a valuable resource to stay current.
Talking about AI, what if you could give it eyes? I love this concept, whether you’re applying it for Claude or another AI tool.
Did you finish your new app icon yet? The new Icon Composer app should become your go-to tool, but there are some challenges to overcome.
Last week's Swift proposal state changes. Review-stage proposals are your chance to influence Swift's future.
Last week, I've spent several days on setting up CI for RocketSim. So far, I've been working alone and didn't need much of validation. However, adding new developers to my team made it a must to ensure stability (AI agents 👀).
I've had a classic week in which I did a lot, but felt like I did nothing. Setting up CI can be a slow process, especially if you constantly think "this is it" and you'll have to wait a few minutes for CI to complete.
Along the way, I learned a few things:
Let CI record your snapshots
Niek (our frontender) told me they're doing this on the web all the time. After some research, I found out that it's quite common on iOS/macOS development as well.
Funny though—after CI recorded the snapshots, they started to fail locally due to a mismatch in machines. CI is headless, non-retina, whereas I'm running on an M3 Max. However, it did allow me to validate the failures locally (crucial for productivity) and it turned out that they actually failed for good reasons.
For context, I've generated snapshots for all types of recordings for RocketSim. This includes validating App Store Connect export resolution, recordings with bezels, and screenshots of any Simulator with device bezels. The snapshots are either the screenshot or a frame of the output video.
These things I did wrong:
I did not respect retina scaling, resulting in different outputs on non-retina machines. Uneven output resolutions got corrected by AVExportSession, but only sometimes.
The latter was frustrating to find out, but it did result in several important fixes to this core library of RocketSim. Eventually, it turned out it doesn't matter whether I record on CI or locally. Both suites complete successfully now, resulting in more stability securance.
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.