In CoreData, Dates are saved with a time interval from a reference date (which is 2001-01-01 00:00:00). The date field is "optional' in CoreData, and when saving 'nil', the value sent to CloudKit is the reference date, and when accessing the date, for CoreData it is not nil, I have the reference data as a value. One workaround could be something like : date.timeIntervalSinceReferenceDate != .zero but just no

CloudKit dashboard: date is nil when created and when editing we have to delete each part of the date manually and save. It seems to be a problem with CoreData + CloudKit sync, still searching

Agree, a lot of great developers have tried MVVM / The Clean Architecture (TCA) first with SwiftUI, and now, the same developers are going back and all say "Use simply SwiftUI and learn how it works - it just works with no BS" And you can always optimise your views when needed (re-rendering != re-evaluating, SwiftUI is smarter every year)

Hello and thank you for this awesome thread. I agree with you on this, and SwiftUI is a completely new way of thinking for iOS. It's like when you are developing using ECS instead of OOP. And again, it depends your app and/or feature. You are not limited to one-exclusive pattern or achitecture for your app. I have some questions about this, and your last post is perfect as an example.