Watch my WWDC session to learn how to easily adopt Swift concurrency in your app with new Swift 6.2 features🤩 #WWDC25 developer.apple.com/videos/p…

What a great day!! We were BLOWN AWAY by the quality of projects people built in 3 hours at Bitrig Hacks! And a massive thank you to our judges, @simanerush @AriX @yumaSoerianto @davemorin @bradflora @lllucas

New for Apple developers: Foundation Models support for Claude lets developers use Apple's Foundation Models framework to call Claude for multi-step reasoning, code generation, and longer context.

Getting day 3 started with the SwiftUI group lab #WWDC #WWDC26

If you missed it, the recording of today's SwiftUI Group Lab is now available on YouTube: youtube.com/live/7g-Xg5xiH4o

So many great questions in the #WWDC SwiftUI group lab this morning! There’s one more tomorrow evening that you won’t want to miss. Bring your questions, or just watch to learn a ton of interesting stuff. developer.apple.com/videos/p…

Tomorrow at 9am, come join us for the SwiftUI Group Lab! We’re looking forward to answering your questions! developer.apple.com/videos/p…

SwiftUI’s new type-checking enhancements (`@ContentBuilder`) and lazy `@State` are the culmination of literally years of careful effort behind the scenes to solve some of the biggest everyday pain points in SwiftUI development. At this point, there are millions of lines of SwiftUI result builder and state code shipping in production. With these changes, every one of those lines of code will suddenly compile differently, improving both compilation and runtime performance, and most developers *will never even notice*. That doesn’t normally happen. Maintaining binary, source, and backwards compatibility across releases imposes strict limitations on how SDK APIs can evolve. If you think of a better way to compile some library DSL syntax after shipping it publicly, you’re usually out of luck. These enhancements were only possible because of dedicated engineers on the Swift and SwiftUI teams working closely together, sweating the subtlest of details, and persevering through countless dead-end experiments and fraught internal deployments. Their reward? That future developers will *not* see some type-check error or performance hitch, and will *never* have to know that it ever worked any differently. But that’s wonderful. We love it. The joy is in the doing. Thank you @slazaruseth, @daniel_duan, @hollyborla, Pavel Yaskevich, and others from the Swift and SwiftUI teams for getting these enhancements over the finish line! (I’m no longer at Apple but can’t help but brag about these talented people 👏🏻)

> Maintaining binary, source, and backwards compatibility across releases imposes strict limitations on how SDK APIs can evolve. You can learn more about how we achieved this while making @.State lazy here: x.com/i/status/2064195688469…

This is a great tip for diagnosing and improving the performance of ForEach!

The recording of SwiftUI for Beginners Group Lab is now available on YouTube! Go check it out in case you missed it: youtube.com/watch?v=IbNHuOt5…

Tune in to the SwiftUI Beginner Group Lab tomorrow! Sign up here: developer.apple.com/videos/p…

Happy #WWDC26!

A great behind-the-scenes improvement is ContentBuilder – which has been a massive undertaking – and delivers meaningful improvements to type checking performance.

Hope you like lazy stuff cause we made State and AsyncImage lazy.

Today, Xcode ships with agent skills for SwiftUI (with the ability to export them to use with any agent). These skills will help you and your agent create modern, idiomatic, and performant SwiftUI and make the best use of brand-new APIs. We have synthesized best practices of years of adoption for SwiftUI with context and explanation to help you build amazing and powerful apps. Let us know what you think!

State Macro 🥳

We've got a killer group of judges for Bitrig's WWDC Hackathon on 6/10. It's going to be a ton of fun 🙂

I’m so excited to see all of your amazing projects at Bitrig Hacks!