Explain the iOS app and scene lifecycle in SwiftUI.

Question

IT Interview Practice · Accepted Answer

An iOS app moves through **lifecycle phases** — launch, active, background, terminated — and SwiftUI exposes them through the `App` protocol and the `scenePhase` environment value. You hook into these to save data, pause work, and refresh the UI at the right moments.

## How it works

The app entry point is a `struct` marked `@main` conforming to `App`. It returns one or more `Scene`s (usually a `WindowGroup`).

```swift
@main
struct MyApp: App {
    @Environment(\.scenePhase) private var scenePhase

var body: some Scene {
        WindowGroup {
            ContentView()
        }
        .onChange(of: scenePhase) { _, newPhase in
            switch newPhase {
            case .active:    resumeTimers()    // app in foreground, interactive
            case .inactive:  pauseSensitive()  // transitioning (e.g. app switcher)
            case .background: saveState()       // not visible — persist now
            @unknown default: break
            }
        }
    }
}
```

## The three scene phases

- **`.active`** — foreground and receiving events. Resume animations, timers, live updates.
- **`.inactive`** — visible but not receiving events (incoming call, app switcher). A brief transitional state.
- **`.background`** — not visible. You get limited time to **persist state and free resources** before possible termination.

## Pitfalls

- Do heavy saves in `.background`, not `.inactive` — inactive fires often and briefly.
- Background execution time is limited; long tasks need `BGTaskScheduler`, not the phase handler.
- With the older UIKit `AppDelegate`/`SceneDelegate`, the equivalent callbacks are `applicationDidEnterBackground` etc. SwiftUI can still bridge to them via `@UIApplicationDelegateAdaptor`.

## Why it matters

Users switch apps constantly, and the system can terminate a backgrounded app without warning. Reacting correctly to `scenePhase` is what makes an app feel reliable — unsaved data survives, and the UI refreshes when the user returns instead of showing stale content.