SwiftUI is often explained as a tree of views that gets diffed every time state changes. After reverse engineering the framework’s behavior and comparing it with Apple’s granted patents, I arrived at a different mental model: SwiftUI is a single demand-driven attribute graph. In this session we’ll follow the data from @State through dependency tracking, invalidation, layout, rendering, and animation to understand why SwiftUI behaves the way it does. Instead of focusing on API usage, we’ll examine the underlying architecture and connect it to Core Animation and the rendering pipeline. The goal is to leave with a coherent mental model that explains many of SwiftUI’s seemingly mysterious behaviors.