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.