mvvm-uikit-architecture

Migrate a UIKit MVC codebase to MVVM safely by scaffolding a dedicated refactoring/ directory and iteratively extracting ViewModels from existing view controllers using a phased workflow. This production-first approach enforces testable PR workflows for staged refactoring.

Enforce zero UIKit imports in ViewModels by adopting a strict ViewState enum for asynchronous data flow. This pattern separates view logic entirely, ensuring ViewModels remain testable and independent of UIKit dependencies.

The best way to implement Coordinator-based navigation in a large UIKit app is by combining it with dependency injection via constructors. This ensures scalable, testable navigation flows decoupled from view controllers.

Yes, you can use DiffableDataSource with programmatic Auto Layout when migrating to MVVM. This combination is supported within the phased refactoring workflow to modernize data-driven UIKit views safely.

MVVM refactoring is suitable for enterprise iOS applications because it prioritizes testability, maintainability, and scalable navigation patterns. It enforces strict guidelines like constructor-based dependency injection and testable PR workflows.

UIKit to MVVM migrations often fail testability checks when ViewModels contain UIKit imports or lack constructor-based dependency injection. Enforcing a strict ViewState enum and DI via constructors resolves these testability failures.