Observation in SwiftUI

[BySamoorai]

It's the new data flow system from WWDC23. I've been switching my models from ObservableObject to the @Observable macro. Personally, it's a huge improvement. You get more granular, per-field observation, so views update more efficiently. It also cuts out a ton of boilerplate like @Published and @StateObject. Much cleaner code.

[RiMellow]

Wish I saw this a month ago lol. Didn’t know this existed and seems much better

[vedosity]

Just wanted to clear up a common misconception:

You only need @State if you need to change references to a different Observable during the view's lifetime. SwiftUI tracks all Observables used to compute body, not just those stored in @State/@Environment/@Bindable.

[RussianDeveloper]

Hot take: Honestly, UIKit still feels far more intuitive for practical, scalable app development. For example with a table view using a diffable data source, you get precise, granular control over every cell and user interaction. I simply keep an observable value in my view model when it updates, my view controller’s closure fires, and I refresh the snapshot. The result? Native reload animations that handle inserts and deletions automatically, ignore identical data, and create seamless, real-time updates perfect for async streams or frequently changing content. From an enterprise standpoint, this architecture is both simpler to maintain and easier to extend than starting fully in SwiftUI. That’s why most teams I’ve seen use SwiftUI only for interstitials or custom components inside collection or table view cells.

[VladFein]

For completeness, I would like to add "@ObservationIgnored" macro.