swiftui-view-refactor

Split the body into dedicated subview types with small explicit inputs like data, bindings, and callbacks. Move business logic into services or models, keep only thin orchestration in the view, and reorder members so environment, state, init, body, and helpers follow a consistent top-to-bottom order.

Default to MV: views act as lightweight state expressions using @State, @Environment, @Query, and lifecycle modifiers, with business logic in services and models. Introduce a view model only when explicitly requested, required by existing code, or when shared presentation state genuinely needs a long-lived reference object.

Store @Observable reference types as @State in the owning view on iOS 17 and later, and pass them down explicitly to child views. For deployment targets including iOS 16 or earlier, use @StateObject at the owner and @ObservedObject for injected legacy observable models.

Computed some View helpers hide structure and make large screens harder to reason about when overused. Dedicated subview types get their own identity, state, previews, and explicit inputs, which improves stability and testability; keep computed helpers rare and small.

Avoid a view model when it would only mirror local view state, wrap environment dependencies, duplicate @Query or Binding data flow, or exist just because the body is too long. Split the view into smaller types and move logic into services instead of adding indirection.