generators-state-restoration

SwiftUI state restoration captures NavigationStack paths, selected tabs, scroll positions, and form drafts using Codable models with @SceneStorage or file-based backends. It encodes UI state deterministically so apps resume exactly where users left off after background termination or scene changes.

Form draft restoration uses debounced autosave to Application Support or UserDefaults, writing in-progress text periodically and clearing it on submit. This ensures unsaved drafts survive background termination and relaunch without requiring manual snapshot management.

State restoration supports per-scene @SceneStorage for multi-window iPadOS apps, allowing each window to independently persist and restore its own NavigationStack path, TabView selection, and draft text. Shared UserDefaults or file backends handle cross-scene state when needed.

State restoration includes state versioning and graceful fallbacks for schema changes, using Codable models that detect version mismatches and discard incompatible data. Time-limited restore policies and optional ask-before-restore prompts prevent stale or corrupted state from disrupting the user experience.

Environment-driven integration provides optional modifiers for NavigationStack and TabView that automatically capture and restore selection state. The StateRestorationManager coordinates these modifiers with Codable AppState models to synchronize navigation paths and tab selections across launches.

Scene termination loses UI state when navigation paths, tab selections, and scroll offsets are not persisted. Without a StateRestorationManager encoding this data to @SceneStorage or a file backend, the app cannot rebuild the previous context and defaults to its initial view hierarchy.