Why Repository pattern in iOS Swift? - Purpose & Use Cases

The Big Idea

What if you could change your app's data source without rewriting your whole code?

The Scenario

Imagine you are building an app that fetches user data from different places like a local database, a web server, or a cache. Without a clear plan, you write code everywhere to get and save data directly. It feels like juggling many balls at once, and it's easy to drop one.

The Problem

When you manually fetch or save data everywhere, your code becomes messy and hard to fix. If the data source changes, you must hunt down every place in your app to update it. This wastes time and causes bugs that are hard to find.

The Solution

The Repository pattern acts like a smart helper that hides all the data fetching details. Your app talks only to this helper, and it decides where to get or save data. This keeps your code clean, easy to change, and less buggy.

Before vs After

✗ Before

let user = database.getUser(id: 1)
// elsewhere
let user = api.fetchUser(id: 1)

✓ After

let user = userRepository.getUser(id: 1)
// userRepository handles source internally

What It Enables

It lets you change where data comes from without touching the rest of your app, making your code flexible and easier to maintain.

Real Life Example

Think of a music app that plays songs from your phone or streams online. The Repository pattern lets the app switch between local songs and online streams smoothly without changing the player code.

Key Takeaways

Manual data handling scatters code and causes bugs.

Repository pattern centralizes data access in one place.

This makes your app easier to update and maintain.

Practice

1.

What is the main purpose of the Repository pattern in iOS Swift development?

easy

A. To separate data access logic from the rest of the app

B. To handle UI animations smoothly

C. To manage app navigation between screens

D. To store user interface layout information

Solution

1. Step 1: Understand the role of Repository pattern

   The Repository pattern is designed to isolate data access logic from business logic in an app.

2. Step 2: Identify the correct purpose

   Separating data access makes the app easier to maintain and test, which matches To separate data access logic from the rest of the app.

3. Final Answer:

   To separate data access logic from the rest of the app -> Option A

4. Quick Check:

   Repository pattern = separate data access [OK]

Hint: Repository = data access separation [OK]

Common Mistakes:

• Confusing Repository with UI or navigation roles
• Thinking Repository manages animations
• Assuming Repository stores UI layout

2.

Which of the following is the correct way to declare a repository protocol in Swift?

?

easy

A. struct UserRepository { func fetchUsers() -> [User] }

B. class UserRepository { func fetchUsers() -> [User] }

C. enum UserRepository { func fetchUsers() -> [User] }

D. protocol UserRepository { func fetchUsers() -> [User] }

Solution

1. Step 1: Identify correct Swift syntax for protocols

   Protocols in Swift are declared with the keyword protocol followed by method signatures without bodies.

2. Step 2: Match the correct declaration

   protocol UserRepository { func fetchUsers() -> [User] } correctly declares a protocol with a method signature. Other options use class, struct, or enum which are not protocols.

3. Final Answer:

   protocol UserRepository { func fetchUsers() -> [User] } -> Option D

4. Quick Check:

   Protocol declaration uses protocol keyword [OK]

Hint: Protocols start with 'protocol' keyword [OK]

Common Mistakes:

• Using class or struct instead of protocol for interface
• Adding method bodies inside protocol
• Using enum incorrectly for repository

3.

Given the following code snippet, what will be printed?

protocol UserRepository {
  func fetchUsers() -> [String]
}

class MockUserRepository: UserRepository {
  func fetchUsers() -> [String] {
    return ["Alice", "Bob"]
  }
}

let repo: UserRepository = MockUserRepository()
print(repo.fetchUsers())

medium

A. []

B. ["Alice", "Bob"]

C. nil

D. Compilation error

Solution

1. Step 1: Understand protocol conformance and method implementation

   The class MockUserRepository conforms to UserRepository and implements fetchUsers() returning ["Alice", "Bob"].

2. Step 2: Analyze the print statement

   The variable repo is typed as UserRepository but holds an instance of MockUserRepository. Calling fetchUsers() returns ["Alice", "Bob"], which is printed.

3. Final Answer:

   ["Alice", "Bob"] -> Option B

4. Quick Check:

   Protocol method returns mock data [OK]

Hint: Protocol variable calls concrete implementation [OK]

Common Mistakes:

• Expecting empty array instead of returned data
• Thinking protocol variable can't call methods
• Assuming compilation error due to protocol

4.

Identify the error in this repository implementation:

protocol UserRepository {
  func fetchUsers() -> [String]
}

class UserRepo: UserRepository {
  func fetchUsers() {
    return ["Alice", "Bob"]
  }
}

medium

A. Protocol method has wrong name

B. Method does not return a value

C. Missing return type in method signature

D. Class does not conform to protocol

Solution

1. Step 1: Compare protocol and class method signatures

   The protocol method fetchUsers() returns [String]. The class method lacks the return type in its signature.

2. Step 2: Identify the mismatch causing error

   Because the class method signature does not match the protocol, it causes a compilation error. The method must declare the return type.

3. Final Answer:

   Missing return type in method signature -> Option C

4. Quick Check:

   Method signatures must match protocol [OK]

Hint: Method signature must match protocol exactly [OK]

Common Mistakes:

• Forgetting to add return type in implementation
• Assuming method name mismatch
• Thinking protocol conformance is automatic

5.

You want to switch your data source from a local database to a remote API without changing your app's business logic. How does the Repository pattern help you achieve this?

hard

A. By defining a repository interface and implementing separate classes for each data source

B. By embedding API calls directly in the UI code

C. By storing all data in global variables accessible everywhere

D. By using a single class that mixes local and remote data fetching

Solution

1. Step 1: Understand the role of repository interface

   The Repository pattern uses an interface (protocol) to abstract data access methods.

2. Step 2: Implement separate classes for each data source

   You create one class for local database access and another for remote API, both conforming to the same interface. This allows switching without changing business logic.

3. Final Answer:

   By defining a repository interface and implementing separate classes for each data source -> Option A

4. Quick Check:

   Interface + multiple implementations = easy data source switch [OK]

Hint: Use interface + multiple classes for data sources [OK]

Common Mistakes:

• Mixing data fetching code in UI layer
• Using global variables for data access
• Combining local and remote logic in one class