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

The Big Idea

Discover how a simple idea can save you hours of repetitive coding and bugs!

The Scenario

Imagine you are building an app with many types of objects, like cars, bikes, and boats. Each has some common features, but also unique ones. You try to write separate code for each type to handle shared behavior.

The Problem

Writing separate code for each type means repeating yourself a lot. If you want to change how a shared feature works, you must update every type manually. This is slow, confusing, and easy to make mistakes.

The Solution

Protocol-oriented programming lets you define shared features once as a protocol. Then, each type can adopt the protocol and get the shared behavior automatically. This keeps your code clean, easy to update, and flexible.

Before vs After

✗ Before

class Car { func start() { print("Starting engine") } }
class Bike { func start() { print("Starting engine") } }

✓ After

protocol Vehicle { func start() }
extension Vehicle { func start() { print("Starting engine") } }
struct Car: Vehicle {}
struct Bike: Vehicle {}

What It Enables

It enables you to write less code, avoid mistakes, and easily add new types that share behavior without rewriting everything.

Real Life Example

Think of a music app where different instruments can play sounds. Using protocols, you define a common way to play sound once, then each instrument just adopts it, making your app easier to build and expand.

Key Takeaways

Manual code repeats shared behavior, causing errors and slow updates.

Protocols define shared features once for many types.

This approach makes code cleaner, safer, and easier to grow.