Readaggregator - iOS, Swift, Apple, Programming, Mobile

«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

Some time ago I mentioned sosumi — a neat tool that makes Apple docs readable for LLMs. But today I ran into another one that approaches the same problem differently: Instead of fixing the website, it works with the documentation that already ships inside Xcode. • indexes local Xcode documentation • runs entirely on-device (requires Xcode 26.3) • answers almost instantly https://github.com/BitrigApp/XCDocs/ #LLM

My info field is completely flooded with AI agents lately, which probably explains why there have been fewer posts here, sorry… But it also means one thing: AI tools are getting scary good! We’re no longer at “it writes boilerplate for me.” We’re at “it writes the code, runs it, taps the UI, and checks whether it actually works.” Three tools that make this very real: • AXe — a CLI to control iOS Simulator via accessibility & HID functionality. Tap at specific coordinates. Swipe with precise velocity. Type text. Dump the accessibility tree. Record video. Chain it in scripts. • MotionEyes — analyzes UI motion frame-by-frame. It can detect when pixels start changing and when they stop — so you can assert animation duration instead of eyeballing it. • Haptix — an actual SDK you embed into your app. Once integrated, your app becomes controllable via MCP — an agent can inspect UI, take screenshots, interact with elements, and run flows. Works with simulators and real devices. #LLM

Xcode 26.3 ships agentic coding. The AI now has real tools: filesystem access, project config changes, builds, tests, previews. At this rate, Xcode might eventually evolve into a full IDE. (not guaranteed) Thanks to MCP, Xcode can be used as a headless IDE backend: connect it to your agent, stay in the terminal, and let Xcode do the “IDE stuff” for you. Except it currently asks for permission on basically every action, doesn’t allow project-level agent trust, and refuses to render SwiftUI previews unless the editor tab is open. 😥 So close. So very Apple. #Xcode #AI

TIL: UIScreenShotServiceDelegate exists since iOS 13. Found it only today. Somehow missed it for years. It lets your app provide a custom Full Page representation — basically a PDF that the system uses when the user chooses that mode. Safari uses it for long pages. Apple Maps uses it to export a clean map, without UI chrome. Feels like one of those UIKit features that quietly shipped and never got attention.

Probably everyone is already tired of reading about Clawdbot. Too many posts, too much noise. But this story is on a different level. Honestly, it reads like a Netflix script. The short version: • Anthropic complained about the Clawdbot name. • The project rushed a rename. • During that window, the account was taken over. • Under the old name, fake tokens were pushed to the market. • Within hours, FOMO kicked in on Solana and the token briefly hit a ~$16M market cap. 🫠 Not a bug — pure timing. https://dev.to/sivarampg/from-clawdbot-to-moltbot-how-a-cd-crypto-scammers-and-10-seconds-of-chaos-took-down-the-4eck #security #Clawdbot

As multi-module setups become more common, it helps to be precise about how imports work.

import Foo

• Swift 5: implicitly a public import (see public import Foo below), unless InternalImportsByDefault is explicitly enabled. • Swift 6: a regular internal import — visible only inside the module and does not affect the public interface.

public import Foo

• Allows Foo types to be used in public / open API. • Downstream modules gain access to Foo, but still have to explicitly write import Foo themselves.

@_exported import Foo

• Foo types become automatically available to any module importing yours. • Useful for facade modules. https://alexanderweiss.dev/blog/2026-01-16-exported-import-vs-public-import #swift

Every time Apple ships a “simpler” sync API, I hope this is the one where I won’t have to think too much. CKSyncEngine almost looks like it… until you read Christian Selig’s article. It’s not a tutorial — it’s a list of things that will quietly break later if you trust the magic: • saves resolve conflicts, deletes don’t; • enums in synced models are a trap; • engine state must be persisted; • quota errors are still your problem. The API is better, but architectural responsibility didn’t go anywhere. So it’s worth reading if you’re considering CKSyncEngine. https://christianselig.com/2026/01/cksyncengine/ #iOS #CloudKit

Okay, maybe now I’ll finally get strict concurrency. 😠 https://fuckingapproachableswiftconcurrency.com Joining the trusted collection: • https://fuckingformatstyle.com • https://fuckingblocksyntax.com #Swift #concurrency

Every time I read articles about SF Symbols, I’m amazed by the animations, the customization, and how polished everything looks. I think: maybe next year I’ll finally sneak them into a real app… Spoiler: yeah… probably never. Most of these ideas live happily in pet projects and playgrounds. Maybe there are some lucky people in this chat actually using them in production? If so — envy! As the year ends, here’s my little wish for all of us: may next year finally give us a project brave enough to let us play with them for real! 😎 https://nilcoalescing.com/blog/AnimatingSFSymbolsInSwiftUI/ #SwiftUI #animations

Recently had to animate a SwiftUI sheet resizing itself — sounds like a super basic thing, but the actual solution was anything but obvious. If you ever need an animatable, auto-sized sheet, this write-up breaks down an approach. Might save you a couple of hours (and some sanity). https://clive819.github.io/posts/animatable-auto-sized-to-fit-swiftui-sheet/ #SwiftUI #Layout

Nice reminder about how .task behaves when it depends on a property that can change — and why adding an id makes all the difference. https://chris.eidhof.nl/post/swiftui-task-identity/ #SwiftUI

Apple quietly dropped a few nice App Store updates. The biggest one — you can finally submit a new version, while another build is still under review. 🙌 Other small but welcome changes: • Up to 70 custom product pages per app (each with unique keywords). • Offer codes now work for all IAP types, replacing old promo codes by March 2026. https://www.macrumors.com/2025/10/29/apple-developer-app-store-updates/ #AppStore

Me: waiting for Swift Assist Swift team: “How about Swift… on Android?” https://www.swift.org/blog/nightly-swift-sdk-for-android/