@StateObject

What @StateObject does in SwiftUI

@StateObject is about ownership, not just observation. It tells SwiftUI to create an ObservableObject for a view and keep that instance alive across redraws, so the view keeps a stable source of truth even as SwiftUI rebuilds the body many times.

This matters because SwiftUI views are value types and can be recreated frequently. Without a persistent owner, object state can be reset, duplicated, or initialized at the wrong time, which can produce flickering UI, lost local state, or repeated side effects.

How it differs from @ObservedObject

@ObservedObject is for an object created and owned elsewhere. @StateObject is for the view that should own the object’s lifecycle. That distinction is practical, because the wrong wrapper can cause SwiftUI to treat the model as disposable when it should actually be preserved.

In real code, the choice usually depends on where the model comes from. If a parent injects it, observation is often enough. If the view itself needs to create the model once and retain it, @StateObject is the correct fit.

Why lifecycle stability matters

The main value of @StateObject is lifecycle stability. It helps keep subscriptions, published properties, and local UI state attached to the same object identity rather than re-creating the object whenever the view updates.

That stability can also reduce subtle bugs in asynchronous views. For example, if a model starts a network load, subscribes to a data source, or tracks transient UI state, recreating it unnecessarily can restart work or discard progress.

Common mistakes and safe usage patterns

A common mistake is using @ObservedObject for an object the view itself creates. Another is placing initialization logic where it can run more than once, which defeats the purpose of keeping a single owned instance.

Use @StateObject when the view is the lifetime owner, and pass the object downward to child views that only need to observe it. That keeps ownership clear and avoids accidental reinitialization when the view hierarchy changes.