WWDC 2026 and the platform that keeps its own counsel

Apple's developer conference ran this week. The pattern of the last few years continues: strong on-device capability, tight platform integration, and a set of platform policy questions that are being settled in courtrooms rather than on stage.

the on-device strategy, holding#

Apple's position has been consistent and, I think, correct for their situation:

• A small model on device, free, private, offline, exposed to third-party apps through a constrained system API.
• A larger model available for the cases the small one cannot handle.
• Routing handled by the system.
• Privacy as the differentiating property rather than raw capability.

That is not going to win a benchmark comparison and it was never trying to. It is going to win on the axis where Apple competes, which is a coherent product where the default behavior is the one most users want.

For developers, the practical implication has not changed: design features so the small model handles the common case.

Concretely — the 90% that the on-device model can do is free, instant, and works on a plane. The 10% that needs escalation costs money and needs a network. Getting that split right is the engineering, and it is a different skill from prompt design.

the Swift trajectory#

Swift continues its expansion beyond Apple platforms — server-side, embedded, WebAssembly, cross-platform tooling. The concurrency model's strict checking continues to produce a language that catches data races at compile time, which is a genuinely valuable property that the migration cost has made contentious.

The honest state: strict concurrency checking is correct and it is a real migration burden for existing codebases, and the error messages when you get it wrong are still harder to act on than they should be.

Swift is a better language than it gets credit for outside the Apple ecosystem and its adoption outside that ecosystem remains limited, mostly for reasons of tooling gravity rather than language quality.

the platform policy question#

The regulatory pressure on app distribution and payments continues, differently in different jurisdictions, with the result that the rules now vary by region in ways that are genuinely confusing for developers to comply with.

I do not have a clean position on the substance. What I will say is the practical part:

If you ship an app with any monetization, you now have jurisdiction-specific compliance work, and the rules are still moving. Budget for it, watch the changes, and do not assume a policy you read last year is current.

The broader observation, which is not about Apple specifically: the era of one global set of platform rules is over. Every major platform now operates under different obligations in the EU, the US, and several other markets, and that fragmentation is going to increase rather than resolve.

the things worth actually adopting#

Filtering out the keynote, the items that will matter to a working developer:

Anything that reduces app size or launch time. These are the metrics that correlate with retention and they get the least stage time.

Testing and debugging improvements in the toolchain. Consistently the most valuable and least covered part of every WWDC.

Deprecation notices. The most important announcements at any platform conference are the ones about what is going away, and they are never in the keynote. Read the release notes.

the honest assessment#

Apple ships coherent, well-integrated platforms with genuinely good on-device capability and a privacy posture that is a real product differentiator rather than only marketing.

It also operates the developer relationship with less flexibility than any comparable platform, and the regulatory environment is the mechanism by which that is being adjusted rather than any change of heart.

Both of those have been true for a decade and neither is changing this year.