Why Protocol requirements (methods and properties) in Swift? - Purpose & Use Cases

The Big Idea

What if you could guarantee every part of your code plays by the same rules without rewriting everything?

The Scenario

Imagine you are building a game with many characters. Each character needs to move and attack, but you write separate code for each one without any shared rules.

Later, you want to add a new character, but you have to remember and rewrite all the movement and attack code again.

The Problem

Writing separate code for each character is slow and confusing. You might forget to add important actions or make mistakes because there is no clear agreement on what each character should do.

This leads to bugs and wasted time fixing repeated code.

The Solution

Protocols let you define a clear list of methods and properties that every character must have. This way, you create a simple contract that all characters follow.

Swift checks that each character implements these required methods and properties, so you never miss anything important.

Before vs After

✗ Before

class Warrior {
  func move() { /* code */ }
  func attack() { /* code */ }
}

class Mage {
  func move() { /* code */ }
  func attack() { /* code */ }
}

✓ After

protocol Character {
  func move()
  func attack()
}

class Warrior: Character {
  func move() { /* code */ }
  func attack() { /* code */ }
}

class Mage: Character {
  func move() { /* code */ }
  func attack() { /* code */ }
}

What It Enables

Protocols make your code organized and safe by ensuring all types follow the same rules, making it easier to add new features and fix bugs.

Real Life Example

Think of a remote control that works with many devices. The remote expects every device to respond to certain buttons like power and volume. Protocols are like that remote's instructions, making sure every device knows how to respond.

Key Takeaways

Protocols define required methods and properties as a contract.

They prevent mistakes by enforcing consistent implementation.

Protocols make adding new types easier and safer.

Practice

1. What does a protocol in Swift require from a type that adopts it?

easy

A. To declare new methods unrelated to the protocol

B. To inherit from a superclass

C. To override all existing methods

D. To implement all the methods and properties declared in the protocol

Solution

1. Step 1: Understand protocol purpose

   Protocols define a set of methods and properties that a type must implement.

2. Step 2: Check adoption requirements

   Any type adopting a protocol must provide implementations for all its requirements.

3. Final Answer:

   To implement all the methods and properties declared in the protocol -> Option D

4. Quick Check:

   Protocol adoption = implement all requirements [OK]

Hint: Protocols require full implementation of declared methods and properties [OK]

Common Mistakes:

• Thinking protocols require inheritance from a class
• Assuming methods can be skipped
• Confusing protocol adoption with subclassing

2. Which of the following is the correct way to declare a read-only property requirement in a Swift protocol?

easy

A. var name: String { get }

B. var name: String { get set }

C. let name: String

D. func name() -> String

Solution

1. Step 1: Recall property syntax in protocols

   Read-only properties use { get } to indicate they must be readable but not necessarily writable.

2. Step 2: Analyze options

   var name: String { get } uses { get } correctly; var name: String { get set } requires read-write; let name: String is invalid in protocols; func name() -> String is a method, not a property.

3. Final Answer:

   var name: String { get } -> Option A

4. Quick Check:

   Read-only property = { get } [OK]

Hint: Use { get } for read-only property in protocols [OK]

Common Mistakes:

• Using let instead of var in protocol
• Confusing methods with properties
• Using { get set } for read-only properties

3. Consider the following Swift code:

protocol Vehicle {
    var speed: Double { get set }
    func description() -> String
}

struct Car: Vehicle {
    var speed: Double
    func description() -> String {
        return "Car speed is \(speed) km/h"
    }
}

let myCar = Car(speed: 80)
print(myCar.description())

What is the output when this code runs?

medium

A. Error: Protocol requirements not met

B. Car speed is 80.0 km/h

C. Car speed is 80 km/h

D. Car speed is km/h

Solution

1. Step 1: Check protocol conformance

   Car struct implements the required property speed and method description(), fulfilling Vehicle protocol.

2. Step 2: Analyze print output

   The description() returns "Car speed is \(speed) km/h". Since speed is 80.0 (Double), string interpolation formats it as "80.0".

3. Final Answer:

   Car speed is 80.0 km/h -> Option B

4. Quick Check:

   Protocol methods implemented = correct output [OK]

Hint: String interpolation for Double 80.0 prints '80.0' [OK]

Common Mistakes:

• Expecting 80 instead of 80.0
• Thinking protocol conformance causes error
• Missing string interpolation syntax

4. Given this protocol and struct:

protocol Shape {
    var area: Double { get }
    func perimeter() -> Double
}

struct Square: Shape {
    var side: Double
    var area: Double {
        side * side
    }
}

What is the error in the code?

medium

A. area property should be var with get set

B. side property must be a constant (let)

C. Missing implementation of perimeter() method

D. Square cannot have computed properties

Solution

1. Step 1: Check protocol requirements

   Shape protocol requires a read-only property area and a method perimeter().

2. Step 2: Verify Square struct implementation

   Square implements area as computed property but does not implement perimeter() method.

3. Final Answer:

   Missing implementation of perimeter() method -> Option C

4. Quick Check:

   All protocol methods must be implemented [OK]

Hint: All protocol methods must be implemented, or error occurs [OK]

Common Mistakes:

• Assuming computed properties are not allowed
• Thinking get set is required for read-only
• Ignoring missing method implementations

5. You want to create a protocol Identifiable that requires a read-only id property of type String and a method identify() that prints the id. Which of the following is the correct protocol and extension to provide a default implementation of identify()?

hard

A. protocol Identifiable {
var id: String { get }
func identify()
}
extension Identifiable {
func identify() {
print("ID: \(id)")
}
}

B. protocol Identifiable {
var id: String { get set }
func identify()
}
extension Identifiable {
func identify() {
print(id)
}
}

C. protocol Identifiable {
let id: String
func identify()
}
extension Identifiable {
func identify() {
print("ID is " + id)
}
}

D. protocol Identifiable {
var id: String { get }
func identify() -> String
}
extension Identifiable {
func identify() -> String {
return id
}
}

Solution

1. Step 1: Define protocol requirements

   id must be read-only, so use { get } and identify() method with no return.

2. Step 2: Provide default implementation in extension

   Extension implements identify() printing "ID: \(id)" matching protocol signature.

3. Final Answer:

   protocol Identifiable { var id: String { get }; func identify() } extension Identifiable { func identify() { print("ID: \(id)") } } -> Option A

4. Quick Check:

   Read-only property + default method in extension [OK]

Hint: Use protocol extension for default method implementations [OK]

Common Mistakes:

• Using let in protocol property
• Changing method signature in extension
• Making id writable when only read-only needed