I took a moment to jot down some things I'm going to be paying close attention to during the WWDC announcements. Not a wish list - more like a watch list.

https://www.massicotte.org/blog/wwdc-26-watchlist/

WWDC 2026 Watchlist

WWDC is an exciting time. Here's what I'm paying attention to.

massicotte.org
@mattiem re: SDK Swift Compatibility. My sense is that instead of updating the existing SDK interface, they would rather abandon it in favor of a half baked rewrite that sits incomplete for a decade
@mattiem An item on my list is revamped Xcode project file format. It has so much unnecessary complexity. I’d like it to work more like package.swift declarations.

@weston I thought about adding this at one point, but forgot!

I think Apple management’s attitude towards AI is going to play a major factor in this decision.

@mattiem @weston I'm not sure where the conversation about `AppleProductTypes` was going. This was a good idea… but I did not follow along to see what happened next.

https://skyaaron.com/posts/swiftpm-app-projects/

Swift Playgrounds App Projects | Aaron Sky

Xcode 13.2 beta 1 just released, and by surprise it will be supporting the new project format used for writing iOS apps in Swift Playgrounds 4! Wait a second…a new project format?

Aaron Sky

@weston @mattiem Fairly certain every single possible Xcode project setting is used by at least one internal project. ā€œUnnecessaryā€ complexity is usually necessary for someone.

(Personally, I would like Package.swift to be a lot more like Xcode šŸ˜‚)

@steve @mattiem I meant complexity in the UI and file format, not in features.

If someone really needs to manually adjust the optimization level for the c++ compiler, I don't think we need a dropdown box for that, they can just add the flag. It might give Apple a reason to spruce up the compiler documentation.

@steve @mattiem Basically, I just want the project file to be.

1. Easy to read.
2. Easy to handle merge conflicts.
3. Fast to load.

The current file format doesn't really meet any of these. In addition sometimes just opening the project generates a ton of diffs that most developers don't really know the consequences of.

If folks wanna build a frontend that lets them do crazy configs.. I am all for that, but the minimum set of options should be easy for average devs to reason about.

@mattiem I guess if there is no meaningful movement towards a feature complete and more stable SwiftUI, I might actually consider moving back to UIKit 🫣
@simonnickel @mattiem I’m tempted at least once a week (but usually more often). There are so many sharp edges, walls, and cliffs—especially trying to use it for macOS development (alongside iOS).

@mattiem Re: ā€œI thought that Apple was going to launch Swift 6 with a fully-annotated SDK. But we're now three years inā€

Swift 6.0 came out in 2024. So we’re two years in, not three?

@mattiem ā€žpublicly discuss its internal use of xyzā€œ - never going to happen šŸ™ƒ
@helge you’re probably right
@mattiem I have a good feeling on the "probability", want to bet? 😃
@mattiem oh I thought of a new one. They should rename Photo Booth to Standup Check... because thats all I ever use it for. 🤣
@mattiem re Observations, UIKit supports it and it’s even supported on iOS 18, albeit with limitations. https://developer.apple.com/documentation/uikit/updating-views-automatically-with-observation-tracking
Updating views automatically with observation tracking | Apple Developer Documentation

Use Swift Observation and UIKit’s automatic tracking to update your views in response to model data updates.

Apple Developer Documentation
@benedictc ah yes! I was actually thinking specifically about the Observations struct, which is new to the 26 OSes.

@mattiem ahh I see. What kind of usage would you be looking for? I would assume that even if a framework use Observations internally it would expose it as AsyncSequence.

I used TipKit for the first time recently which uses AsyncSequence to provide values (for UIKit). It’s the first time I recall encountering it in an Apple API and the pattern had some sharp corners. I wonder/hope they refine and standardise the patterns.

@benedictc if I remember right, ExtensionKit on macOS was the first API to prompt me to use Swifts concurrency system!

I dunno what I’m looking for specifically, just anything at all…

@mattiem the only thing on my list which is not on yours is expansion of Digital ID to more regions (e.g. the EU)
@mattiem oh and confirmation that UIDesignRequiresCompatibility is gone for good come April '27 of course
@mattiem Cool list Matt. I think your predictions make sense. Personally, I'd love to see some refocusing of syntax and the evolution process too. As for SwiftUI.. maybe it's time for a new UI framework that takes some learnings from SwiftUI and the ones before it šŸ˜…

@iamkonstantin me too on syntax but surprise WWDC evolution proposals are a very bad idea and I won’t think (hope) we’ll see that.

UI frameworks, huh? I see you are a dreamer I like it.

@iamkonstantin @mattiem Apple barely has bandwidth for the current UI frameworks. I don’t expect anything new happening in the next decade.