SwiftUI Fundamentals
Present temporary workflows and system messages with data-driven sheets, alerts, confirmation dialogs, and semantic toolbar actions.
Before you begin
Learning stage
A pushed destination extends the current hierarchy; a sheet presents a temporary or self-contained task. Use fullScreenCover only when immersive focus is justified. Presentation should follow the product relationship, not merely a desired animation.
Boolean presentation works for a simple local condition, but item-driven presentation connects visibility and content to one optional Identifiable value. When the value becomes non-nil, SwiftUI presents it; when presentation ends, the value returns to nil. This avoids separate isPresented and selectedItem state becoming inconsistent.
Alerts communicate important information or request a small decision. ConfirmationDialog is appropriate for a set of related choices, especially destructive ones. Toolbars place navigation, confirmation, cancellation, and contextual actions according to platform conventions. Button roles communicate semantics to styling and assistive technology.
Learning stage
The selected lesson is both the presentation trigger and the data supplied to the editor, eliminating invalid Boolean-plus-selection combinations.
import SwiftUI
struct Lesson: Identifiable {
let id: UUID
var title: String
}
struct LessonLibrary: View {
@State private var selectedLesson: Lesson?
@State private var lessonToDelete: Lesson?
var body: some View {
List(sampleLessons) { lesson in
Button(lesson.title) { selectedLesson = lesson }
.swipeActions {
Button("Delete", role: .destructive) { lessonToDelete = lesson }
}
}
.navigationTitle("Library")
.sheet(item: $selectedLesson) { lesson in
NavigationStack { LessonEditor(lesson: lesson) }
}
.confirmationDialog(
"Delete this lesson?",
isPresented: Binding(
get: { lessonToDelete != nil },
set: { if !$0 { lessonToDelete = nil } }
),
presenting: lessonToDelete
) { lesson in
Button("Delete (lesson.title)", role: .destructive) { delete(lesson) }
Button("Cancel", role: .cancel) { }
} message: { lesson in
Text("This action cannot be undone for (lesson.title).")
}
}
}Learning stage
Connect the SwiftUI concept to complete, maintainable application features.
Learning stage
Identify patterns that weaken ownership, identity, adaptation, accessibility, or user experience.
Learning stage
Build the behavior in a small Xcode project and review it in multiple states.
Activity 1
Present an editor sheet from a list using an optional Identifiable selection. Include Cancel and Save toolbar actions and dismiss only after valid save.
Hint: Let the selected optional value control both presentation and content.
Activity 2
Add a confirmation dialog for deleting a course with a clear consequence, destructive role, and cancel action.
Hint: Name the object so the user can verify what will be deleted.
Learning stage
Answer each question before revealing the explanation.
QUESTION 1
One optional value controls both presentation and content
The impossible state of a visible sheet with no selected item is eliminated.
QUESTION 2
Usually no. Validation is generally clearer near the relevant field.
Alerts interrupt the user and are better reserved for important messages or small decisions.
Learning stage
Explain the design in terms of data flow, identity, lifecycle, platform behavior, and trade-offs.
Short answer: Use navigation for hierarchy and a sheet for a temporary, self-contained task that preserves the current context.
The product relationship determines the presentation. A detail usually belongs in navigation. Editing, creation, filters, or account tasks often fit a modal. I also consider whether the task needs its own internal NavigationStack and how cancellation or completion returns to the underlying context.
Possible follow-ups
Learning stage
Presentation is part of information architecture. Model modal content from data, use system roles and toolbar placements, and reserve alerts and confirmation dialogs for decisions that truly need interruption.