fatbobman.com
WWDC 2025 First Impressions - As Expected, Yet Unexpected
Excerpt
One regret: I tested several reproducible SwiftUI bugs I’d encountered over the past year, and they remain in beta 1. I believe that addressing stability issues and improving performance will need to remain SwiftUI’s top priorities for some time to come. ## SwiftData SwiftData added only one feature this year—model inheritance—which isn’t widely used by most developers. Other highly requested capabilities, such as additional sync options (shared, public) and dynamic predicate adjustments, didn’t materialize in this release. That said, this update isn’t a failure. By fixing several critical bugs from previous versions and filling in some long-overdue functionality, SwiftData in Xcode 26 has become increasingly viable for real-world apps. - A bug preventing view updates when mutating data under `@ModelActor` has been resolved. - For model properties conforming to `Codable`, you can now use those properties in predicates. Remarkably, both fixes remain backward compatible to iOS 17. ... > In Xcode 26 beta 1, model inheritance and enum-typed properties still exhibit some bugs, but I expect those to be ironed out before the final release. It’s also highly likely that enums with `RawValue` will be queryable directly in predicates. Once Xcode 26 ships, I believe SwiftData can genuinely be a primary choice for persistence in most apps.
Related Pain Points
SwiftUI has unresolved stability and performance issues
7Multiple reproducible bugs in SwiftUI persist across beta releases, indicating that stability and performance remain unaddressed top priorities. Developers encounter recurring issues that block reliable deployment of SwiftUI-based apps.
SwiftData lacks highly requested synchronization and querying features
6SwiftData does not provide additional sync options (shared, public) or dynamic predicate adjustments that developers widely request. Feature gaps limit its viability for many real-world applications despite recent bug fixes.