Readaggregator - iOS, Swift, Apple, Programming, Mobile

Apple introduced @ContentBuilder this year, and we’re already seeing developers push it beyond its original use case. My Swift buddy Artem ran an interesting experiment using @ContentBuilder with non-View types. It’s a nice example of how the new builder…

Oh, alignmentGuide is one of my favorite SwiftUI APIs! This article is a great example of how it can elegantly solve a layout problem without resorting to GeometryReader, offsets, or other workarounds. If you’ve never really used alignmentGuide, this is definitely worth a read! https://nilcoalescing.com/blog/AlignmentGuidesInSwiftUI #SwiftUI

Apple introduced @ContentBuilder this year, and we’re already seeing developers push it beyond its original use case. My Swift buddy Artem ran an interesting experiment using @ContentBuilder with non-View types. It’s a nice example of how the new builder can be used to create clean DSL-like APIs. https://artemnovichkov.com/blog/using-swiftui-contentbuilder-with-non-view-types #Swift #SwiftUI

If you’re migrating to Swift 6, this is a great short refresher on one of the most confusing concurrency changes. It explains, with simple examples: • how nonisolated behaves with Approachable Concurrency • when execution stays on the caller’s executor • and when @concurrent is actually needed. These are easy details to forget, but they often come up in code reviews and technical interviews. 😉 https://nsvasilev.com/posts/approachable_concurrency/ #swift #concurrency

FYI Apple deprecated canOpenURL(_:) in iOS 27. Instead of checking whether an app is installed, the new recommendation is to simply call open(_:completionHandler:) and handle failures. There’s another change: apps linked against the iOS 27 SDK can now declare only 25 entries in LSApplicationQueriesSchemes (down from 50). https://developer.apple.com/documentation/uikit/uiapplication/canopenurl(_:) #iOS #privacy

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

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 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

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

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

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

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

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

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

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

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

Figma opened the canvas to AI agents. Go make your designers happy — they can now finally say: “move it 10px to the left”. https://www.figma.com/blog/the-figma-canvas-is-now-open-to-agents/ #figma #llm

Another post in your feed about the WWDC26 announcement — June 8 to 12. My small wishlist this year: • Stricter swift concurrency by default. Less warnings, more reality. • Liquid Glass everywhere, whether your app wanted it or not. Our designers will be thrilled. • Xcode deprecated. Nature is healing. Let’s see what actually lands. https://developer.apple.com/wwdc26/ #Apple #wwdc

Xcode 26.3 is already out, and I only recently stumbled upon an article about a new build flag in Xcode 26: COMPILATION_CACHE_ENABLE_CACHING. In theory it should speed up builds by caching compilation artifacts. Looks simple enough, but the real impact seems very case-dependent. A few observations from different sources: • Helps when switching branches or doing repeated clean builds. https://mjtsai.com/blog/2025/06/13/xcode-26-announced/ • Tuist reports that in early Xcode 26 versions not everything is cached yet — parts of SwiftPM and some build graph work still bypass the cache. https://tuist.dev/blog/2025/10/22/xcode-cache • CI results vary a lot. Bitrise points out that the local compilation cache and a shared CI cache are different problems. The flag alone doesn’t give you a distributed cache. https://bitrise.io/blog/post/lifting-the-hood-on-build-cache-for-xcode • Things like asset catalogs, storyboards, linking, script phases and dSYM generation can still invalidate large parts of the build. https://docs.bitrise.io/en/bitrise-build-cache/build-cache-for-xcode/xcode-compilation-cache-faq.html #Xcode #optimization

Apple docs are already frustrating and often not very helpful for developers, and on top of that, LLMs can barely make sense of them: try loading a page with an LLM and all it sees is a JavaScript error: “This page requires JavaScript. Please turn it on and…