How does navigation and data flow work with NavigationStack in SwiftUI?

Question

IT Interview Practice · Accepted Answer

`NavigationStack` (iOS 16+) is SwiftUI's **data-driven** navigation container: instead of pushing view controllers imperatively, you bind an array **path** of values, and the stack renders a screen for each value. Data flows *down* through view initializers and the *environment*, and *up* through bindings and callbacks.

## How it works

You drive navigation by mutating a `@State` path, and map value types to destination views with `navigationDestination`.

```swift
struct AppView: View {
    @State private var path: [Route] = []      // the navigation stack, as data

var body: some View {
        NavigationStack(path: $path) {
            List(products) { p in
                NavigationLink("Open", value: Route.detail(p.id))  // append value
            }
            .navigationDestination(for: Route.self) { route in
                switch route {
                case .detail(let id): DetailView(id: id)
                }
            }
        }
    }
}
enum Route: Hashable { case detail(Int) }
```

Because the path is plain data, you can **deep-link** by setting `path = [.detail(42)]`, or **pop to root** with `path.removeAll()` — navigation becomes testable, serializable state.

## Data flow directions

- **Down:** pass values via initializers (`DetailView(id:)`), or share cross-cutting objects with `.environmentObject(...)` / the `@Environment` system.
- **Up:** child mutates a `@Binding` or calls a closure the parent supplied.

## Pitfalls

- Destination values must be **`Hashable`**.
- Register each type once with `navigationDestination`; multiple registrations for the same type conflict.
- Avoid passing giant model objects down every initializer — use the environment for app-wide services instead.

## Why it matters

Data-driven navigation makes flows like deep links, restoration, and "pop three screens back" trivial because the stack is just an array you own. Interviewers ask this to see whether you model navigation as state — the modern SwiftUI approach — rather than fighting the old imperative `NavigationView`.

How it works

Data flow directions

Pitfalls

Why it matters

Related questions