If users cannot land on the right screen, return to the expected state, or recover after authentication, the problem is not “just SwiftUI”. It is a broken path through the product.

Patterns I watch for

  • route state owned in too many places
  • implicit state restoration
  • deep-link handling split between UIKit and SwiftUI layers
  • async work mutating route state after the user already moved on

What usually helps

Choose one place that owns route decisions. Make transitions observable. Prefer boring route graphs over clever convenience.