Bird
Raised Fist0
iOS Swiftmobile~20 mins

Repository pattern in iOS Swift - Mini App: Build & Ship

Choose your learning style10 modes available
Build: User List
This screen shows a list of users fetched from a repository. The repository abstracts data fetching, so the UI does not know where data comes from.
Target UI
---------------------
|     User List      |
---------------------
| * Alice            |
| * Bob              |
| * Charlie          |
|                    |
| [Refresh]          |
---------------------
Create a UserRepository protocol with a method to fetch users asynchronously.
Implement a MockUserRepository that returns a fixed list of users after a short delay.
Build a SwiftUI view that uses the repository to load and display users in a list.
Add a Refresh button to reload the user list from the repository.
Show a loading indicator while fetching data.
Starter Code
iOS Swift
import SwiftUI

// TODO: Define User model here

// TODO: Define UserRepository protocol here

// TODO: Implement MockUserRepository here

struct UserListView: View {
    // TODO: Add @State properties for users and loading state
    
    // TODO: Add repository property
    
    var body: some View {
        NavigationView {
            VStack {
                // TODO: Show loading indicator or user list
                
                Button("Refresh") {
                    // TODO: Load users from repository
                }
                .padding()
            }
            .navigationTitle("User List")
        }
        .onAppear {
            // TODO: Load users when view appears
        }
    }
}

struct UserListView_Previews: PreviewProvider {
    static var previews: some View {
        UserListView()
    }
}
Task 1
Task 2
Task 3
Task 4
Task 5
Task 6
Task 7
Task 8
Solution
iOS Swift
import SwiftUI

struct User: Identifiable {
    let id: Int
    let name: String
}

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

class MockUserRepository: UserRepository {
    func fetchUsers() async -> [User] {
        try? await Task.sleep(nanoseconds: 1_000_000_000) // 1 second delay
        return [
            User(id: 1, name: "Alice"),
            User(id: 2, name: "Bob"),
            User(id: 3, name: "Charlie")
        ]
    }
}

struct UserListView: View {
    @State private var users: [User] = []
    @State private var isLoading = false
    private let repository: UserRepository = MockUserRepository()

    var body: some View {
        NavigationView {
            VStack {
                if isLoading {
                    ProgressView("Loading...")
                        .padding()
                } else {
                    List(users) { user in
                        Text(user.name)
                    }
                }
                Button("Refresh") {
                    Task {
                        await loadUsers()
                    }
                }
                .padding()
            }
            .navigationTitle("User List")
        }
        .task {
            await loadUsers()
        }
    }

    private func loadUsers() async {
        isLoading = true
        users = await repository.fetchUsers()
        isLoading = false
    }
}

struct UserListView_Previews: PreviewProvider {
    static var previews: some View {
        UserListView()
    }
}

We start by defining a simple User struct with an id and name. This lets SwiftUI identify each user uniquely in the list.

The UserRepository protocol declares a method fetchUsers() that returns users asynchronously. This hides the data source details from the UI.

MockUserRepository implements this protocol and simulates a network delay using Task.sleep. It returns a fixed list of users.

In UserListView, we use @State properties to hold the users and loading state. The repository is a constant instance of MockUserRepository.

The UI shows a ProgressView while loading, and a List of user names when done. The Refresh button triggers reloading.

We use Swift concurrency with async and await to fetch users without blocking the UI. The .task modifier loads users when the view appears.

This pattern cleanly separates data fetching logic from UI code, making it easier to maintain and test.

Final Result
Completed Screen
---------------------
|     User List      |
---------------------
| * Alice            |
| * Bob              |
| * Charlie          |
|                    |
| [Refresh]          |
---------------------
When the screen appears, a loading spinner shows briefly, then the user list appears.
Tapping the Refresh button shows the spinner again and reloads the user list.
The list displays user names in a scrollable list.
Stretch Goal
Add error handling to the repository and show an alert if fetching users fails.
💡 Hint
Modify fetchUsers() to throw errors. Use try? or do-catch in loadUsers(). Show an Alert with .alert modifier in the view.

Practice

(1/5)
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
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard