WWDC26 Group Labs

Illustration inspired by Apple's official Group Lab covers, featuring Jorge's animated character icon over a circle with the text "Jorge's Group Lab Guide WWDC26". Illustration inspired by Apple's official Group Lab covers, featuring Jorge's animated character icon over a circle with the text "Jorge's Group Lab Guide WWDC26".

Table of contents

My Problem 🤔

When I published my WWDC26 video guide, I devoted Block 17 to the Group Labs with barely a line of context per session. The reason was simple: Apple’s official descriptions are practically identical to one another —“Join us to dive deeper into WWDC26 with Apple engineers”— and they say nothing useful about what was actually discussed inside.

What I didn’t share back then is that, before writing that block, I had started watching the Group Labs and got a surprise. They are not passive sessions. They are live Q&A rounds between real developers and engineers from the Apple team, and the quality of the questions and answers is very different from that of regular sessions. In ordinary sessions, Apple shows what it wants to show. In the Group Labs, developers ask what they really need to know, and the engineers answer directly.

The problem is that this content is practically invisible. There are no transcripts, no index, no way to search inside the video. If you don’t sit down and watch the whole session, you don’t know what it covers.

I started taking notes. One session, then another, and I ended up with eighteen.

My Solution 🧩

I decided to transcribe and structure the content of each Group Lab: the topics asked about, the exact timecode, the summarized answer and which engineers took part. The goal was to have something searchable, something that would let me jump straight to the minute I care about instead of digging blindly through the video.

Before the list, three examples of what came up inside and that you won’t find in any main session:

  • In the Swift Group Lab, the language team explained why they would have designed concurrency differently if they were starting today, and what changed in Swift 6.2 to fix the model.
  • In the SwiftUI Group Lab, the engineers broke down when to use AnyView, how DynamicProperty runs before body, and why conditionals inside lazy containers are an antipattern.
  • In the Apple Intelligence Group Lab, the team explained the real differences between App Schemas and IndexEntity, and the current limits of video support in Foundation Models.

Here are all the available sessions, with a direct link to the official video:

Language and data

  • Swift Group Lab — Concurrency, performance, SwiftPM and language features.
  • SwiftData Group Lab — ResultsObserver, HistoryObserver, the new Codable, CloudKit sync, migrations and concurrency.

SwiftUI

Tooling and performance

Platforms and web

Intelligence, ML and AI

Quality and distribution

My Result 🎯

The value of the Group Labs is not in the official descriptions —it’s inside. Developer questions surface the use cases Apple doesn’t cover in the main sessions: the bugs the team acknowledges, the design decisions they explain off the record, the patterns they recommend in practice and not in marketing.

If you already have my video guide as a map of the catalog, the Group Labs are the layer on top: where Apple engineers really talk about what they built.

Keep coding, keep running 🏃‍♂️