swiftui-view-refactor

Refactor large SwiftUI views by extracting small, explicit subviews and applying an MV-first data flow. This approach clarifies dependencies, stabilizes the view tree, and removes inline logic from the body for better readability.

Separate business logic from SwiftUI views by adopting an MV-first architecture that uses explicit dependency injection and correct Observation usage to stabilize the view tree and increase testability.

No, this approach is strictly for refactoring existing SwiftUI files to improve structure. For new page patterns or initial designs, you should switch to SwiftUI UI patterns instead of applying this refactoring logic.

Ensure the refactored SwiftUI code builds successfully by running a final verify-ios-build check in the project environment after any changes are made to the Xcode project.

You should not use this refactoring approach for non-SwiftUI files, general page implementations, or new page designs. It is specifically scoped to restructure existing SwiftUI views only.