swiftui-views

Apply the container/presentational split where a Root view owns state and a pure presentation view renders UI, using an @Observable view model to centralize state and ensure compile-time safety.

The container/presentational split in SwiftUI separates a Root view that owns state and data from a pure presentation view that renders UI, ensuring reusable and testable components across screens.

Implement typed navigation in SwiftUI by using guided navigation routing with a minimal navigation path, managed through an @Observable view model to handle navigation callbacks safely.

Yes, the architecture enforces fully previewable UI components by using stateless presentation views that render purely from state, allowing robust previews without requiring the full Root container.

Add accessibility labels to SwiftUI presentation views by following the built-in accessibility best practices provided in the architecture playbook, ensuring efficient rendering and robust support.

Use an @Observable view model when you need centralized, testable state management with compile-time safety across screens, rather than isolated local state within individual views.