iOS ecosystem overview (iPhone, iPad, Apple Watch) in iOS Swift - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Device Capabilities in iOS Ecosystem

Which device in the iOS ecosystem primarily supports apps that use a smaller screen and focus on quick interactions with complications and notifications?

A Apple Watch

B iPad

C iPhone

D MacBook

💡 Hint

Think about which device is worn on the wrist and designed for glanceable information.

The Apple Watch is designed for quick interactions on a small screen, using complications and notifications to provide timely information.

❓ ui_behavior

intermediate

Adapting UI for Different iOS Devices

When designing an app that runs on both iPhone and iPad, which approach best ensures the UI adapts properly to different screen sizes?

A Create separate apps for iPhone and iPad

B Use fixed pixel sizes for all UI elements

C Design only for iPhone and scale up for iPad

D Use Auto Layout constraints and size classes

💡 Hint

Think about how to make UI flexible and responsive.

Auto Layout and size classes allow the UI to adapt dynamically to different screen sizes and orientations on iPhone and iPad.

❓ lifecycle

advanced

App Lifecycle Differences on Apple Watch

Which statement best describes the app lifecycle behavior on Apple Watch compared to iPhone?

A Apple Watch apps have limited background execution and rely on snapshots

B Apple Watch apps use the same lifecycle methods as iPad apps

C Apple Watch apps do not support background tasks at all

D Apple Watch apps run continuously in the background like iPhone apps

💡 Hint

Consider battery and performance constraints on the watch.

Apple Watch apps have limited background execution to save battery and use snapshots to quickly show app state when launched.

❓ navigation

advanced

Navigation Patterns Across iOS Devices

Which navigation pattern is most commonly used on iPad apps but less on iPhone apps due to screen size differences?

A Tab Bar Controller

B Modal Presentation

C Split View Controller

D Page View Controller

💡 Hint

Think about how iPad uses larger screen space for master-detail views.

Split View Controller is commonly used on iPad to show master-detail interfaces side by side, which is less practical on smaller iPhone screens.

🔧 Debug

expert

Identifying Cause of Watch App Launch Delay

An Apple Watch app takes a long time to launch and sometimes crashes. Which cause is most likely responsible?

iOS Swift

func applicationDidFinishLaunching() {
  for _ in 0..<1000000 {
    print("Loading...")
  }
}

A The app is not using Auto Layout for UI

B The app is performing heavy work on the main thread during launch

C The app is using background tasks incorrectly

D The app is missing required Info.plist keys

💡 Hint

Consider what happens if you do a lot of work right when the app starts.

Doing heavy work on the main thread during launch blocks the UI and causes delays or crashes on Apple Watch.

Practice

1. Which device is NOT part of the iOS ecosystem?

easy

A. iPad

B. Android Phone

C. Apple Watch

D. iPhone

Solution

1. Step 1: Identify devices in the iOS ecosystem

   The iOS ecosystem includes iPhone, iPad, and Apple Watch devices.

2. Step 2: Compare options with known devices

   Android Phone is not part of Apple's iOS ecosystem; it runs a different operating system.

3. Final Answer:

   Android Phone -> Option B

4. Quick Check:

   iOS devices exclude Android phones [OK]

Hint: Remember Apple devices only include iPhone, iPad, Watch [OK]

Common Mistakes:

• Confusing Android phones as iOS devices
• Thinking iPod Touch is a main iOS device here
• Mixing up Apple Watch with other smartwatches

2. Which Swift code snippet correctly checks if the device is an iPad?

easy

A. if UIDevice.current.userInterfaceIdiom == .pad { /* iPad code */ }

B. if UIDevice.current.deviceType == "iPad" { /* iPad code */ }

C. if UIDevice.isPad { /* iPad code */ }

D. if UIDevice.current.model == "iPad" { /* iPad code */ }

Solution

1. Step 1: Recall correct property for device type

   UIDevice.current.userInterfaceIdiom returns the device type enum, including .pad for iPad.

2. Step 2: Check each option's syntax

   if UIDevice.current.userInterfaceIdiom == .pad { /* iPad code */ } uses the correct property and enum value. Others use incorrect or non-existent properties.

3. Final Answer:

   if UIDevice.current.userInterfaceIdiom == .pad { /* iPad code */ } -> Option A

4. Quick Check:

   Use userInterfaceIdiom == .pad to detect iPad [OK]

Hint: Use userInterfaceIdiom property to detect device type [OK]

Common Mistakes:

• Using non-existent properties like deviceType or isPad
• Comparing model string instead of userInterfaceIdiom
• Forgetting to use enum .pad for iPad

3. What will this Swift code print on an Apple Watch device?

let device = UIDevice.current
switch device.userInterfaceIdiom {
  case .phone: print("iPhone")
  case .pad: print("iPad")
  case .carPlay: print("CarPlay")
  default: print("Other")
}

medium

A. CarPlay

B. iPad

C. iPhone

D. Other

Solution

1. Step 1: Understand userInterfaceIdiom values

   Apple Watch devices have a userInterfaceIdiom value of .watch, which is not explicitly handled in the switch.

2. Step 2: Determine which case matches

   Since .watch is not matched by .phone, .pad, or .carPlay, the default case runs, printing "Other".

3. Final Answer:

   Other -> Option D

4. Quick Check:

   Unmatched idioms print default "Other" [OK]

Hint: Default case catches Apple Watch userInterfaceIdiom [OK]

Common Mistakes:

• Assuming Apple Watch is .phone or .pad
• Missing default case in switch
• Confusing .carPlay with Apple Watch

4. Identify the error in this Swift code intended to detect Apple Watch devices:

if UIDevice.current.userInterfaceIdiom == .watch {
  print("Apple Watch detected")
}

medium

A. The code is correct and will work as expected

B. UIDevice.current is not accessible on Apple Watch

C. The comparison should use a string instead of enum

D. The .watch case does not exist in userInterfaceIdiom enum

Solution

1. Step 1: Verify UIUserInterfaceIdiom enum

   UIUserInterfaceIdiom includes .watch (available since iOS 14.0/watchOS 7.0).

2. Step 2: Confirm UIDevice usage on Apple Watch

   UIDevice.current is accessible in watchOS apps (UIKit supported since watchOS 7), and returns .watch on Apple Watch.

3. Final Answer:

   The code is correct and will work as expected -> Option A

4. Quick Check:

   UIDevice.userInterfaceIdiom == .watch detects Apple Watch [OK]

Hint: Use UIDevice.current.userInterfaceIdiom == .watch for Apple Watch detection [OK]

Common Mistakes:

• Thinking UIDevice.current is unavailable on Apple Watch apps
• Believing .watch does not exist in UIUserInterfaceIdiom
• Assuming string comparison is needed instead of enum

5. You want to create a single SwiftUI app that adapts its layout for iPhone, iPad, and Apple Watch. Which approach is best?

hard

A. Create separate apps for each device and share no code

B. Use only iPhone layout and scale it for other devices

C. Use conditional views with if UIDevice.current.userInterfaceIdiom and WKInterfaceDevice checks

D. Ignore device differences and use fixed sizes for all

Solution

1. Step 1: Understand device-specific UI needs

   iPhone, iPad, and Apple Watch have different screen sizes and interaction models requiring adaptive layouts.

2. Step 2: Choose adaptive coding approach

   Using conditional checks with UIDevice for iPhone/iPad and WKInterfaceDevice for Apple Watch allows customizing views in one app.

3. Step 3: Evaluate other options

   Separate apps increase maintenance; scaling fixed layouts reduces usability; ignoring differences harms UX.

4. Final Answer:

   Use conditional views with if UIDevice.current.userInterfaceIdiom and WKInterfaceDevice checks -> Option C

5. Quick Check:

   Adaptive UI with device checks is best practice [OK]

Hint: Use device checks to adapt UI in one app [OK]

Common Mistakes:

• Building separate apps for each device unnecessarily
• Using fixed layouts that don't fit all screens
• Ignoring Apple Watch's unique interface needs