Empty state handling in iOS Swift - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What will the UI show when the data array is empty?

Consider this SwiftUI view that shows a list or an empty state message. What will the user see if the data array is empty?

iOS Swift

struct ContentView: View {
  let data: [String]
  var body: some View {
    if data.isEmpty {
      Text("No items found.")
        .foregroundColor(.gray)
        .italic()
    } else {
      List(data, id: \.self) { item in
        Text(item)
      }
    }
  }
}

A A runtime error because the list has no data

B An empty list with no rows visible

C A gray italic text saying "No items found."

D A blank white screen with no text

💡 Hint

Look at the condition that checks if data.isEmpty and what it shows.

The code checks if the data array is empty. If it is, it shows a gray italic text "No items found." Otherwise, it shows the list of items.

❓ lifecycle

intermediate

When should you update the empty state UI in a SwiftUI view?

You have a SwiftUI view showing a list or an empty state message. When is the best time to update the UI to reflect changes in the data source?

A Whenever the data source changes, the view should update automatically if data is a @State or @ObservedObject property

B Only when the view appears for the first time

C Manually call a function to refresh the UI every second

D Update the UI only when the app restarts

💡 Hint

Think about how SwiftUI reacts to changes in @State or @ObservedObject properties.

SwiftUI automatically updates the UI when properties marked with @State or @ObservedObject change. This keeps the UI in sync with the data source.

🔧 Debug

advanced

Why does the empty state text not appear in this UIKit code?

This UIKit code tries to show a label when the data array is empty, but the label never appears. What is the cause?

iOS Swift

class ViewController: UIViewController {
  let data: [String] = []
  let emptyLabel = UILabel()

  override func viewDidLoad() {
    super.viewDidLoad()
    emptyLabel.text = "No data available"
    emptyLabel.textColor = .gray
    emptyLabel.textAlignment = .center
    if data.isEmpty {
      view.addSubview(emptyLabel)
    }
  }

  override func viewDidLayoutSubviews() {
    super.viewDidLayoutSubviews()
    emptyLabel.frame = CGRect(x: 0, y: 0, width: view.bounds.width, height: 50)
    emptyLabel.center = view.center
  }
}

A The label is never added to the view hierarchy

B The label is behind other views and not visible

C The label text is empty so nothing shows

D The label is added but has zero size because frame is set after viewDidLayoutSubviews

💡 Hint

Think about view layering and if other views cover the label.

The label is added and sized correctly, but other subviews added earlier may cover it. Without bringing the label to front or adjusting layering, it stays hidden behind other views.

❓ navigation

advanced

How to navigate from an empty state view to a data entry screen in SwiftUI?

You want to show a button on the empty state screen that navigates to a data entry view. Which code snippet correctly implements this navigation?

A Add a gesture recognizer to the empty state text to push DataEntryView

B Button(action: { NavigationLink(destination: DataEntryView()) }) { Text("Add Item") }

C Use a modal presentation without NavigationLink or NavigationView

D NavigationLink(destination: DataEntryView()) { Text("Add Item") } inside the empty state view

💡 Hint

NavigationLink is the standard way to navigate in SwiftUI inside a NavigationView.

NavigationLink creates a tappable element that navigates to the destination view when tapped. It must be inside a NavigationView to work properly.

🧠 Conceptual

expert

Why is handling empty states important in mobile app UX?

Choose the best explanation for why empty state handling improves user experience in mobile apps.

A It guides users on what to do next and prevents confusion when no data is available

B It reduces app size by not loading data unnecessarily

C It improves app performance by skipping UI rendering

D It allows the app to crash gracefully when data is missing

💡 Hint

Think about how users feel when they see an empty screen with no explanation.

Empty states provide helpful messages or actions that guide users, making the app feel friendly and easy to use even when no data is present.