How does the Coordinator pattern decouple navigation, and what are its components?

WHAT THIS TESTS: This question probes your ability to recognize and fix architectural coupling in UIKit. Interviewers want to see that you understand view controllers are view objects prefixed with UI and should not own flow logic, and that you can articulate how a higher-level object can marshal view controllers without creating a massive central router.

A GOOD ANSWER COVERS: First, the motivation: view controllers often entangle flow logic, view logic, and business logic, which prevents reuse in extensions, iPads, or A/B tests. Second, the solution: a Coordinator is a plain old NSObject that takes over navigation and flow decisions, so each view controller becomes an island that only binds a model to a view. Third, the structure: an AppCoordinator lives in the app delegate and owns an array of child coordinators; each child might manage a navigation controller or a specific flow like authentication or photo creation. Fourth, memory management: coordinators are retained in a parent array and must be removed when a flow completes to avoid leaks.

COMMON WRONG ANSWERS: Calling the Coordinator a router or a replacement for the navigation controller misses the point; it is an object that decides what comes next, not one that merely pushes view controllers. Another red flag is suggesting a singleton coordinator or a single global instance, which destroys modularity. Failing to mention the child coordinator array and the parent-child tree shows you have not thought through retain cycles or deallocation. Finally, saying view controllers communicate back via delegates is correct, but omitting that the coordinator implements those delegates to decide the next step is incomplete.

LIKELY FOLLOW-UPS: How do you handle deep linking or state restoration with coordinators? How would you adapt this pattern to SwiftUI? What happens when a coordinator needs to pass data back up the tree? How do you prevent retain cycles between the coordinator and the view controllers it presents? Can you mix coordinators with MVVM or Clean Architecture?

ONE CONCRETE EXAMPLE: Imagine an Instagram-style photo creation flow. The AppCoordinator has a root view controller and an array of child coordinators. When the user taps Create, the AppCoordinator allocates a PhotoCreationCoordinator, adds it to the childCoordinators array, and calls beginPhotoCreationProcess. That coordinator creates a photo selection view controller, sets itself as the delegate, and presents it. When the user finishes or cancels, the PhotoCreationCoordinator informs its delegate, the AppCoordinator, which removes it from the childCoordinators array. None of the view controllers in that flow know about each other, and the flow logic lives in one place.

Source: khanlou.com