WWDC26 starts in 27 days. The keynote is on June 8 at 10:00 AM Pacific Time at Apple Park, with an in-person component for selected developers and students. Technical sessions continue online through June 12 with more than 100 videos and bookable labs with Apple engineers.
No hardware announcements are confirmed for WWDC26. The format is the usual software conference: a keynote with platform highlights, the State of the Union session the same day for developers, then a dense week of technical sessions, labs, and appointments with Apple teams.
What’s almost certain
iOS 27, iPadOS 27, macOS 27, watchOS 27, tvOS 27, and visionOS 27 are the expected headline announcements. The macOS 27 name hasn’t been leaked. First developer betas will be available shortly after the keynote — likely the evening of June 8.
Apple has indicated that the engineering focus this cycle is on software quality: reducing technical debt, fixing structural bugs, and improving baseline performance. That’s a statement Apple makes most years, so it shouldn’t be taken literally. What’s concrete is that the iOS 26 release cycle included notable performance revisions in several point releases. If that pattern continues into iOS 27’s betas, the early builds may be more stable than usual.
Apple Intelligence will receive updates. The developer-facing APIs around Foundation Models, Writing Tools, and Siri intents are the areas where the most practical changes for app developers are likely to emerge.
What isn’t known yet
There are no credible, verified leaks about specific API changes or App Store policy updates for iOS 27. Hardware announcements — new Macs, chip updates — are not typical for WWDC, which remains a software conference. Any hardware announcement on keynote day would be a genuine surprise.
Changes to App Review Guidelines, entitlements, privacy requirements, or DMA obligations are not pre-announced before WWDC. It’s worth waiting for the keynote and SDK release notes rather than planning around speculation.
What’s worth doing now
Several things are easier to handle before the new SDKs arrive than during the beta period:
Minimum iOS version audit. If the app still supports iOS 24 or earlier, WWDC is typically when Apple updates its recommended minimum targets. Having an installed-base analysis ready lets you make that call quickly after the keynote rather than spending the beta weeks on the decision.
CI and Xcode. Pipelines using provider-managed Xcode should be pinned to Xcode 26.5 (released May 11) before Xcode 27 betas appear. Having a stable pipeline on the current release reduces the number of variables to manage once beta season starts.
Third-party dependencies and SDKs. Early iOS/macOS 27 betas can break dependencies that haven’t been updated for compatibility. Inventorying external frameworks, analytics SDKs, payment libraries, and mapping integrations — and checking whether vendors have communicated iOS 27 support plans — is an operation that goes much faster before the beta cycle than in the middle of it.
TestFlight and certificates. Provisioning profiles and distribution certificates expire independently of WWDC. Checking expiration dates before the end of May prevents operational blockers during the beta period.
Labs and sessions
Apple offers technical labs and individual appointments with its engineers throughout the conference week. Bookings typically open after the keynote. Labs are particularly useful for specific questions about APIs, App Review, entitlements, or platform compatibility — one of the few times during the year to get direct answers from the people who wrote the code.
Session videos remain available after the conference at developer.apple.com without registration.
On keynote day, it’s worth monitoring the SDK release notes and updated App Review Guidelines in parallel with the keynote stream. Developer-specific operational details rarely surface in the keynote itself, which is consumer-oriented, but appear in documentation released alongside it.
