Why Protocols in iOS Swift? - Purpose & Use Cases

The Big Idea

What if you could make different parts of your app talk the same language without rewriting code over and over?

The Scenario

Imagine you are building an app with many different types of objects, like buttons, sliders, and switches. Each object needs to respond to user taps, but you have to write separate code for each one to handle taps.

The Problem

Writing separate tap-handling code for every object is slow and error-prone. If you want to add a new object type, you must remember to add tap code again. This leads to repeated code and bugs when you forget or do it inconsistently.

The Solution

Protocols let you define a common set of behaviors that many different objects can share. You write the tap-handling code once in the protocol, and any object that adopts the protocol promises to implement that behavior. This keeps your code clean and consistent.

Before vs After

✗ Before

class Button {
  func tap() { /* handle tap */ }
}
class Slider {
  func tap() { /* handle tap differently */ }
}

✓ After

protocol Tappable {
  func tap()
}
class Button: Tappable {
  func tap() { /* handle tap */ }
}
class Slider: Tappable {
  func tap() { /* handle tap differently */ }
}

What It Enables

Protocols enable you to write flexible, reusable code that works with many object types through a shared interface.

Real Life Example

In iOS apps, protocols let you create delegate patterns where one object tells another what happened, like a table view telling its delegate when a row is selected.

Key Takeaways

Protocols define shared behaviors for different objects.

They reduce repeated code and bugs.

They make your app easier to extend and maintain.

Practice

1. What is the main purpose of a protocol in Swift?

easy

A. To create a new class with default behavior

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

C. To store data persistently on the device

D. To handle user interface layout automatically

Solution

1. Step 1: Understand what a protocol defines

   A protocol specifies methods and properties that a type must implement, acting as a blueprint.

2. Step 2: Differentiate from other concepts

   Protocols do not create classes or store data; they only define requirements.

3. Final Answer:

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

4. Quick Check:

   Protocol purpose = blueprint [OK]

Hint: Protocols define required methods and properties [OK]

Common Mistakes:

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

2. Which of the following is the correct syntax to declare a protocol named Drivable in Swift?

easy

A. struct Drivable { func drive() }

B. class Drivable { func drive() }

C. func protocol Drivable() { drive() }

D. protocol Drivable { func drive() }

Solution

1. Step 1: Identify correct protocol declaration syntax

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

2. Step 2: Check method declaration inside protocol

   Methods inside protocols are declared without implementation, just the signature.

3. Final Answer:

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

4. Quick Check:

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

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

Common Mistakes:

• Using class or struct instead of protocol
• Adding method implementation inside protocol
• Incorrect keyword order

3. Consider this Swift code:

protocol Greetable {
  func greet() -> String
}

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

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

What will be printed when this code runs?

medium

A. Hello!

B. greet()

C. Error: Missing protocol implementation

D. nil

Solution

1. Step 1: Check protocol and struct conformance

   The struct Person adopts Greetable and implements the required greet() method returning "Hello!".

2. Step 2: Understand the print statement 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 [OK]

Common Mistakes:

• Expecting protocol name printed
• Thinking missing implementation error occurs
• Assuming nil is printed

4. What is wrong with this Swift code?

protocol Runnable {
  func run()
}

struct Athlete: Runnable {
  // Missing run() implementation
}

medium

A. No error, code is valid

B. Error: run() must have a return type

C. Error: Athlete does not implement required method run()

D. Error: Protocol Runnable cannot be adopted by struct

Solution

1. Step 1: Check protocol requirements

   The protocol Runnable requires a method run() with no return value.

2. Step 2: Verify struct conformance

   The struct Athlete adopts Runnable but does not implement run(), causing a compile error.

3. Final Answer:

   Error: Athlete does not implement required method run() -> Option C

4. Quick Check:

   Missing required method causes error [OK]

Hint: All protocol methods must be implemented [OK]

Common Mistakes:

• Assuming structs can't adopt protocols
• Thinking missing method is allowed
• Expecting run() to require return type

5. You want to create a protocol Vehicle with a property speed that can be read and set. Which of these protocol declarations is correct?

hard

A. protocol Vehicle { var speed: Int { get set } }

B. protocol Vehicle { var speed: Int }

C. protocol Vehicle { func speed() -> Int }

D. protocol Vehicle { let speed: Int }

Solution

1. Step 1: Understand property requirements in protocols

   To require a property to be readable and writable, use { get set } in the protocol.

2. Step 2: Analyze each option

   protocol Vehicle { var speed: Int { get set } } correctly declares speed as a variable property with get set. protocol Vehicle { var speed: Int } misses get set, so it's read-only. protocol Vehicle { func speed() -> Int } declares a method, not a property. protocol Vehicle { let speed: Int } uses let, which is not allowed in protocols.

3. Final Answer:

   protocol Vehicle { var speed: Int { get set } } -> Option A

4. Quick Check:

   Writable property = var with get set [OK]

Hint: Use 'var' with { get set } for read-write properties [OK]

Common Mistakes:

• Using 'let' in protocol properties
• Omitting { get set } for writable properties
• Confusing methods with properties