Why Async functions in iOS Swift? - Purpose & Use Cases

The Big Idea

Discover how async functions keep your app smooth and users happy by avoiding freezes!

The Scenario

Imagine you want your app to load a photo from the internet. If your app waits and does nothing else until the photo arrives, it feels frozen and slow.

The Problem

Doing tasks one by one means your app can freeze or become unresponsive. Users get frustrated because they can't tap buttons or scroll while waiting.

The Solution

Async functions let your app start a task and keep working on other things while waiting. When the task finishes, the app gets the result without freezing.

Before vs After

✗ Before

let data = try Data(contentsOf: url)
// UI waits here until data loads

✓ After

let (data, _) = try await URLSession.shared.data(from: url)
// UI stays smooth while loading

What It Enables

Async functions make your app fast and smooth by handling slow tasks in the background without blocking the user.

Real Life Example

When you open a chat app, messages load in the background while you can still scroll and type new messages without delay.

Key Takeaways

Manual waiting blocks the app and frustrates users.

Async functions let tasks run in the background smoothly.

This keeps your app responsive and enjoyable to use.

Practice

1. What does marking a function with async in Swift mean?

easy

A. The function cannot call other functions.

B. The function runs only once and then stops.

C. The function must return an integer value.

D. The function can pause and resume without blocking the app's main thread.

Solution

1. Step 1: Understand async function behavior

   Async functions allow pausing and resuming work without freezing the app's main thread.

2. Step 2: Compare options with async meaning

   Only The function can pause and resume without blocking the app's main thread. correctly describes this behavior; others are unrelated or incorrect.

3. Final Answer:

   The function can pause and resume without blocking the app's main thread. -> Option D

4. Quick Check:

   Async means non-blocking pause/resume = A [OK]

Hint: Async means work happens without freezing UI [OK]

Common Mistakes:

• Thinking async means the function runs only once
• Confusing async with return types
• Believing async functions cannot call others

2. Which of the following is the correct way to declare an async function in Swift?

easy

A. func fetchData() async throws -> String {}

B. async func fetchData() -> String {}

C. func async fetchData() throws -> String {}

D. func fetchData() throws async String {}

Solution

1. Step 1: Recall Swift async function syntax

   In Swift, async comes after the parameter list and before the return type.

2. Step 2: Match options to correct syntax

   Only func fetchData() async throws -> String {} matches the correct syntax: func name() async throws -> Type {}.

3. Final Answer:

   func fetchData() async throws -> String {} -> Option A

4. Quick Check:

   Async keyword after () = C [OK]

Hint: Async keyword goes after function parameters () [OK]

Common Mistakes:

• Placing async before func keyword
• Mixing async and throws order
• Putting async after return type

3. What will be printed by this Swift code?

func fetchNumber() async -> Int {
  return 42
}

Task {
  let number = await fetchNumber()
  print(number)
}

medium

A. 42

B. nil

C. Task

D. Compilation error

Solution

1. Step 1: Understand async function return

   The async function fetchNumber() returns 42 as an Int.

2. Step 2: Await call inside Task and print

   The await keyword waits for the async function to finish, then prints 42.

3. Final Answer:

   42 -> Option A

4. Quick Check:

   Await fetch returns 42 printed = D [OK]

Hint: Await pauses until async returns value [OK]

Common Mistakes:

• Expecting nil because of async
• Thinking Task prints itself
• Assuming compilation error without await

4. Identify the error in this Swift async code:

func loadData() async -> String {
  return "Data"
}

let result = loadData()
print(result)

medium

A. Async functions cannot return String

B. Missing await keyword when calling async function

C. Function must be marked throws

D. Cannot print async function result

Solution

1. Step 1: Check async function call

   Async functions must be called with await to get their result.

2. Step 2: Identify missing await

   The code calls loadData() without await, causing a compile error.

3. Final Answer:

   Missing await keyword when calling async function -> Option B

4. Quick Check:

   Call async with await = B [OK]

Hint: Always use await when calling async functions [OK]

Common Mistakes:

• Calling async functions without await
• Thinking async functions can't return String
• Assuming print can't show async results

5. You want to fetch user data and then fetch user image asynchronously in Swift. Which code correctly waits for both tasks in order?

hard

A. async func loadUser() {
let data = fetchUserData()
let image = fetchUserImage(data.id)
print(image)
}

B. func loadUser() {
let data = fetchUserData()
let image = fetchUserImage(data.id)
print(image)
}

C. async func loadUser() {
let data = await fetchUserData()
let image = await fetchUserImage(data.id)
print(image)
}

D. async func loadUser() {
let data = await fetchUserData()
let image = fetchUserImage(data.id)
print(image)
}

Solution

1. Step 1: Understand async calls order

   Both fetchUserData() and fetchUserImage() are async and must be awaited to complete before next step.

2. Step 2: Check which code awaits both calls

   Only async func loadUser() { let data = await fetchUserData() let image = await fetchUserImage(data.id) print(image) } awaits both calls in order, ensuring data is ready before fetching image.

3. Final Answer:

   async func loadUser() { let data = await fetchUserData() let image = await fetchUserImage(data.id) print(image) } -> Option C

4. Quick Check:

   Await each async call in order = A [OK]

Hint: Await each async call to run sequentially [OK]

Common Mistakes:

• Not awaiting async calls
• Calling async functions without async keyword
• Mixing sync and async calls incorrectly