Offline-first behavior on iOS is not a cache toggle. It is a persistence decision that makes the device store the place where screens read, edits land, and state survives launch interruptions, suspension, and connectivity loss. Apple describes Core Data as a framework for saving permanent data for offline use on a single device, while SwiftData organizes persistent models around a ModelContainer and ModelContext that manage storage and lifecycle. Once that local layer becomes authoritative, the network stops being a prerequisite for ordinary interaction and becomes a synchronization transport instead. Local State Defines Availability In practice, that means views should render from disk-backed state, not straight from requests. The broader offline-first pattern formalizes the local data source as the canonical read path, and Apple’s history APIs reinforce the same idea by tracking changes over time so that later reconciliation can be incremental rather than a full refresh. SwiftData History, for example, records ordered transactions and changes, which is exactly the raw material needed for server sync and extension-driven updates.