Why protocol-oriented design matters in Swift

Introduction

Protocol-oriented design helps you write clear and flexible code. It makes your programs easier to change and reuse.

When you want different parts of your app to share common behavior without repeating code.

When you need to swap or change parts of your program easily without breaking everything.

When you want to write tests for your code by using simple, replaceable pieces.

When you want to organize your code by what it does, not just by what it is.

When you want to avoid complex inheritance and keep your code simple and clear.

Syntax

Swift

protocol SomeProtocol {
    func doSomething()
}

struct SomeStruct: SomeProtocol {
    func doSomething() {
        print("Doing something")
    }
}

A protocol defines a set of methods or properties that a type must have.

Types like struct, class, or enum can adopt protocols to promise they implement those methods.

Examples

This example shows a protocol Drivable and a struct Car that follows it by implementing drive().

Swift

protocol Drivable {
    func drive()
}

struct Car: Drivable {
    func drive() {
        print("Car is driving")
    }
}

Here, Flyable is a protocol for flying behavior, and Bird adopts it.

Swift

protocol Flyable {
    func fly()
}

struct Bird: Flyable {
    func fly() {
        print("Bird is flying")
    }
}

This shows a protocol with a property requirement. User must have an id string.

Swift

protocol Identifiable {
    var id: String { get }
}

struct User: Identifiable {
    var id: String
}

Sample Program

This program shows how two different types, Person and Robot, can both greet because they follow the Greetable protocol. The function sayHello works with any Greetable type.

Swift

protocol Greetable {
    func greet()
}

struct Person: Greetable {
    var name: String
    func greet() {
        print("Hello, my name is \(name)!")
    }
}

struct Robot: Greetable {
    func greet() {
        print("Beep boop. I am a robot.")
    }
}

func sayHello(to greeter: Greetable) {
    greeter.greet()
}

let alice = Person(name: "Alice")
let bot = Robot()

sayHello(to: alice)
sayHello(to: bot)

Important Notes

Protocols let you write code that works with many types, as long as they follow the same rules.

Using protocols helps avoid repeating code and makes your app easier to update later.

Protocol-oriented design is a key idea in Swift to build flexible and clean programs.

Summary

Protocols define shared behavior that many types can use.

Protocol-oriented design helps make code reusable and easy to change.

It encourages thinking about what things do, not just what they are.

Practice

1. What is the main benefit of using protocols in Swift's protocol-oriented design?

easy

A. They make the code run faster.

B. They store data like variables.

C. They replace classes completely.

D. They allow different types to share common behavior.

Solution

1. Step 1: Understand what protocols do

   Protocols define a set of behaviors that many types can adopt and share.

2. Step 2: Identify the main benefit

   This sharing of behavior helps make code reusable and flexible.

3. Final Answer:

   They allow different types to share common behavior. -> Option D

4. Quick Check:

   Protocols = shared behavior [OK]

Hint: Protocols share behavior across types, not data storage [OK]

Common Mistakes:

• Thinking protocols speed up code execution
• Confusing protocols with classes
• Believing protocols store data

2. Which of the following is the correct way to declare a protocol in Swift?

easy

A. struct Vehicle: protocol { func drive() }

B. class Vehicle { func drive() }

C. protocol Vehicle { func drive() }

D. func protocol Vehicle() { drive() }

Solution

1. Step 1: Recall Swift protocol syntax

   Protocols are declared using the keyword 'protocol' followed by the name and curly braces.

2. Step 2: Match the correct syntax

   protocol Vehicle { func drive() } correctly uses 'protocol Vehicle { func drive() }'. Other options misuse keywords or structure.

3. Final Answer:

   protocol Vehicle { func drive() } -> Option C

4. Quick Check:

   Protocol declaration = protocol keyword + name + braces [OK]

Hint: Protocols start with 'protocol' keyword, not 'class' or 'func' [OK]

Common Mistakes:

• Using 'class' instead of 'protocol'
• Trying to inherit protocol with ':' in struct incorrectly
• Writing 'func protocol' which is invalid

3. Consider this Swift code:

protocol Greetable { func greet() -> String }

struct Person: Greetable {
  func greet() -> String { "Hello!" }
}

let p = Person()
print(p.greet())

What will be the output?

medium

A. Hello!

B. greet()

C. Error: Missing function implementation

D. nil

Solution

1. Step 1: Check protocol conformance

   Person struct implements the greet() method required by Greetable.

2. Step 2: Understand the print output

   Calling p.greet() returns "Hello!", which is printed.

3. Final Answer:

   Hello! -> Option A

4. Quick Check:

   Implemented method returns "Hello!" [OK]

Hint: Implemented protocol methods run normally when called [OK]

Common Mistakes:

• Assuming protocol methods print their name
• Expecting runtime error without implementation
• Thinking print outputs nil if no return

4. What is wrong with this Swift code?

protocol Drawable {
  func draw()
}

struct Circle: Drawable {
  // Missing draw() implementation
}

let c = Circle()

medium

A. Circle must implement draw() or code won't compile.

B. Circle can omit draw() because it's a struct.

C. Protocol Drawable should not have functions.

D. Circle should be a class, not a struct.

Solution

1. Step 1: Check protocol requirements

   Drawable requires any conforming type to implement draw().

2. Step 2: Verify Circle implementation

   Circle does not implement draw(), so it violates the protocol.

3. Final Answer:

   Circle must implement draw() or code won't compile. -> Option A

4. Quick Check:

   Protocol methods must be implemented [OK]

Hint: All protocol methods must be implemented to compile [OK]

Common Mistakes:

• Thinking structs can skip protocol methods
• Believing protocols can't have functions
• Confusing struct vs class requirements

5. You want to design a system where multiple types like Car and Bicycle can be "startable" with a start() method. Using protocol-oriented design, which approach is best?

hard

A. Write separate start() functions outside the types for each vehicle.

B. Create a protocol Startable with start() and have both types conform to it.

C. Make Car and Bicycle subclasses of a common class with start() method.

D. Use global variables to track if Car or Bicycle started.

Solution

1. Step 1: Identify shared behavior

   Both Car and Bicycle need a start() method, which is shared behavior.

2. Step 2: Apply protocol-oriented design

   Defining a Startable protocol with start() and making both types conform promotes reuse and flexibility.

3. Step 3: Compare other options

   Subclassing limits flexibility; separate functions or globals reduce clarity and reuse.

4. Final Answer:

   Create a protocol Startable with start() and have both types conform to it. -> Option B

5. Quick Check:

   Protocol for shared behavior = best design [OK]

Hint: Use protocols to share behavior across unrelated types [OK]

Common Mistakes:

• Using class inheritance when unrelated types
• Writing separate functions instead of protocol
• Using global state instead of behavior abstraction