Daniel Andrews:

If that’s true, here’s what I’m hoping for: fix Liquid Glass on the Mac where it’s genuinely bad. Not a cosmetic tweak, a real rethink of the parts that trade usability for novelty. Bring back some intentionality to the design. Focus on human interaction, stability and speed as primary goals, not footnotes in the release notes. Do small, meaningful things for developers. It’s just one cycle so my hopes are pretty low. But just directional progress and iteration.

Brian Webster:

It’s insane that there’s no way to programmatically create/modify a shortcut. I’m really hoping this gets fixed at WWDC this year. 🤞

[…]

I wish for a headless, agent-first Xcode Server in the menu bar — exposing every UI-only operation as MCP (including the .xcodeproj-mutating ones), queueing builds across projects, and running nightly maintenance on sims and derived data.

Cihat Gündüz:

Here are five things I most want them to ship — the gaps slowing me down most in the era of agentic engineering.

Jordan Morgan:

Consider this — each dub dub session which presents a new API comes packaged with a skill.

[…]

Depending on who you ask, MCPs are amazing or terrible token wasters on their way out. Regardless, I’d love a direct, official line to Apple’s docs.

Krishna Sadasivam:

Apple made no secret that it will be dropping Intel support with macOS 27. Does this bode well for a “Snow Leopard” type release? I really hope so. Renewed focus on software quality would be a strong overture to developers and users alike. Fix bugs and improve performance!

My wishes from last year still stand. I’m not holding my breath for a better designed Systems Setting panel. I also think that Liquid Glass is here to stay, despite the backlash it’s received. I’m hoping Apple will include more options for users to customize the color for both the windows and the Dock.

While I am excited about potential software quality improvements, I remain ambivalent about Apple’s AI push. I see some beneficial value in AI, but I don’t want it to be rammed down my throat.

Steve Troughton-Smith:

I wouldn’t mind some qualitymaxxing at WWDC.

Antoine Van Der Lee:

While I already mentioned an MCP example and we already have an Xcode MCP and CLIs, I just wish for Apple to continue supporting agentic development.

[…]

Similarly, I think they can further open up developer tooling. Apps like Icon Composer and Xcode Instruments don’t work well with agents today and can be further optimized for integrations. Updating App Store Metadata, archiving, and publishing a new release: to automate these, we still have to do a lot of work ourselves. Yes, there’s Xcode Cloud, but I believe this process can be optimized even further with agents.

Majid Jabrayilov:

We already have on-device image generation using the ImagePlayground framework. Why not have image analysis as part of Foundation Models? I think it is the most expected feature along with increased context size.

[…]

Layout protocol is great and allows us to build super custom layouts from flow layout to hexagonal layout. One thing it is really missing at the moment is the option to make it lazy, like LazyVStack or LazyHStack.

[…]

Another important feature I expect almost for three years is the recycling view in SwiftUI. At the moment, all views are displayed eagerly or lazily, but there is no reusing mechanism like in UITableView or UICollectionView.

Joel Breckinridge Bassett:

As outlined years ago, the history of Apple’s text layout architectures has been very convoluted and without any long term vision for some time now. When I ran across Artem Loenko’s post, ‘Native all the way, until you need text’, my first reaction was ‘that’s what happens without a unified vision’. Nobody at Apple seems to be asking ‘where can we take customers and developers?’ The difference in Apple Pay Wallet and text teams is striking. Loenko outlines the basic problem of using TextKit 2[…]

[…]

This is the state of Apple Pay Wallet since the arrival of iOS 18.1 NFC & SE Platform. The only real change needed for 2027 is the expansion of UWB support in CCC digital car keys to include recent UWB FiRa Consortium spec developments in Mobile FeliCa, Mobile MIFARE and Aliro. This would allow UWB Express Mode use with transit cards, hotel keys, home keys, office keys and ID badges.

Fatbobman:

But this year, at least by the time I was putting together this issue, there seemed to be noticeably fewer such posts than around the same time last year. […] Perhaps the issue isn’t a lack of anticipation, but rather that the traditional format of a wishlist is no longer quite sufficient. […] We hope to see updated features, more stable frameworks, and a clearer platform direction.

Sarah Reichelt:

I had not noticed the vanishing WWDC wish lists until you mentioned it, but I had felt no desire to write one this year. We haven’t even got stability in the OS 26s yet and within a couple of weeks we’ll get betas of OS 27s which cannot be any better unless Apple has scrapped 26 and built 27 on top of older, more polished versions. This sounds incredibly unlikely, so they will be piling bugs on top of bugs and hoping nobody notices.

Helge Heß:

I think my top wish for #WWDC would be ways to properly integrate the SwiftNIO event loop into the concurrency runtime (so that async/await can be used w/o hopping threads all the time). Or maybe just make the NIO event loop part of the concurrency runtime in the first place.

Tony Arnold:

My WWDC wishlist? A new, simpler, directly editable Xcode project file.

I’m duplicating a target today for an AppStore vs Direct Distribution variant, and Xcode crashes when I try to duplicate the target via the UI.

So yeah, easier to maintain project files would be a very welcome addition.

Howard Oakley:

It’s now almost a year since we got our first glimpse of Tahoe at WWDC 2025, and eight months since it was released to the public. Despite widespread outcry and detailed criticism, it has changed remarkably little. If you were unconvinced of its merits last September, I see little here that’s likely to persuade you otherwise. The only remaining question is whether, in the razzle of WWDC, Apple will do anything substantial to relieve the dazzle on our displays. I fear I already know the answer.

Warner Crocker:

iCloud syncing. Just make it reliable and give us Sync Now buttons. We get one is Messages. How about the rest of the core apps?

Perpetual Betas: I know, and respect that Apple is continuing to work on each new operating system throughout the year. Kudos. It can’t be easy. That said, find a way to keep from mucking things up on the backend for users who don’t participate in betas. Perpetual beta weirdness is hell for normal users.

[…]

Error Messages. Tell us more. Yes, I know something failed. Tell me more about what failed and point to a solution or information that can help me find out more. 

[…]

App Store. For a company that spends untold amounts of money on its brick and mortar stores, I remain shocked at how they can be proud of the software versions of any of its App Stores. 

Codenter:

I can deal with ugly UI, missing features, whatever. Xcode is different because it constantly makes me waste time on problems that feel completely detached from my code.

[…]

Some days it’s SwiftUI previews: change one harmless view and suddenly previews stop loading, or you get some useless wall of diagnostics that disappears after nuking DerivedData. Some days the simulator decides it doesn’t want to boot after an update. Sometimes indexing eats the whole machine, autocomplete gets drunk, fixed errors keep hanging around, or debugging from Xcode is mysteriously way slower than running the same thing normally.

Helge Heß:

My secret bet for WWDC is OpenSource SwiftUI. Why? Because it’s kinda inevitable that someone else does that otherwise using the current tooling. Just imagine a working List! 🙈

Confidence level: 0.1%. Probably won’t happen because of ignorance(/arrogance?), but would likely be the right decision for that specific project.

Steve Troughton-Smith:

The best kind of WWDC is the WWDC that gives me a big grab-bag of tools to make my apps better along several axes, and doesn’t burden me with a huge amount of needless churn just to tread water.

My favorite WWDCs are the ones where iPad gets a lot of love — there aren’t many of them, and no signs whatsoever that this year will be one of those years.

(A GOAT WWDC would be one where they introduce a true cross-platform successor to UIKit and AppKit and back away from the SwiftUI dumpster-fire)

Previously:

• WWDC 2025 Wish Lists

Update (2026-06-04): Imthaz Ahamed:

I wrote mine a month ago.

1. A Snow Leopard year where focus is on quality
2. Siri that is competent, and Siri being able to talk across devices (like ask Siri on my iPhone what my iPad battery level is at)
3. Apple Watch Independence — this is long overdue, I want Apple Watch to not be tied to one iPhone, but be able to connect/switch to different iPhones(or even iPads!). Maybe a toggle in the Watch control centre.

Tim Schmitz:

Here’s my WWDC wish list entry: When I say “Hey Siri, add hot salsa to my grocery list,” add a single item called “hot salsa” instead of two unrelated items called “hot” and “salsa,” which it currently does every. single. time. 🤦‍♂️

Yep.

Matt Massicotte:

Here’s my “watchlist” of things I’ll be paying special attention to.

Update (2026-06-05): Rui Carmo:

My expectations are effectively rock-bottom by now. Apple has become a hardware company where software seems to have been tacked on as a somewhat under-maintained afterthought. But I can’t help but keep a scorecard, so here’s what I’m hoping for–in rough order of how often it ruins my week.

[…]

I want Mail to be automatable again. Not necessarily the full plugin API they killed, but an AppleScript dictionary that isn’t frozen in amber and a MailKit surface that can file, tag and search without ceremony–because the one app I live in all day is the one black box I can’t point an agent at. While they’re at it, smart folders and rules that sync from the Mac should finally arrive on iOS, roughly twenty years late.

Spotlight should simply find things that exist. I’d settle for that alone–no AI, no reinvention–just reliable, complete results and the one-line reindex affordance the Mac has had for years made available on iOS, so a corrupted index doesn’t mean a multi-hour restore that breaks Apple Pay and FaceID along the way.

[…]

Stabilise SwiftUI or admit it’s a research project. Views that worked on iOS 17 behave differently on 18 and seem broken on 26, and I lose hours dropping to UIKit to dodge layout bugs reported years ago.

Juli Clover:

Some of the same features that are coming in iOS 27 will come to macOS 27, like the new version of Siri and the dedicated Siri app, but we want to hear from MacRumors readers. What are you hoping to see in macOS 27?

Do you want updates to Liquid Glass? Changes to multitasking? Bug fixes? Better external display support? Improved memory management since no one can afford RAM anymore?

App Store Apple Software Quality Artificial Intelligence Foundation Models Framework iCloud Icon Composer iOS iOS 27 iPadOS iPadOS 27 Liquid Glass Mac Mac App Store macOS 27 Golden Gate Model Context Protocol (MCP) Programming Shortcuts Siri Swift Concurrency Swift Programming Language SwiftNIO SwiftUI Text Kit Wallet watchOS watchOS 27 WWDC Xcode Xcode Cloud

19 Comments

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---