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

In the last edition, I shared my first impressions after the WWDC26 keynote and the Platforms State of the Union.

This week felt like the more useful part of WWDC for me: sitting down with the sessions, rewatching the moments that matter and trying to separate the exciting demos from the things that can genuinely improve how we build apps.

Similarly to last year, our iOS team gathered in a room for two days to watch some of the Apple WWDC26 sessions and brainstorm.

These were the sessions that stayed with me the most.

What's new in Swift

If issue #73 was about the bigger platform picture, this session was a good reminder that Swift itself continues to move in a direction that feels very practical.

My main takeaways were:

• Better everyday ergonomics for normal Swift code.
• Safer high-performance Swift with stronger ownership tools.
• Useful updates across testing, Foundation and interoperability.

What I liked most is that the session did not feel split between "beginner Swift" and "compiler wizard Swift". It felt like Apple and the Swift team are trying to make the language nicer for app teams while still expanding what expert developers can do when performance really matters.

What's new in SwiftUI

This was probably one of the most relevant sessions for teams shipping product features every week.

The updates that stood out most to me were:

• A new Document model with direct disk access and snapshot-based diffing.
• Better presentations and interactions, including swipe actions on any view.
• Nice improvements to data flow, performance and content reordering.

My overall impression is the same one I mentioned last week: SwiftUI keeps getting better in the places that matter in production. It is less about one giant headline and more about chipping away at real friction.

What's new in Xcode 27

This session made it clearer why Xcode 27 was one of my biggest takeaways from the keynote week.

The key points for me were:

• Better editor workflow with customization, themes and inline issues.
• Deeper support for coding agents inside Xcode.
• Stronger tooling around Device Hub, localization, Instruments and Xcode Cloud.

This is the kind of Xcode release I usually appreciate the most. Not because one single feature changes everything overnight, but because many smaller improvements combine into less context switching and fewer annoying interruptions during the week.

Xcode, agents, and you

I was especially curious about this one because agent workflows can look impressive in demos while still feeling awkward in real projects.

The concise version of the session is this:

• Agents can help across exploring, building, refining and orchestrating work.
• The best use case is speeding up iteration, not replacing engineering judgment.
• Developers still need to review and guide the output carefully.

That last point is probably why the session worked for me. It did not try to sell the fantasy that prompts replace engineering judgment. It felt much more grounded in the reality of product teams where speed only matters if the result is still maintainable.

Get the most out of Device Hub

This was actually my favorite session from the whole week and the one I am most excited to try in practice.

The main takeaways were:

• Device Hub brings devices and simulators into one clearer workflow.
• It looks especially useful for reproducing bugs faster.
• devicectl adds a nice automation angle for teams that script their workflows.

I really liked how practical this session felt. This is exactly the kind of tooling improvement that may not dominate social media, but can save a lot of time in real development. I am genuinely excited to try the new Device Hub.

Create UI prototypes using agents in Xcode

This session was interesting because it focused less on code generation in the usual sense and more on exploring UI ideas quickly.

The points that stood out most were:

• Agents can help explore UI directions quickly.
• They are useful for making prototypes feel more realistic and lived in.
• The real value is faster iteration on key interactions.

For Apple developers working with SwiftUI, I think this is one of the more underrated uses of these tools. Fast prototyping can be valuable long before you trust an agent with production code.

🤝 Wrapping Up

Last week was about first impressions, this week felt more concrete.

After going through these sessions with the team, my biggest takeaway is that WWDC26 was not just about adding more things to the Apple developer stack. It was about making the stack feel more usable: a stronger Swift, a sharper SwiftUI, and an Xcode story that seems genuinely focused on reducing friction.

Have a great week ahead 🤎