swift-data-flow

@StateObject and @ObservedObject manage reference types in SwiftUI, but @StateObject initializes and owns the object for the view's lifetime, while @ObservedObject only observes an object owned elsewhere to prevent premature destruction.

Use @Observable for modern SwiftUI state management on iOS 17+, which simplifies data flow tracking, versus the legacy ObservableObject pattern using @Published that requires explicit property declaration for view updates.

Choose the right SwiftUI property wrapper for data flow by evaluating data ownership and access needs: use @State for local value types, @Binding for child view sharing, and @Environment for app-wide dependency injection.

Common SwiftUI state management anti-patterns include misusing @ObservedObject for local object ownership instead of @StateObject, and overusing global @EnvironmentObject when localized @Binding passing would preserve better view encapsulation.

Yes, you can use @Environment to share data across SwiftUI views without passing bindings manually, allowing parent views to inject objects that any descendant view can read directly via the environment.