swiftui-view-refactor

Refactor SwiftUI views by reordering property declarations top-to-bottom: Environment, access modifiers, @State, stored properties, computed vars, init, body, and helpers. This standardization improves readability and maintainability across multi-file view architectures.

Split large SwiftUI views into subviews when the body or computed views become too complex to read easily. Extracting dedicated subviews improves maintainability and aligns with MV-pattern guidance for lightweight view architectures.

Keep @Observable state objects at the root view level and pass them down explicitly to children. This state management approach ensures clear ownership and consistent observation tracking throughout your SwiftUI view hierarchy.

Environment-based dependency injection passes services into SwiftUI views via @Environment rather than view models. This MV-pattern approach minimizes view-model usage and keeps views lightweight by relying on the environment for dependencies.

Yes, you can minimize or eliminate view models by using @Observable state directly. Keep observable objects at the root state level and inject services via @Environment to achieve non-optional view model usage where possible.