Coordinator pattern in iOS Swift - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use the Coordinator pattern in iOS apps?

Which of the following best explains the main benefit of using the Coordinator pattern in an iOS app?

A It centralizes navigation logic to keep view controllers simple and focused on UI.

B It automatically generates UI layouts without coding.

C It replaces the need for storyboards entirely.

D It manages app data persistence across launches.

💡 Hint

Think about how navigation and screen transitions are handled in an app.

The Coordinator pattern helps by moving navigation code out of view controllers, making them easier to maintain and test.

❓ ui_behavior

intermediate

Coordinator navigation flow

Given a Coordinator that starts with a Login screen and then shows a Home screen after successful login, what happens when the user logs in?

iOS Swift

class AppCoordinator: Coordinator {
  func start() {
    showLogin()
  }
  func showLogin() {
    let loginVC = LoginViewController()
    loginVC.onLoginSuccess = { [weak self] in
      self?.showHome()
    }
    navigationController.pushViewController(loginVC, animated: true)
  }
  func showHome() {
    let homeVC = HomeViewController()
    navigationController.pushViewController(homeVC, animated: true)
  }
}

A The app replaces Login screen with Home screen without animation.

B The app pushes Login screen, then pushes Home screen on login success.

C The app shows Login and Home screens side by side.

D The app pops Login screen and then pushes Home screen.

💡 Hint

Look at how navigationController is used to push view controllers.

The code pushes Login screen first. When login succeeds, it pushes Home screen on top, so user sees Home next.

❓ lifecycle

advanced

Coordinator memory management

What is the main reason to use [weak self] in closures inside a Coordinator?

iOS Swift

loginVC.onLoginSuccess = { [weak self] in
  self?.showHome()
}

A To prevent a strong reference cycle that causes memory leaks.

B To make the closure run on a background thread.

C To ensure the closure runs only once.

D To allow the closure to modify self even if it is nil.

💡 Hint

Think about what happens if self holds a strong reference to the closure and vice versa.

Using [weak self] avoids retain cycles between the Coordinator and closures, preventing memory leaks.

❓ navigation

advanced

Handling child coordinators

In a Coordinator pattern, why do we keep a strong reference to child coordinators?

A To allow child coordinators to access the parent view controller directly.

B To enable child coordinators to modify the app delegate.

C To keep child coordinators alive while they manage their flows and prevent them from being deallocated.

D To automatically save child coordinator state to disk.

💡 Hint

Think about what happens if a child coordinator is not strongly referenced.

Without a strong reference, child coordinators get deallocated immediately, breaking navigation flow.

📝 Syntax

expert

Correct Coordinator protocol definition

Which option correctly defines a Coordinator protocol with a start() method and a navigationController property?

A

protocol Coordinator {
  var navigationController: UINavigationController? { get }
  func start() -> Void
}

B

protocol Coordinator {
  var navigationController: UINavigationController? { get set }
  func start() -> Int
}

C

protocol Coordinator {
  var navigationController: UINavigationController { get set }
  func start()
}

D

protocol Coordinator {
  var navigationController: UINavigationController { get }
  func start()
}

💡 Hint

The navigationController should be readable but not necessarily writable. start() returns nothing.

Option D correctly declares a read-only navigationController and a start method with no return value.

Practice

1. What is the main purpose of the Coordinator pattern in iOS development?

easy

A. To separate navigation logic from view controllers

B. To manage data persistence

C. To handle network requests

D. To style UI components

Solution

1. Step 1: Understand the role of Coordinator

   The Coordinator pattern is designed to manage navigation and screen flow in an app.

2. Step 2: Compare with other options

   Data persistence, network requests, and UI styling are handled by other parts of the app, not the Coordinator.

3. Final Answer:

   To separate navigation logic from view controllers -> Option A

4. Quick Check:

   Coordinator = navigation separation [OK]

Hint: Coordinator handles navigation, not data or UI [OK]

Common Mistakes:

• Confusing Coordinator with data managers
• Thinking Coordinator styles UI
• Assuming Coordinator handles network calls

2. Which of the following is the correct way to declare a basic Coordinator protocol in Swift?

easy

A. protocol Coordinator { func start() }

B. class Coordinator { func start() {} }

C. struct Coordinator { var start: () -> Void }

D. enum Coordinator { case start }

Solution

1. Step 1: Identify protocol syntax

   In Swift, protocols are declared with the protocol keyword and define method signatures without implementation.

2. Step 2: Check each option

   protocol Coordinator { func start() } correctly declares a protocol with a start() method signature. class Coordinator { func start() {} } is a class, not a protocol. struct Coordinator { var start: () -> Void } is a struct with a closure property, not a protocol. enum Coordinator { case start } is an enum, which is not used for protocols.

3. Final Answer:

   protocol Coordinator { func start() } -> Option A

4. Quick Check:

   Protocol syntax = protocol Coordinator { func start() } [OK]

Hint: Protocols use 'protocol' keyword and method signatures only [OK]

Common Mistakes:

• Using class instead of protocol
• Adding method implementation in protocol
• Confusing struct or enum with protocol

3. Given this Coordinator code snippet, what will be printed when appCoordinator.start() is called?

protocol Coordinator {
  func start()
}

class AppCoordinator: Coordinator {
  func start() {
    print("App started")
  }
}

let appCoordinator = AppCoordinator()
appCoordinator.start()

medium

A. start() method not found

B. No output

C. Compilation error

D. App started

Solution

1. Step 1: Analyze the class and method

   The AppCoordinator class implements the start() method which prints "App started".

2. Step 2: Check method call

   Calling appCoordinator.start() executes the print statement inside start().

3. Final Answer:

   App started -> Option D

4. Quick Check:

   Method call prints message [OK]

Hint: Calling start() runs its print statement [OK]

Common Mistakes:

• Assuming start() is missing
• Thinking code won't compile
• Expecting no output

4. Identify the error in this Coordinator implementation:

protocol Coordinator {
  func start()
}

class MainCoordinator: Coordinator {
  func start() {
    print("Starting main flow")
  }

  func startFlow() {
    print("Flow started")
  }
}

medium

A. startFlow() method is not part of the protocol

B. No error, code is correct

C. Missing start() method implementation

D. Protocol should be a class, not protocol

Solution

1. Step 1: Check protocol conformance

   The MainCoordinator class implements the required start() method from the Coordinator protocol.

2. Step 2: Verify additional methods

   Having extra methods like startFlow() is allowed and does not cause errors.

3. Final Answer:

   No error, code is correct -> Option B

4. Quick Check:

   Extra methods allowed, required methods implemented [OK]

Hint: Extra methods don't cause errors if required ones exist [OK]

Common Mistakes:

• Thinking extra methods must be in protocol
• Assuming missing methods cause errors
• Confusing protocol with class requirements

5. You want to start a login flow from your MainCoordinator and then show the home screen after login. Which approach best uses the Coordinator pattern to handle this navigation?

hard

A. LoginCoordinator handles login and home screens without notifying MainCoordinator

B. MainCoordinator directly pushes login and home view controllers without coordinators

C. MainCoordinator creates and starts a LoginCoordinator, then listens for login completion to start HomeCoordinator

D. Use a single view controller to manage login and home screens

Solution

1. Step 1: Understand Coordinator responsibilities

   MainCoordinator should manage the overall flow and delegate specific flows to child coordinators like LoginCoordinator.

2. Step 2: Evaluate navigation flow

   MainCoordinator creates LoginCoordinator to handle login, then listens for completion to start HomeCoordinator, keeping navigation logic centralized.

3. Step 3: Compare other options

   The other options break separation of concerns or do not coordinate flows properly.

4. Final Answer:

   MainCoordinator creates and starts a LoginCoordinator, then listens for login completion to start HomeCoordinator -> Option C

5. Quick Check:

   Parent coordinator manages child flows [OK]

Hint: Parent coordinator controls child coordinators and flow [OK]

Common Mistakes:

• Handling navigation only in view controllers
• Child coordinators acting independently
• Mixing multiple screens in one view controller