Why protocol-oriented design matters in Swift - Visual Breakdown

Concept Flow - Why protocol-oriented design matters

Define Protocol

↓

Create Types conforming to Protocol

↓

Use Protocol as Interface

↓

Write Generic Code using Protocol

↓

Easily Extend with New Types

↓

Achieve Flexible, Reusable Code

Protocol-oriented design starts by defining protocols, then types conform to them, enabling flexible and reusable code through generic programming.

Execution Sample

Swift

protocol Greetable {
    func greet() -> String
}

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

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

Defines a protocol and a struct that conforms to it, then calls the protocol method.

Execution Table

Step	Action	Evaluation	Result
1	Define protocol Greetable with greet()	Protocol created	Greetable protocol ready
2	Define struct Person conforming to Greetable	Person implements greet()	Person type ready
3	Create instance p of Person	p is Person	Instance p created
4	Call p.greet()	Calls Person.greet()	"Hello!" returned
5	Print result	Output to console	Hello!

💡 Program ends after printing greeting

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
p	undefined	Person instance	Person instance	Person instance
greet() output	undefined	undefined	"Hello!"	"Hello!"

Key Moments - 3 Insights

Why do we use a protocol instead of just a class or struct?

Protocols let us define a common interface that many types can share, as shown in execution_table step 1 and 2, enabling flexible and reusable code.

How does calling greet() on p know which code to run?

Because p is a Person instance that conforms to Greetable, calling greet() runs Person's implementation (step 4 in execution_table).

What if we add another type conforming to Greetable?

We can add new types easily without changing existing code, making the design flexible (concept_flow last steps).

Visual Quiz - 3 Questions

Look at the execution_table, what is the output of p.greet() at step 4?

A "Hi!"

B "Hello!"

C Error

D No output

💡 Hint

Check execution_table row 4 under Result column

At which step is the Person instance created?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at execution_table row 3 Action column

If we add a new struct conforming to Greetable, what changes in the execution_table?

A Step 4 output changes

B Step 1 protocol changes

C New steps showing the new struct definition and usage

D No changes at all

💡 Hint

Refer to key_moments about adding new types and concept_flow steps

Concept Snapshot

protocol ProtocolName {
    func method() -> ReturnType
}

struct TypeName: ProtocolName {
    func method() -> ReturnType { ... }
}

- Protocols define shared interfaces.
- Types conform to protocols to implement behavior.
- Enables flexible, reusable, and testable code.

Full Transcript

Protocol-oriented design in Swift means defining protocols as blueprints for behavior. Types like structs or classes then conform to these protocols by implementing required methods. This approach allows writing generic code that works with any type conforming to the protocol, making code flexible and reusable. In the example, a protocol Greetable defines a greet method. The struct Person conforms by implementing greet. Creating a Person instance and calling greet prints Hello!. This design lets you add new types conforming to Greetable without changing existing code, promoting easy extension and maintenance.

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