Michael Freiwald

@freiwald.dev

📱 Developer on  platforms 👨‍💻 Mobile Consultant @ Netlight 💛 Love talking about Swift • SwiftUI • iOS 🏡 Interested in Smart Home & KNX 🇩🇪 Living in Munich with my family 👩‍❤️‍👨👧👶 Developer of @getskydeck.app & @getremark.app 🌐 https://freiwald.dev

I'm wondering how we’re supposed to support the design split between iOS 18 and iOS 26. If I just update my UI, it will also change the look & feel on iOS 18. Especially with custom implementations, I see a lot of extra work coming with `if #available(iOS 26.0, *)`. #WWDC25

in xcode 26, newly created projects have their default actor isolation set to MainActor, which means all types declared in the project will implicitly have `MainActor` added. it seems there should be an option to add this choice when creating the project.

Bild

SwiftData Bug Fixed! The issue where modifications to ModelActor in a private context were not immediately reflected in the view has been fixed. Additionally, this issue has been resolved for SwiftData applications compiled with Xcode 26 on iOS 18.