Why protocol-oriented design matters in Swift - The Real Reasons

The Big Idea

Discover how a simple design shift can save you hours of frustrating code fixes!

The Scenario

Imagine building a large app where many parts share similar features but are slightly different. You try to write separate code for each part, copying and changing bits everywhere.

The Problem

This manual way means lots of repeated code, making it hard to fix bugs or add new features. One small change requires updating many places, which is slow and error-prone.

The Solution

Protocol-oriented design lets you define shared behaviors once and then apply them to many types. This way, you write less code, keep it clean, and easily add new features without breaking existing parts.

Before vs After

✗ Before

class Dog { func speak() { print("Woof") } }
class Cat { func speak() { print("Meow") } }

✓ After

protocol Animal { func speak() }
extension Animal { func speak() { print("Some sound") } }
struct Dog: Animal { func speak() { print("Woof") } }
struct Cat: Animal { func speak() { print("Meow") } }

What It Enables

It enables building flexible, reusable code that adapts easily as your app grows.

Real Life Example

Think of a game with many characters: protocol-oriented design lets you define common actions like move or attack once, then customize each character's behavior without repeating code.

Key Takeaways

Manual copying leads to messy, hard-to-maintain code.

Protocols define shared behavior clearly and simply.

Designing with protocols makes your code flexible and reusable.