Why clean architecture maintains codebases in iOS Swift - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a protocol for the use case layer.

iOS Swift

protocol [1] {
    func execute()
}

Drag options to blanks, or click blank then click option'

AService

BUseCase

CModel

DViewController

Attempts:

3 left

💡 Hint

Common Mistakes

Using ViewController as protocol name mixes UI with business logic.

Using Model or Service does not clearly represent the use case layer.

The use case layer is defined by a protocol named UseCase to separate business logic from UI.

2fill in blank

medium

Complete the code to inject the dependency in the initializer.

iOS Swift

class Presenter {
    let useCase: [1]

    init(useCase: [1]) {
        self.useCase = useCase
    }
}

Drag options to blanks, or click blank then click option'

AUseCase

BUIViewController

CRepository

DService

Attempts:

3 left

💡 Hint

Common Mistakes

Using UIViewController mixes UI with business logic.

Using Repository or Service without protocol abstraction reduces flexibility.

Dependency injection uses the UseCase protocol to keep the presenter independent of concrete implementations.

3fill in blank

hard

Fix the error in the code by choosing the correct layer to handle data fetching.

iOS Swift

class [1] {
    func fetchData() {
        // fetch data from network or database
    }
}

Drag options to blanks, or click blank then click option'

ARepository

BViewController

CPresenter

DUseCase

Attempts:

3 left

💡 Hint

Common Mistakes

Putting fetchData in ViewController mixes UI with data logic.

Presenter or UseCase should not directly fetch data.

The Repository layer handles data fetching to separate data sources from business logic and UI.

4fill in blank

hard

Fill both blanks to complete the clean architecture layers interaction.

iOS Swift

class [1] {
    let repository: [2]

    func execute() {
        repository.fetchData()
    }
}

Drag options to blanks, or click blank then click option'

AUseCase

BViewController

CRepository

DPresenter

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing Presenter or ViewController with UseCase.

Assigning ViewController as repository type.

The UseCase calls the Repository to get data, keeping layers separate and maintainable.

5fill in blank

hard

Fill all three blanks to complete the flow from UI to data layer.

iOS Swift

class [1] {
    let useCase: [2]

    func present() {
        useCase.execute()
    }
}

class [3] {
    func fetchData() {}
}

Drag options to blanks, or click blank then click option'

APresenter

BUseCase

CRepository

DViewController

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing ViewController with Presenter or UseCase.

Assigning ViewController as data fetcher.

The Presenter calls the UseCase, which uses the Repository to fetch data, following clean architecture principles.

Practice

1. Why does clean architecture help maintain large iOS codebases?

easy

A. It separates code into layers with clear responsibilities.

B. It combines all code into one file for simplicity.

C. It removes all comments to reduce clutter.

D. It uses only one programming language.

Solution

1. Step 1: Understand the role of layers in clean architecture

   Clean architecture divides code into layers, each with a specific job, like UI, business logic, and data.

2. Step 2: Recognize how separation aids maintenance

   This separation keeps code organized and easier to change without affecting unrelated parts.

3. Final Answer:

   It separates code into layers with clear responsibilities. -> Option A

4. Quick Check:

   Layered code = easier maintenance [OK]

Hint: Think: separate jobs make code easier to manage [OK]

Common Mistakes:

• Thinking all code in one file is simpler
• Believing removing comments improves maintenance
• Assuming language choice affects architecture

2. Which Swift code snippet best shows separation of concerns in clean architecture?

easy

A. struct User { var name: String } // Model
class UserView { func display() {} } // View
class UserService { func fetch() {} } // Service

B. class User { var name: String; func display() {} func fetch() {} }

C. var name = "User"; func display() { print(name) }

D. struct UserView { var name: String; func fetch() {} }

Solution

1. Step 1: Identify separation of concerns

   struct User { var name: String } // Model class UserView { func display() {} } // View class UserService { func fetch() {} } // Service splits code into Model, View, and Service classes, each with a clear job.

2. Step 2: Compare with other options

   Other options mix responsibilities in one class or struct, breaking separation.

3. Final Answer:

   Separate Model, View, and Service classes. -> Option A

4. Quick Check:

   Separate classes = separation of concerns [OK]

Hint: Look for separate classes for data, UI, and logic [OK]

Common Mistakes:

• Mixing UI and data in one class
• Putting fetch logic inside view structs
• Ignoring separation in code structure

3. Given this Swift code snippet, what is the main benefit of using clean architecture here?

protocol UserRepository {
  func getUser() -> User
}

class UserInteractor {
  let repo: UserRepository
  init(repo: UserRepository) { self.repo = repo }
  func fetchUser() -> User { repo.getUser() }
}

medium

A. It tightly couples data fetching with UI code.

B. It makes the code run faster by combining layers.

C. It allows easy swapping of data sources without changing business logic.

D. It removes the need for protocols in Swift.

Solution

1. Step 1: Analyze the use of protocol and interactor

   The protocol defines a contract for data fetching, and the interactor uses it without knowing details.

2. Step 2: Understand benefit of abstraction

   This abstraction allows changing data source (e.g., network or database) without changing business logic.

3. Final Answer:

   Allows easy swapping of data sources without changing business logic. -> Option C

4. Quick Check:

   Protocol abstraction = flexible data sources [OK]

Hint: Protocols hide details, making swapping easy [OK]

Common Mistakes:

• Thinking it couples UI and data tightly
• Assuming faster runtime from layering
• Believing protocols are unnecessary

4. Identify the problem in this Swift code violating clean architecture principles:

class UserViewController {
  func fetchUser() {
    let user = UserService().getUser()
    print(user.name)
  }
}

class UserService {
  func getUser() -> User { User(name: "Alice") }
}

medium

A. UserService should be a struct, not a class.

B. UserService should not return a User object.

C. UserViewController should not print user name.

D. UserViewController directly calls UserService, mixing UI and data logic.

Solution

1. Step 1: Check responsibility of UserViewController

   UserViewController is UI code and should not directly fetch data from service layer.

2. Step 2: Identify violation of separation

   Direct call to UserService mixes UI and data logic, breaking clean architecture.

3. Final Answer:

   UserViewController directly calls UserService, mixing UI and data logic. -> Option D

4. Quick Check:

   UI should not directly access data services [OK]

Hint: UI layer should not call data services directly [OK]

Common Mistakes:

• Thinking printing user name is wrong
• Believing UserService must be struct
• Assuming UserService can't return User

5. How does clean architecture help a team working on a large iOS app with many developers?

hard

A. By forcing all developers to write UI and data code together.

B. By dividing the app into layers, each team can focus on one layer without conflicts.

C. By removing the need for documentation and comments.

D. By making the app run only on one device type.

Solution

1. Step 1: Understand team collaboration challenges

   Large teams need clear boundaries to avoid conflicts and confusion.

2. Step 2: See how layering supports teamwork

   Clean architecture divides code into layers, so teams can work independently on UI, business logic, or data.

3. Final Answer:

   By dividing the app into layers, each team can focus on one layer without conflicts. -> Option B

4. Quick Check:

   Layered code = easier team collaboration [OK]

Hint: Layers let teams work separately without stepping on toes [OK]

Common Mistakes:

• Thinking all developers must write all code types
• Assuming documentation is unnecessary
• Believing architecture limits device support