Issue 759

17^th July 2026

Written by Juan Marin

Comment

I’ve spent most of my career actively avoiding the spotlight. Writing to this many iOS developers at once is, I’ll admit, a strange way to protect that record.

An honest confession to start us off: after twenty years of mobile engineering, I can no longer look at anything without seeing the system underneath. Restaurants are queueing theory. Careers are dependency graphs with feelings. And every one of them fails the way software fails: by accumulation. There’s no malice here. Just a thousand reasonable additions that nobody ever came back to subtract. Complexity doesn’t arrive. It settles.

That’s the deformation I bring to this chair. By day I’m Juan, a Principal Mobile Engineer in London; in the margins I mentor: engineers plotting their next move, founders assembling their first company, all of it happening off-stage, which is where I’ve always preferred to work. The instinct is the same everywhere: find what can be removed. A newsletter turns out to be the rare system where that instinct is the whole job. Hundreds of candidates went in this week. A handful came out. The quality lives in the gap.

Whether my subtractions match your taste, that’s the experiment we’re now running. I’ll see you Friday.

– Juan Marin

Sponsored Link

The CFS for swiftCon has ended. Now the fun begins! We had over 200 community submissions for swiftCon and the program committee is working hard on the evaluations. Before the agenda is announced, we’re launching a 25% off discount code exclusively for iOS Dev Weekly Readers. The code is only good for 50 users, so be sure to jump on this quickly! Enter voucher code IOSDEVWEEKLY25 on the next.app devCon home page or navigate to this registration link.

News

The story of the week, and probably of the quarter. Apple’s 41-page complaint accuses OpenAI of systematically targeting its people, allegedly recruiting with Apple’s internal code names, with more than 400 former Apple employees now working there. Michael Tsai has collected the best commentary in one place, and a story this messy reads best as a roundup. The takes range from “the Apple Intelligence partnership is now untenable” to gentle reminders that Apple has played this game from the other side before.

I have no idea how this ends, but the two companies are wired deep into each other’s products, and untangling that will be worth watching.

Code

Natalia Panferova helped build SwiftUI at Apple, and here she flags a proper footgun: class-typed @Entry defaults get reallocated on every access, so SwiftUI sees a “new” value each time and re-evaluates views that had no business updating. The fix is a one-line move to stable storage.

This is precisely the kind of cost I meant in this week’s intro: invisible, reasonable-looking, and quietly compounding until someone goes looking. Worth five minutes even if all your environment values are structs today.

A reusable SwiftUI view isn’t one you can reuse; it’s one a teammate can adopt without reading your source. That’s the standard Alexander Weiß holds himself to here: make custom components feel like Apple shipped them, from immutable inputs and Bindings in the right places to custom styles, environment hooks and accessibility that comes along by default. Long, thorough, and honest enough to admit none of it is a silver bullet.

Business and Marketing

Most WWDC26 monetisation coverage restated the announcements; this playbook sequences them. Ship the retention messaging first, because it needs no code. Audit your metadata before the affinity engine starts reading it. And treat cross-developer bundles as your last move, not your first, because a bad bundle partner is someone else’s churn attached to your revenue.

Tools

Xcode’s MCP bridge launched with 20 tools; the Xcode 27 beta has quietly grown that to 47. Everyone’s first instinct with that surface has been to point an agent at it and let the machine do the talking. Amy asked a different question: what happens if you skip the agent entirely? Her post drives RenderPreview directly over JSON-RPC and turns Xcode into a rendering service for a SwiftUI preview gallery app she’s now building.

More than doubling the tool count is Apple saying something about where Xcode is headed. Consuming those tools as a plain API, for features rather than chat, is new territory, and it looks bigger than one gallery app.

And finally...

If decades of careful indie shipping can’t protect an inbox from From-line spoofing, the rest of us are living on borrowed filters.