Coordinator pattern in iOS Swift - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Coordinator pattern in iOS development?

The Coordinator pattern is a design approach that helps manage navigation flow in an app by moving navigation logic out of view controllers into separate coordinator objects.

beginner

Why use the Coordinator pattern instead of handling navigation inside view controllers?

Using the Coordinator pattern keeps view controllers simple and focused on UI, improves code reuse, and makes navigation easier to manage and test.

beginner

In the Coordinator pattern, what is the role of a 'Coordinator'?

A Coordinator is an object that creates view controllers and handles navigation between them, coordinating the flow of screens.

intermediate

How does the Coordinator pattern improve app scalability?

By separating navigation logic, it makes adding new flows or screens easier without cluttering view controllers, supporting better app growth.

intermediate

What is a common way to start a Coordinator in Swift?

You create a class conforming to a Coordinator protocol with a start() method that sets up the initial view controller and navigation.

What does a Coordinator primarily manage in an iOS app?

A User interface layout

B Navigation flow between screens

C Data storage and retrieval

D Network requests

Coordinators handle navigation flow, moving this responsibility out of view controllers.

Which benefit does the Coordinator pattern provide?

A Makes view controllers responsible for navigation

B Automatically generates UI elements

C Removes the need for view controllers

D Simplifies view controllers by removing navigation logic

It simplifies view controllers by moving navigation logic to coordinators.

What method is commonly used to start a Coordinator?

A init()

B run()

C start()

D launch()

The start() method is typically used to begin the coordinator's flow.

How does the Coordinator pattern affect testing?

A Makes testing navigation easier

B Makes testing impossible

C Has no effect on testing

D Requires UI tests only

Separating navigation logic into coordinators makes it easier to test navigation flows.

Which of these is NOT a responsibility of a Coordinator?

A Managing business logic inside view controllers

B Handling navigation between screens

C Creating view controllers

D Starting the app flow

Business logic inside view controllers is not handled by coordinators.

Explain the Coordinator pattern and why it is useful in iOS app development.

Think about how navigation is usually handled and how coordinators change that.

Describe how you would implement a basic Coordinator in Swift.

Focus on the structure and main method of a coordinator.

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