Protocol-oriented architecture in iOS Swift

Introduction

Protocol-oriented architecture helps organize code by defining clear roles and behaviors. It makes your app easier to understand and change.

When you want to share common behavior across different types without using inheritance.

When you want to write flexible and reusable code that can work with many kinds of objects.

When you want to separate what something does from how it does it.

When you want to make your code easier to test by using protocols as contracts.

When you want to design your app with clear responsibilities for each part.

Syntax

iOS Swift

protocol SomeProtocol {
    func doSomething()
}

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

A protocol defines a blueprint of methods or properties.

Types like structs, classes, or enums can conform to protocols by implementing the required methods.

Examples

This example shows a protocol Drivable and a struct Car that follows it.

iOS Swift

protocol Drivable {
    func drive()
}

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

Here a class Bird conforms to the Flyable protocol by implementing fly().

iOS Swift

protocol Flyable {
    func fly()
}

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

This shows a protocol with a property requirement and a struct that provides it.

iOS Swift

protocol Identifiable {
    var id: String { get }
}

struct User: Identifiable {
    var id: String
}

Sample App

This program defines a protocol Greetable with a greet method. The struct Person follows the protocol and prints a greeting with the person's name.

iOS Swift

protocol Greetable {
    func greet()
}

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

let person = Person(name: "Alex")
person.greet()

Important Notes

Protocols help you write code that focuses on what to do, not how to do it.

Using protocols makes your code easier to change and test.

Swift encourages protocol-oriented programming as a modern way to design apps.

Summary

Protocols define a set of rules or behaviors.

Types conform to protocols by implementing required methods or properties.

Protocol-oriented architecture helps build flexible and reusable code.

Practice

1. What is the main purpose of a protocol in Swift's protocol-oriented architecture?

easy

A. To store data persistently in an app

B. To define a blueprint of methods and properties that conforming types must implement

C. To create a concrete class with implemented methods

D. To handle user interface layout automatically

Solution

1. Step 1: Understand what a protocol is

   A protocol defines a set of rules or requirements for methods and properties that any conforming type must implement.

2. Step 2: Differentiate from other concepts

   Protocols do not implement functionality themselves but specify what must be implemented, unlike classes or structs.

3. Final Answer:

   To define a blueprint of methods and properties that conforming types must implement -> Option B

4. Quick Check:

   Protocol = Blueprint for behavior [OK]

Hint: Protocols specify required methods and properties only [OK]

Common Mistakes:

• Confusing protocols with classes or structs
• Thinking protocols store data
• Assuming protocols handle UI layout

2. Which of the following is the correct syntax to declare a protocol named Drivable with a method drive()?

easy

A. func Drivable() { drive() }

B. class Drivable { func drive() }

C. struct Drivable { func drive() }

D. protocol Drivable { func drive() }

Solution

1. Step 1: Recall protocol declaration syntax

   Protocols are declared with the keyword protocol followed by the protocol name and curly braces containing method signatures.

2. Step 2: Identify correct method declaration

   The method drive() is declared without a body inside the protocol.

3. Final Answer:

   protocol Drivable { func drive() } -> Option D

4. Quick Check:

   Protocol syntax = protocol + name + method signatures [OK]

Hint: Protocols use 'protocol' keyword, not class or struct [OK]

Common Mistakes:

• Using class or struct instead of protocol keyword
• Adding method bodies inside protocol
• Incorrect function declaration syntax

3. Given the code below, what will be printed when car.start() is called?

protocol Startable {
  func start()
}

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

let car = Car()
car.start()

medium

A. Car started

B. start() method not implemented

C. Compilation error

D. No output

Solution

1. Step 1: Check protocol conformance

   The struct Car conforms to Startable and implements the required start() method.

2. Step 2: Analyze method call output

   Calling car.start() executes the method which prints "Car started" to the console.

3. Final Answer:

   Car started -> Option A

4. Quick Check:

   Implemented method prints output [OK]

Hint: Implemented protocol methods run normally [OK]

Common Mistakes:

• Assuming missing implementation error
• Thinking protocol methods print automatically
• Confusing compilation errors with runtime

4. Identify the error in the following code snippet:

protocol Runnable {
  func run()
}

struct Athlete: Runnable {
  func run(distance: Int) {
    print("Running \(distance) meters")
  }
}

medium

A. Structs cannot conform to protocols

B. Protocol Runnable cannot have methods

C. Method signature in Athlete does not match protocol requirement

D. Missing return type in run() method

Solution

1. Step 1: Compare protocol and struct method signatures

   The protocol requires func run() with no parameters, but Athlete implements func run(distance: Int) which has a parameter.

2. Step 2: Understand conformance rules

   Method signatures must match exactly for conformance; differing parameters cause a mismatch error.

3. Final Answer:

   Method signature in Athlete does not match protocol requirement -> Option C

4. Quick Check:

   Method signatures must match exactly [OK]

Hint: Method signatures must match protocol exactly [OK]

Common Mistakes:

• Adding parameters to protocol methods in implementation
• Thinking structs can't conform to protocols
• Ignoring method signature differences

5. You want to create a flexible system where different types can be "playable" with a play() method, and some can also be "recordable" with a record() method. Which protocol-oriented approach below best supports this design?

hard

A. Define separate protocols Playable and Recordable, then have types conform to one or both as needed

B. Create a single protocol with both play() and record() methods, and require all types to implement both

C. Use a base class with play() and record() methods and inherit from it

D. Implement play() and record() as global functions

Solution

1. Step 1: Understand protocol composition

   Defining separate protocols allows types to conform only to behaviors they support, making the design flexible and reusable.

2. Step 2: Evaluate other options

   Single protocol forces all types to implement all methods, base class limits flexibility, and global functions do not enforce behavior contracts.

3. Final Answer:

   Define separate protocols Playable and Recordable, then have types conform to one or both as needed -> Option A

4. Quick Check:

   Separate protocols = flexible conformance [OK]

Hint: Use multiple protocols for flexible behavior [OK]

Common Mistakes:

• Forcing all types to implement all methods
• Using inheritance instead of protocols
• Not leveraging protocol composition