Why Protocol extensions for shared behavior in Swift? - Purpose & Use Cases

The Big Idea

What if you could write a behavior once and have it magically work for many types without extra effort?

The Scenario

Imagine you have many different types of objects in your app, like cars, bikes, and boats. Each one needs to do similar things, like start or stop, but you write the same code again and again for each type.

The Problem

Writing the same code repeatedly is slow and boring. It's easy to make mistakes or forget to update all places when you want to change how starting or stopping works. This makes your app harder to fix and grow.

The Solution

Protocol extensions let you write shared behavior once and automatically give it to all types that follow the protocol. This means less code, fewer mistakes, and easier updates--all while keeping your code organized and clear.

Before vs After

✗ Before

protocol Vehicle {
    func start()
}

struct Car: Vehicle {
    func start() {
        print("Car started")
    }
}

struct Bike: Vehicle {
    func start() {
        print("Bike started")
    }
}

✓ After

protocol Vehicle {
    func start()
}

extension Vehicle {
    func start() {
        print("Vehicle started")
    }
}

struct Car: Vehicle {}
struct Bike: Vehicle {}

What It Enables

You can create flexible, reusable code that works across many types without repeating yourself, making your apps easier to build and maintain.

Real Life Example

Think of a game where many characters can jump. Instead of writing jump code for each character, you write it once in a protocol extension and all characters get the jump ability automatically.

Key Takeaways

Writing shared behavior once saves time and reduces errors.

Protocol extensions give default implementations to many types easily.

This keeps your code clean, organized, and easier to update.