Looks like TCA 2.0 is on the way.

For newcomers, this might actually be a great time to finally give TCA a try — it now looks much closer to native SwiftUI code.

For the rest of us with TCA 1.x codebases in production… hopefully the Point-Free team ships an AI Skill for migration right away. 🙈

https://www.pointfree.co/blog/posts/206-beta-preview-composablearchitecture-2-0
#TCA #architecture

Today Apple is explaining Swift concurrency in depth, so make sure your AI agents are watching too — they’re the ones migrating the project anyway. 😏
https://www.youtube.com/live/E95agtPgaa0
#Swift #concurrency

Love seeing an actual clean use case for fixedSize() in SwiftUI.

Usually it ends up as one of those “well… this somehow fixes the UI bug” modifiers you throw in as a layout bandaid. But this one was genuinely elegant and made perfect sense.

https://www.swiftdifferently.com/blog/swiftui/fixedsize-usecase
#SwiftUI #Layout

«Ah shit, here we go again» but now in a less scary way.
https://x.com/stephancasas/status/2059730171964670086
#Xcode

Time to do some prompt archaeology in the new Xcode
https://github.com/artemnovichkov/xcode-27-system-prompts
#Xcode #llm

All SwiftUI changes in one image.
https://x.com/shubham_iosdev/status/2064081215788118280?s=46&t=YNy4qFziI3PFPTlrSCXpmA

FYI: starting with Xcode 27, Apple will ignore the UIDesignRequiresCompatibility flag.

So if you're hoping to avoid Liquid Glass, your only option will be staying on an older Xcode. The bigger question is how long App Store submissions from older toolchains will remain supported.
https://developer.apple.com/documentation/BundleResources/Information-Property-List/UIDesignRequiresCompatibility
#Xcode

WWDC26 Swift Group Lab Q&A is probably the most valuable Swift Concurrency content from this year’s WWDC.

Lots of subtle details:

• Does Task {} actually leave MainActor?
• What does nonisolated mean in Swift 6.2 now?
• When should you use @concurrent?
• Is async code really running where you think it is?

… turns out the answer is increasingly: “not where you think.”

https://antongubarenko.substack.com/p/wwdc26-swift-group-lab-q-and-a
#Swift #concurrency

If you rushed to install the new Xcode after WWDC, started migrating code to ContentBuilder, and explored the new @State macro…

don’t forget to read TN3211.

It’s Apple’s guide to understanding why some perfectly valid SwiftUI code from last week suddenly isn’t so valid anymore.

https://developer.apple.com/documentation/technotes/tn3211-resolving-swiftui-source-incompatibilities-for-state-and-contentbuilder
#SwiftUI

Apple finally got around to adding this in iOS 27, and somehow I’m still genuinely excited about it. 😄

textSelection() now supports granular text selection. In iOS 26, applying it to a Text view only let you select the entire block. Now you can simply drag to select the exact part you want, just like in any native text view.

It took them until iOS 27… but I’ll happily take it.

https://x.com/natpanferova/status/2070781569044996429?s=46&t=YNy4qFziI3PFPTlrSCXpmA
#SwiftUI

If you’re using Tuist, it’s worth trying their new package resolution process - Swifterpm

Why did they build it?

• Better support for Git worktrees
• Faster parallel installs for AI coding agents
• A shared package store to avoid duplicate checkouts
• Faster dependency resolution and package materialization

The benchmark results look very promising.

The Tuist team is actively looking for feedback, so if it works well in your project, let them know!

#build #optimization #tuist