Thank you to the #SwiftData team for their Group Lab! You all rock and I always learn so much. #wwdc26

#SwiftData and the improvements to it this year at #WWDC are great.

Except if you use CloudKit and your queries are updated repeatedly regardless of if the data has changes.

You won’t notice it for simple views but anything complex will re-render, be slow and possibly flash, etc.

I’ve seen Apple engineers suggest that can happen please provide feedback. I have.

This is why the yearly update cycle sucks. Maybe next time.

So back to manual fetches and a view model (or ??)

Sigh.

Something I didn’t see someone mention during the #WWDC26 is that #SwiftData now supports dynamic compound predicates!

Haven’t tested it, but looks like a great extension to the already existing static compound predicates.

https://developer.apple.com/forums/thread/832230

Dynamic Compound Predicates | Apple Developer Forums

🎉 SwiftData Architecture Book is now Available!

Includes iOS 27 Features.

https://azamsharp.school/swiftdata-architecture.html

#iosdev #swiftdata #swiftui

There's a shocker near the end of the #wwdc26 session: Code-along: Add persistence with SwiftData (see screenshot)

It's a work around for not being able to use didSet in @.Model class. Since the view puts the observation token inside the activity model it means the activity can only be monitored in one View at a time. So it should really be activity.itemViewToken and need to be sure no ActivityItemView exists for the same activity. But likely causes a retain cycle and a memory leak.

#Swiftdata

Some of the new features in SwiftData are incredible. However we still don’t have a way to add collaboration to apps using #SwiftData feels like something we are never going to get ☹️

Infinite Scrolling in SwiftData Using Fetch Limits and Offsets
https://azamsharp.teachable.com/courses/azamsharp-pro-for-all-content/lectures/65898240

#iosdev #swiftui #swiftdata

[Member Only Video]

Why I chose SwiftData + CloudKit for Roost — even though
they're still rough at the edges:

✅ Apple ID-only auth (no third-party backend)
✅ Private database = Apple can't read user data
✅ Zero server cost for me as an indie

The trade-off: CloudKit's relationship rules took me 2 hours
to debug today (turns out both sides of a one-to-many need
to be declared, not just the inverse side).
But for a local-first app, the privacy trade-off is worth it.

#SwiftData #CloudKit #indiedev #iOSDev

Ensembles 3 is here. 🎉

A local-first sync framework for Core Data & SwiftData. No server, no cloud bill, no lock-in — your data syncs through services your users already have (iCloud, Dropbox, WebDAV…), or peer-to-peer.

I built it before the world moved to the cloud. It was almost end-of-life, but, lately, the world's been coming back around to local-first.

It's free to use with CloudKit and SwiftData/CoreData.

https://ensembles.io

#localfirst #SwiftLang #CoreData #SwiftData

Ensembles — Sync for Swift Developers

The local-first sync framework for Apple platforms. Sync via existing cloud services. No server required. No cloud costs.