Welcome to issue #75 of the iOS Coffee Break Newsletter 📬.

Lately, a lot of my conversations have been orbiting around the same themes: agents, better tooling, SwiftUI craft and what it looks like to use them in real projects.

So for this edition, I picked four recent posts that felt especially relevant. Two are about giving agents a narrower job: one around iOS launch performance, the other on bringing Cursor into Xcode 27. The other two go back to fundamentals I keep coming back to: how to split large SwiftUI views the right way, and a WWDC26 follow-up on building Mac-assed apps with SwiftUI.

Have a great week ahead 🤎

CURATED FROM THE COMMUNITY

The iOS Launch Performance Agent Skill

In Artem's latest article, he explores what it looks like to build an AI skill focused specifically on app launch performance, instead of asking an agent for broad and vague optimization advice.

The article frames launch performance as a pipeline and pushes the agent to reason about what truly belongs on the critical path and what should move later.

Using Cursor in Xcode 27

In this post, Pol walks through how to use Cursor as an agent inside Xcode 27 by wiring it up through Apple's new ACP-compatible agent support.

If you've been curious about mixing Xcode's native workflow with the tools you already use elsewhere, this is a useful setup guide!

Splitting Large SwiftUI Views in the Apple's way

In this post, Emre walks through a refactor he did in Walk Mate after Apple added view structure guidance to Xcode 27's coding skills.

It's a good reminder that cleaner code and faster SwiftUI are not always the same thing. Extract subviews with narrow inputs when you want both and keep @ViewBuilder for the small branching cases where extraction would feel noisy.

A WWDC 26 Update on Building a Mac-assed App with SwiftUI

Paulo wrote a follow-up to his popular post on building a Mac-assed app with SwiftUI, after his original article got traction and even caught the attention of an Apple engineer.

It is a useful checkpoint if you are building for macOS and want a developer's take on the new APIs, without pretending SwiftUI has fully closed the gap with AppKit overnight.