Adding to this, a solution might be enabling continuous releases and leaning into release channels could help in terms of getting more out to users.
In practice it's a challenge because the OS bundles a lot of separate things into releases, namely Safari changes are tied to OS changes which are tied to Apple Pay features which are tied to so on and so on.
It would require a lot of feature flagging and extra complexity which may reduce complexity.
Another way is to start un-bundling releases and fundamentally re-thinking how the dependency graph is structured.
I think they’re painted into a corner with WWDC. Everything has to be a crowd pleasing brain busting wow drop each year. I’m certain there are teams that design their entire workflow around the yearly wwdc. It honestly feels like an executive leadership problem to solve.
If that is a significant part of the problem, then moving WWDC from an in-person keynote attended mostly by nerds and glanced at by the media to an overproduced movie geared at the media and ordinary consumers first probably didn't help. They could've gone back to a stage presentation after COVID, but some of that transition had already been happening prior to that (I recall an increase in how many jokes/bits they were doing in the late 2010's, although that could just be my perception).
In practice it's a challenge because the OS bundles a lot of separate things into releases, namely Safari changes are tied to OS changes which are tied to Apple Pay features which are tied to so on and so on.
It would require a lot of feature flagging and extra complexity which may reduce complexity.
Another way is to start un-bundling releases and fundamentally re-thinking how the dependency graph is structured.