Why Dependency injection in iOS Swift? - Purpose & Use Cases

The Big Idea

Discover how handing over your tools can make your code smarter and easier to manage!

The Scenario

Imagine building an app where every part creates its own tools and helpers inside. For example, a screen creates its own network manager and database handler directly.

The Problem

This manual way makes your code tightly connected and hard to change. If you want to swap the network manager or test the screen, you must dig deep and rewrite many parts. It's like having a tangled ball of yarn that's tough to separate.

The Solution

Dependency injection hands the needed tools to each part from outside. Instead of creating them inside, parts receive what they need. This keeps code clean, easy to swap, and simple to test.

Before vs After

✗ Before

class Screen {
  let network = NetworkManager()
  // uses network directly
}

✓ After

class Screen {
  let network: NetworkManager
  init(network: NetworkManager) {
    self.network = network
  }
  // uses injected network
}

What It Enables

It enables flexible, testable, and maintainable code by separating creation from usage.

Real Life Example

Think of a coffee shop where the barista gets coffee beans delivered instead of growing them. The barista focuses on making coffee, while the beans can come from any supplier.

Key Takeaways

Manual creation leads to tightly coupled code.

Dependency injection separates creation from use.

This makes code easier to change and test.