Get live statistics and analysis of Jacob Bartlett's profile on X / Twitter

Wrote possibly the best SwiftUI of my life today

Advanced Swift Concurrency: You can use task groups to set a timeout for any async function.

Advanced Swift Concurrency: Launch Speed Optimisation You can parallelise app launch work in didFinishLaunchingWithOptions using a GCD DispatchGroup to wait and Swift's taskGroup to parallelise steps This avoids performing all critical work serially on the main thread.

In case you forgot, Swift has 217 keywords now

Advanced Swift Concurrency: don't use actors!! You can protect access to shared mutable state AND keep your API synchronous by using OSAllocatedUnfairLock.

Advanced iOS tips: Impress at Job Interviews Did you know you can download any .ipa from the App Store and inspect their App Bundle? Analysing their app and giving unsolicited architectural tips is a great way to set yourself apart at job interviews.

4 hours ago, the Swift team released the `swift-subprocess` package 📦 Swift was always designed to be a general-purpose language, and that includes scripting. Today, however, writing a Swift script is an enormous pain compared to a regular bash script, because it isn't designed to run other processes. The Process API exists, but is verbose and terrible, even for simple jobs. By importing the Subprocess package, our Swift scripts can call into other CLI tools like git, ls, ffmpeg, or curl naturally, with full access to modern async/await. Screenshot #1 - bash script for logging a git diff Screenshot #2 - the verbose, old-school Process API Screenshot #3 - the brand-new subprocess package Link in reply!

Advanced SwiftUI tip for iOS devs: I love using enums to implement my design systems. You can get progressive disclosure, intelligent defaults, and full customisation within your system.

Advanced Swift Concurrency: Actor re-entrancy To authenticate your API, you might request a bearer token from a service, which returns a cached token, or refreshes it. If you have multiple concurrent requests, you can use actors to suspend them, only refreshing once.

Advanced iOS onboarding UX: Picture in Picture Need your users to access a strictly locked-down permission like always-on location, frequency-update live activities, or keyboard access? Use Picture in Picture alongside a settings link to guide your users step by step!

How do people like to do dependency injection in their iOS apps? I used to roll good old-fashioned constructor injection without a framework, but these days I’m a fan of Factory by Michael Long.

Advanced Swift Concurrency: You can use task groups to set a timeout for any async function.

The biggest problem with SwiftUI is that Apple is re-creating the massive-view-controller problem. All the shiny new iOS tools are designed to bind logic tightly to your Views instead of factored nicely (see SwiftData)

You know what, Swift? I don’t care anymore. Knock yourself out.

SwiftUI interview tips: How to efficiently optimise your views Unnecessary redraws of SwiftUI views are a common cause of performance problems. You can use the private method _printChanges() method to automatically log when a view is redrawn, and why.

Update: Swift now has 219 keywords

Wrote possibly the best SwiftUI of my life today

Apple Intelligence is an embarrassment, but Xcode 16 is even worse. Print statements don't work. Try to `po` something to LLDB and the console instead fills up with *thousands* of obscure error messages.

Hot take: Git GIUs are good and gatekeeping the CLI is cringe

You know what, Swift? I don’t care anymore. Knock yourself out.

Advanced Swift Concurrency: don't use actors!! You can protect access to shared mutable state AND keep your API synchronous by using OSAllocatedUnfairLock.

Whenever I join a new team, the first thing I do is delete any UI tests that exist. This demonstrates value (and leadership) on day one. I’ve never caught a bug using a UI test; but I have lost weeks of cumulative latency on CI, and days of debugging flakey navigation issues.

In case you forgot, Swift has 217 keywords now

SwiftUI is the JavaScript of iOS

How do people like to manage dependencies in their apps? I used to like old-school Constructor Injection, but since I started using Factory I don't know how I ever lived without it.

Every iOS or Android app architecture is either: - All logic in one file (MV / MVC) - 2 files + services (MVP / MVVM) - Death by abstraction (VIPER / Clean Architecture) Prove me wrong.

This is the most controversial question in all of Swift concurrency: is this force unwrap safe or not? Please give your reasoning and argue below!

How do people like to do dependency injection in their iOS apps? I used to roll good old-fashioned constructor injection without a framework, but these days I’m a fan of Factory by Michael Long.

Update: Swift now has 219 keywords

Are the Swift bitwise operators exclusively useful for defining colours? Have you ever used them for something else?

Apple will literally take any opportunity to add another keyword to Swift

Advanced Swift Concurrency: Launch Speed Optimisation You can parallelise app launch work in didFinishLaunchingWithOptions using a GCD DispatchGroup to wait and Swift's taskGroup to parallelise steps This avoids performing all critical work serially on the main thread.